| name | build-report |
| description | Build a durable analytical report with an answer-first narrative, evidence-backed findings, charts or tables, caveats, recommendations, and source context. |
Build an Analytical Report
Use this workflow when the user needs a durable report rather than a transient answer. Run the appropriate analysis workflow first; this workflow owns the reader-facing structure, evidence placement, visual/table placement, caveats, sources, QA, and handoff.
Choose one delivery format
Honor an explicit format. Otherwise use:
- Markdown for the most portable code-agent deliverable.
- Self-contained plain HTML when a polished browser-readable report is useful and the host can render or inspect it.
- PDF, DOCX, slides, or another format only when requested or clearly required by the destination and the host exposes suitable creation and verification tools.
Do not install or require React, Recharts, Vite, MCP Apps, or widget runtimes. HTML must use semantic HTML/CSS and may use inline SVG or small vanilla JavaScript interactions. It must remain readable without JavaScript.
Build the report
- Confirm the audience, decision, scope, comparison window, and requested format from available context. Ask only when a missing choice would materially change the result.
- Verify the analytical evidence. Keep metric definitions, grain, time range, filters, units, exclusions, and source freshness explicit.
- Lead with the answer. State the most important conclusion and decision implication before methodology details.
- Build a coherent narrative rather than a dump of charts or query results.
- Include only visuals and tables that support a finding. Read
../visualize-data/SKILL.md when creating charts.
- Distinguish verified facts, likely explanations, assumptions, limitations, and unresolved questions.
- Provide recommendations tied to evidence, expected impact, owner or next action, and measurable follow-up where appropriate.
