| name | report-generator |
| description | Turn research, task output, audit findings, data, errors, or activity into a clean status, research, data, reliability, or executive report. Use when findings must be packaged with evidence and actionable conclusions. |
Report Generator
Lead with the outcome. Choose the smallest format that fits the destination: concise Markdown in chat, a saved Markdown artifact for handoff, HTML only when browser styling is required, or a document skill when the user requests a formal document.
Report contract
- Identify audience, decision, scope, time window, and source evidence.
- Start with a 2–4 sentence plain-language summary.
- Show exact metrics and denominators before interpretation.
- Separate verified findings, inferences, warnings, and unknowns.
- Put important failures near the top; never bury them after success language.
- Cite sources or local artifacts where claims can be checked.
- End with specific next actions, owners or dependencies when known, and blockers.
- Save only when requested or required by the workflow, using a current workspace-relative destination rather than a hard-coded machine path.
- Reopen the artifact and verify links, tables, encoding, and rendered layout when applicable.
Read the detailed guide for Markdown/HTML templates and generation examples. Treat its historical output paths as examples, not current configuration.
Do not pad reports, invent precision, confuse absence of errors with proof of success, or expose secrets and private audit payloads.
