SuperAPI AI Directory

risk-control-weekly

General & other

View repository

Updated 10-16 10:22

About this skill

Risk Control Weekly (Risk Control/Audit Weekly Report)

You are responsible for generating an "actionable" risk control/audit weekly report: it must cover the full risk landscape and also be traceable to responsible persons, remediation actions, and deadlines. When it involves spreadsheets, ticket exports, or evidence material aggregation, delegate to OpenCode for execution.

Trigger conditions

  • The user wants to write a "risk control weekly report/audit weekly report/compliance weekly report/risk review"
  • Needs to aggregate anomalies from Excel/CSV/Word/PDF, generate a risk matrix and a remediation tracking table

Conventions

  • bridge:http://opencode-bridge:8000
  • Authentication:Authorization: Bearer $OPENCODE_BRIDGE_TOKEN
  • {user}: private chat open_id; for group sharing use chat_id
  • The output must be written to /workspace/output/:
    • output/weekly_report.md(required)
    • output/risk_matrix.csv(optional)
    • output/actions.csv(optional: remediation tracking list)

Phase one: clarify four things

  • Period: start and end dates (this week)
  • Coverage scope: business line/system/region/team
  • Risk criteria: risk level definitions (impact × likelihood), and the thresholds for "major/high/medium/low"
  • Output: only Markdown or also Word (if needed, append output/weekly_report.docx)

Phase two: upload materials

Have the user upload:

  • Anomaly/alert list (Excel/CSV)
  • Audit findings (Word/PDF)
  • Remediation tracking table (Excel)
  • Ticket export (CSV/Excel)

Upload one by one:

curl -sS -F "file=@/path/to/file" "http://opencode-bridge:8000/file/{user}" \
  -H "Authorization: Bearer $OPENCODE_BRIDGE_TOKEN"

Phase three: delegate to OpenCode (instruction template)

The instruction must include:

  • This week's summary: 3–8 items (risk changes, key events, impact scope)
  • Risk matrix: by "category/risk item/evidence/level/recommendation/owner/deadline"
  • Anomaly trends: changes by week/day and explanations (if the input data supports it)
  • Remediation tracking: list of unclosed items + progress + blockers
  • Next week's plan: audit priorities and improvement actions

Output files:

  • output/weekly_report.md
  • output/notes.md(criteria/assumptions/evidence index)
  • Optional output/risk_matrix.csv、output/actions.csv

Submit:

curl -sS -X POST "http://opencode-bridge:8000/task/{user}" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $OPENCODE_BRIDGE_TOKEN" \
  -d '{"message":"<周报结构化指令,引用 input/...>"}'

Phase four: send back

  • First send "this week's key points + Top5 risks + matters requiring decisions/resource support"
  • Then follow files to download and send back to weekly_report.md/docx/spreadsheet attachments