Create Report

Follow the user's brief first. Capture purpose, audience, question or decision, sources, output path, tone or branding, required sections, depth, and constraints before choosing structure. User-selected HTML structure and style override defaults when they stay truthful, safe, accessible, and compatible. Ask only when a missing choice materially changes the artifact.

This skill is not a completion gate. Produce a report only for an explicit standalone HTML artifact when no adjacent workflow owns the task.

Critical rules

• Default to one offline reports/<descriptive-slug>.html. Do not overwrite an existing path without explicit approval.
• Keep the executive layer to about five minutes: answer or outcome, scope, key evidence, implications, and next action.
• Label material ambiguity Observed, Source-reported, Inference, or Unknown. Cite relocatable sources. Never invent metrics, confidence, ownership, dates, status, rationale, or citations.
• Findings state evidence, consequence, and next action. Recommendations state basis, expected effect, trade-off, assumptions, and prerequisites. Use Unassigned, TBD, or Unknown rather than filling gaps.
• Every retained headline number and key conclusion reaches evidence through an ordinary on-page fragment link or a labelled dialog. Dialogs are optional; central evidence stays on-page and print-available. Core content and section navigation work without JavaScript.
• Escape inserted content. Reject unsafe URL schemes. Allow safe citation links. Embed only approved assets. Redact secrets, credentials, tokens, and PII.
• Do not adopt another workflow's authority. A report is not a code-review, plan, complexity audit, change handoff, or live app.
• Before choosing structure, read references/report-design.md. It is mandatory.
• Final audit is required: every material number and claim resolves to support, unsupported claims are removed or labelled, and the report does not adopt another workflow's authority.

Workflow