--- name: html-report-builder description: > Build a self-contained HTML report as a companion artifact for audits, verifications, research, or long multi-command investigations. Always send a concise chat answer first, then save the HTML report under ./tmp/ and include a clickable path in chat. Triggers: "report", "audit", "check", "verify", "findings", "summary". context: fork --- # Report builder (HTML companion) Use when the user asks for a report, audit, verification/check, research write‑up, long-form findings, or when multi-step commands would benefit from a browsable artifact. Produces two outputs: (1) a concise chat response (always first), (2) a self-contained HTML5 report saved under `./tmp/` with a clickable path in chat. ## Workflow 1. Answer briefly in chat with the key outcome(s). 2. Save the HTML report under `./tmp/` as `tmp/-report-YYYYMMDD-HHMMSS.html`. 3. Include a markdown link to the file path in your chat reply. 4. During long investigations, update the report incrementally. ## Report structure - Title and timestamp - Executive summary (1–3 sentences) - Context (why this report exists) - Findings (bullets with supporting data) - Commands run (exact commands) - Evidence (selected logs/test output; truncate if huge, note truncation, link full logs in `./tmp/*.log`) - Recommendations (clear next steps) - References (clickable links) ## Presentation - Self-contained: inline CSS only, no external assets, UTF‑8 encoded. - Default theme: dark blue background, white text. Emojis (✅/❌) for quick status cues. - Add a progress bar when useful (see template). ## Safety and repo hygiene - Save only under `./tmp/`. Do not commit files from `./tmp/`. - Never include secrets/credentials or large binary dumps. Write full logs to `./tmp/*.log` and link. ## Validation checklist (pre-publish) - [ ] Sent a concise chat answer first - [ ] Report saved under `./tmp/` as `-report-YYYYMMDD-HHMMSS.html` - [ ] Executive summary present and accurate - [ ] Sections populated: Context, Findings, Commands run, Evidence, Recommendations, References - [ ] Progress bar included when multi-step/long-running - [ ] No secrets/PII; large outputs truncated in-page with full logs in `./tmp/` and linked - [ ] Self-contained HTML (inline CSS only), UTF‑8, code blocks readable - [ ] Clickable filesystem path included in chat - [ ] All links/paths resolve - [ ] If using `.claude/skills/html-report-builder/assets/report-template.html`, replaced placeholders (`[TASK]`, `[TIMESTAMP]`, `[PROGRESS%]`, etc.) ## HTML template Start from `.claude/skills/html-report-builder/assets/report-template.html` when you need a fuller starting point. The file lives at that exact path inside this skill folder. Minimal inline fallback (dark-blue theme, single-file): ```html [TASK] Report — [TIMESTAMP]

🔎 [TASK] Report [TIMESTAMP]

Context: why this report was generated.

Executive summary

1–3 sentences with key outcomes. ✅ Passed X. ❌ Found Y.

Progress

Findings

  • Finding — short statement with data.

Commands run

$ command --flag
[trimmed output]

Evidence

[short excerpts; full logs in ./tmp/*.log]

Recommendations

  1. Specific next step

References

``` Do not replace the chat response with the HTML. The HTML is a companion artifact only.