メニュー
Load when the user wants a written report produced from prior research, notes, or data — executive summary, technical write-up, or narrative report.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Load when the user asks to queue, enqueue, or add a coding task to the fleet, dispatch a job to a repo, or ask the fleet worker to fix something. Trigger phrases: "add to fleet", "queue a job for", "send to fleet", "dispatch to".
Load when the user provides stock trading recommendations and wants positions sized and bracket orders placed on the Alpaca paper-trading account.
Load when the user wants to navigate a website, click through a flow, fill a form, extract data from a page, or record an interaction as a reusable playbook.
Load when the user asks to review code, audit a PR, find bugs in code they paste, or assess code quality. Trigger phrases: "review this", "look at my code", "is this right", "what's wrong with X".
Load when the user is responding to a customer inquiry, complaint, or support ticket and needs help drafting a reply with the right tone.
Load when the user wants analysis on a dataset — trends, distributions, summary statistics, or insights from a CSV/JSON/Excel file.
| name | Report Writing |
| slug | report-writing |
| description | Load when the user wants a written report produced from prior research, notes, or data — executive summary, technical write-up, or narrative report. |
| icon | FileText |
| color | #6366f1 |
| version | 1.1.0 |
| category | writing |
| tools | ["read_file","write_file","search_knowledge_base"] |
| config_schema | {"type":"object","properties":{"report_style":{"type":"string","enum":["executive","technical","narrative"],"default":"executive"}}} |
Style: {report_style}.
executive — TL;DR → Key Findings → Recommendations → Supporting Data.technical — Abstract → Background → Methodology → Results → Discussion → Conclusion.narrative — Context → Story arc → Evidence → Implications → Next Steps.Lead with the most important finding, not background. Every claim is backed by data or a cited source — no exceptions.
End with concrete next steps. If owners are identifiable, name them.
Save the final report via write_file.