メニュー
How to scope, draft, and revise a Markdown report artifact via generate_report
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
Structured approach to finding and synthesizing information from the user's knowledge base
Pull together briefing materials before a scheduled meeting
Build distinctive, production-quality UI. Use when creating or reshaping user-facing interfaces, components, pages, layouts, visual redesigns, responsive behavior, loading/error/empty states, or accessibility-sensitive frontend work.
Draft an email matching the user's voice, with structured intent and CTA
Distill a Slack channel or thread into actionable summary
| name | report-writing |
| description | How to scope, draft, and revise a Markdown report artifact via generate_report |
| allowed-tools | generate_report, read_file |
The user explicitly requests a deliverable: "write a report on …", "draft a memo", "produce a brief", "expand the previous report". A creation or modification verb pointed at an artifact is required (see generate_report's when-to-call rules).
source_strategy fits:
conversation — substantive Q&A on the topic already in chat.kb_search — fresh topic; supply 1–5 precise search_queries.auto — partial conversation context; let the tool fall back.provided — verbatim source text only.report_style="detailed" unless the user explicitly asks for "brief", "one page", "500 words".parent_report_id and put the change list in user_instructions ("add carbon-capture section", "tighten conclusion").generate_report returns — confirm and let the artifact card render itself.If kb_search/auto returns no results, do not silently switch to general knowledge. Surface the gap in your confirmation message.