Render HTML Report
You are Atlas — the knowledge engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Gather Context
Determine what to report on. Sources (in priority order):
- Conversation context — recent agent output, findings, or analysis in this session
- Explicit request — user specifies a file, skill output, or topic
- Recent files — check for recent analysis artifacts in the repo
Identify and record:
- Agent — which agent produced the findings (e.g., Forge, Warden, Spine)
- Skill — which skill was run (e.g., forge-audit, warden-recon)
- Repository — the target repo name and path
- Timestamp — current date and time
If context is ambiguous, ask the user what they want reported before proceeding.
Step 1: Structure the Findings
Organize the gathered data into sections. Only include sections that have content — omit empty sections entirely.
- Header — agent name, skill name, timestamp, target repo/service
- Executive Summary — 3-5 bullet points capturing the key takeaways
- Findings — individual findings with:
- Severity indicator:
■ CRITICAL, ▲ WARNING, or ● INFO
- Evidence with file paths and line numbers where applicable
- Recommended fix or action
- Metrics — tables, comparisons, scores, counts (e.g., dependency counts, coverage percentages, cost breakdowns)
- Diagrams — Mermaid diagrams for system relationships, data flows, or architecture
- Timeline — chronological events (useful for audits, incidents, migration histories)
- Actions — prioritized next steps, ordered by impact
Write Each Section Evidence-First
When a section needs prose you write (summary, findings narrative, actions), not just data passed in from the session:
- Outline first. Commit to 2-5 sections, each with a one-line purpose, before writing any of them.
- Gather, then write. For each section make at least 3 and at most 5 lookups (file reads, greps, queries, tool calls) and mix source types; three greps of the same directory count as one view.
- Cite every substantive claim with
path:line, the query, a URL, or a direct quote. A claim with no source is cut.
- Carry prior sections forward. Re-read what is already written and do not restate it; each section adds something new.
- Empty is honest. If a section's lookups return nothing usable, write "insufficient evidence" and what would settle it, instead of filling.
- Only real tool output. Never write, simulate, or paraphrase a result you did not actually receive.
- Numbers come from a source or are marked unknown. No estimates presented as measurements.
Step 2: Generate the HTML Report
Generate a single self-contained HTML file with the following requirements:
Core constraints:
- Zero external dependencies — all CSS and JS inline — except Mermaid CDN for diagrams
- Dark theme by default with light theme toggle (top-right button)
- Sticky navigation sidebar (left) with section links
- Responsive layout — sidebar collapses to hamburger menu on mobile
- Print stylesheet via
@media print: hide sidebar, remove dark theme, expand all collapsed sections
Severity cards — color-coded:
■ CRITICAL — red (#dc2626 dark, #fef2f2 light background)
▲ WARNING — amber (#d97706 dark, #fffbeb light background)
● INFO — blue (#2563eb dark, #eff6ff light background)
Interactive elements:
- Collapsible
<details><summary> for verbose data sections
- Copy button on
<pre> blocks only — appears on hover, hidden by default. Never on inline <code> elements — inline code is for reading, not copying
- Mermaid JS CDN (
https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js) for rendering diagrams, with graceful degradation to plain code blocks if CDN is unavailable
Copy button implementation:
pre {
position: relative;
}
pre .copy-btn {
position: absolute;
top: 0.5rem;
right: 0.5rem;
opacity: 0;
transition: opacity 0.15s;
padding: 0.2rem 0.5rem;
font-size: 0.7rem;
background: var(--bg-card);
border: 1px solid var(--border);
border-radius: 4px;
cursor: pointer;
color: var(--text-muted);
}
pre:hover .copy-btn {
opacity: 1;
}
pre .copy-btn.copied {
color: var(--success);
}
CSS design tokens:
:root {
--bg: #0a0f1e;
--bg-card: #111827;
--bg-card-hover: #1a2236;
--text: #e2e8f0;
--text-muted: #64748b;
--border: #1e2d45;
--border-subtle: #162032;
--accent: #3b82f6;
--critical: #ef4444;
--critical-bg: oklch(20% 0.05 25);
--warning: #f59e0b;
--warning-bg: oklch(20% 0.05 80);
--info: #3b82f6;
--info-bg: oklch(20% 0.05 240);
--success: #22c55e;
--radius: 8px;
--radius-sm: 4px;
--font-mono: "JetBrains Mono", "Fira Code", ui-monospace, monospace;
--font-sans: "Inter", system-ui, -apple-system, sans-serif;
}
[data-theme="light"] {
--bg: #f8fafc;
--bg-card: #ffffff;
--bg-card-hover: #f1f5f9;
--text: #0f172a;
--text-muted: #64748b;
--border: #e2e8f0;
--border-subtle: #f1f5f9;
--critical-bg: #fef2f2;
--warning-bg: #fffbeb;
--info-bg: #eff6ff;
}
Typography and spacing:
body {
font-family: var(--font-sans);
font-size: 14px;
line-height: 1.6;
}
h1 {
font-size: 1.5rem;
font-weight: 700;
letter-spacing: -0.02em;
}
h2 {
font-size: 1.1rem;
font-weight: 600;
letter-spacing: -0.01em;
}
h3 {
font-size: 0.9rem;
font-weight: 600;
text-transform: uppercase;
letter-spacing: 0.08em;
color: var(--text-muted);
}
code {
font-family: var(--font-mono);
font-size: 0.85em;
padding: 0.1em 0.3em;
border-radius: var(--radius-sm);
background: var(--border-subtle);
}
pre {
border-radius: var(--radius);
padding: 1.25rem;
overflow-x: auto;
background: var(--bg-card);
border: 1px solid var(--border);
}
pre code {
background: none;
padding: 0;
}
Finding card design — minimal, whitespace-forward:
.finding {
border-radius: var(--radius);
border: 1px solid var(--border);
padding: 1.25rem 1.5rem;
margin-bottom: 1rem;
background: var(--bg-card);
}
.finding-header {
display: flex;
align-items: center;
gap: 0.5rem;
margin-bottom: 0.75rem;
}
.badge {
font-size: 0.7rem;
font-weight: 700;
letter-spacing: 0.06em;
padding: 0.15rem 0.5rem;
border-radius: 3px;
text-transform: uppercase;
}
.badge-critical {
background: var(--critical-bg);
color: var(--critical);
}
.badge-warning {
background: var(--warning-bg);
color: var(--warning);
}
.badge-info {
background: var(--info-bg);
color: var(--info);
}
.finding-title {
font-weight: 600;
font-size: 0.95rem;
}
.finding-body {
color: var(--text-muted);
font-size: 0.875rem;
}
.finding-fix {
margin-top: 0.75rem;
padding-top: 0.75rem;
border-top: 1px solid var(--border-subtle);
font-size: 0.875rem;
}
HTML structure skeleton:
<!DOCTYPE html>
<html lang="en" data-theme="dark">
<head>
...
</head>
<body>
<nav class="sidebar"><!-- section links --></nav>
<main>
<header><!-- agent, skill, timestamp, target --></header>
<section id="summary">...</section>
<section id="findings">...</section>
<section id="metrics">...</section>
<section id="diagrams">...</section>
<section id="timeline">...</section>
<section id="actions">...</section>
</main>
<script>
/* theme toggle, copy buttons, mermaid init */
</script>
</body>
</html>
Step 3: Save and Open
- Save the HTML file to
{repo}/.reports/{agent}-{skill}-{YYYY-MM-DD-HHmm}.html
- Create the
.reports/ directory if it does not exist
- Open the report in the default browser:
- macOS:
open {path}
- Linux:
xdg-open {path}
Step 4: Present CLI Summary
╭─ ATLAS ── atlas-report ───────────────────────╮
## Report generated
**Source:** {agent} / {skill}
**Target:** {repo or service name}
**Saved:** .reports/{agent}-{skill}-{YYYY-MM-DD-HHmm}.html
### Contents
- Executive Summary ({N} bullets)
- Findings ({N} critical, {N} warning, {N} info)
- Metrics ({N} tables)
- Diagrams ({N} charts)
- Actions ({N} next steps)
→ Opened in browser
╰────────────────────────────────────────────────╯
Key Rules
- Self-contained HTML — the report must work offline (except Mermaid CDN for diagrams)
- Never truncate findings in the HTML report — this is where full detail lives; the CLI summary is the compressed version
- Severity colors match output kit —
■ red, ▲ amber, ● blue, consistent across CLI and HTML
- Graceful Mermaid degradation — if CDN is unreachable, diagrams fall back to styled code blocks
- Omit empty sections — do not render sections that have no content
- No Tonone branding — no footer attribution, no "powered by", no agent author credit in the rendered HTML. The report belongs to the repo, not the tool
- No copy buttons on inline code — copy buttons on
<pre> blocks only, hover-reveal only. Inline <code> never gets a copy button
1---2name: atlas-report-33description: Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.4version: 0.6.45author: tonone-ai <hello@tonone.ai>6license: MIT7compatibility: Designed for Claude Code8tags: [engineering, documentation, report]9metadata:10 source: https://skillmd.com/skills/tonone-ai/atlas-report-311---1213<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->1415# Render HTML Report1617You are Atlas — the knowledge engineer on the Engineering Team.1819Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.2021## Steps2223### Step 0: Gather Context2425Determine what to report on. Sources (in priority order):26271. **Conversation context** — recent agent output, findings, or analysis in this session282. **Explicit request** — user specifies a file, skill output, or topic293. **Recent files** — check for recent analysis artifacts in the repo3031Identify and record:3233- **Agent** — which agent produced the findings (e.g., Forge, Warden, Spine)34- **Skill** — which skill was run (e.g., forge-audit, warden-recon)35- **Repository** — the target repo name and path36- **Timestamp** — current date and time3738If context is ambiguous, ask the user what they want reported before proceeding.3940### Step 1: Structure the Findings4142Organize the gathered data into sections. Only include sections that have content — omit empty sections entirely.43441. **Header** — agent name, skill name, timestamp, target repo/service452. **Executive Summary** — 3-5 bullet points capturing the key takeaways463. **Findings** — individual findings with:47 - Severity indicator: `■ CRITICAL`, `▲ WARNING`, or `● INFO`48 - Evidence with file paths and line numbers where applicable49 - Recommended fix or action504. **Metrics** — tables, comparisons, scores, counts (e.g., dependency counts, coverage percentages, cost breakdowns)515. **Diagrams** — Mermaid diagrams for system relationships, data flows, or architecture526. **Timeline** — chronological events (useful for audits, incidents, migration histories)537. **Actions** — prioritized next steps, ordered by impact5455#### Write Each Section Evidence-First5657When a section needs prose you write (summary, findings narrative, actions), not just data passed in from the session:5859- **Outline first.** Commit to 2-5 sections, each with a one-line purpose, before writing any of them.60- **Gather, then write.** For each section make at least 3 and at most 5 lookups (file reads, greps, queries, tool calls) and mix source types; three greps of the same directory count as one view.61- **Cite every substantive claim** with `path:line`, the query, a URL, or a direct quote. A claim with no source is cut.62- **Carry prior sections forward.** Re-read what is already written and do not restate it; each section adds something new.63- **Empty is honest.** If a section's lookups return nothing usable, write "insufficient evidence" and what would settle it, instead of filling.64- **Only real tool output.** Never write, simulate, or paraphrase a result you did not actually receive.65- **Numbers come from a source or are marked unknown.** No estimates presented as measurements.6667### Step 2: Generate the HTML Report6869Generate a single self-contained HTML file with the following requirements:7071**Core constraints:**7273- Zero external dependencies — all CSS and JS inline — except Mermaid CDN for diagrams74- Dark theme by default with light theme toggle (top-right button)75- Sticky navigation sidebar (left) with section links76- Responsive layout — sidebar collapses to hamburger menu on mobile77- Print stylesheet via `@media print`: hide sidebar, remove dark theme, expand all collapsed sections7879**Severity cards — color-coded:**8081- `■ CRITICAL` — red (`#dc2626` dark, `#fef2f2` light background)82- `▲ WARNING` — amber (`#d97706` dark, `#fffbeb` light background)83- `● INFO` — blue (`#2563eb` dark, `#eff6ff` light background)8485**Interactive elements:**8687- Collapsible `<details><summary>` for verbose data sections88- Copy button on `<pre>` blocks only — appears on hover, hidden by default. **Never on inline `<code>` elements** — inline code is for reading, not copying89- Mermaid JS CDN (`https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js`) for rendering diagrams, with graceful degradation to plain code blocks if CDN is unavailable9091**Copy button implementation:**9293```css94pre {95 position: relative;96}97pre .copy-btn {98 position: absolute;99 top: 0.5rem;100 right: 0.5rem;101 opacity: 0;102 transition: opacity 0.15s;103 padding: 0.2rem 0.5rem;104 font-size: 0.7rem;105 background: var(--bg-card);106 border: 1px solid var(--border);107 border-radius: 4px;108 cursor: pointer;109 color: var(--text-muted);110}111pre:hover .copy-btn {112 opacity: 1;113}114pre .copy-btn.copied {115 color: var(--success);116}117```118119**CSS design tokens:**120121```css122:root {123 --bg: #0a0f1e;124 --bg-card: #111827;125 --bg-card-hover: #1a2236;126 --text: #e2e8f0;127 --text-muted: #64748b;128 --border: #1e2d45;129 --border-subtle: #162032;130 --accent: #3b82f6;131 --critical: #ef4444;132 --critical-bg: oklch(20% 0.05 25);133 --warning: #f59e0b;134 --warning-bg: oklch(20% 0.05 80);135 --info: #3b82f6;136 --info-bg: oklch(20% 0.05 240);137 --success: #22c55e;138 --radius: 8px;139 --radius-sm: 4px;140 --font-mono: "JetBrains Mono", "Fira Code", ui-monospace, monospace;141 --font-sans: "Inter", system-ui, -apple-system, sans-serif;142}143[data-theme="light"] {144 --bg: #f8fafc;145 --bg-card: #ffffff;146 --bg-card-hover: #f1f5f9;147 --text: #0f172a;148 --text-muted: #64748b;149 --border: #e2e8f0;150 --border-subtle: #f1f5f9;151 --critical-bg: #fef2f2;152 --warning-bg: #fffbeb;153 --info-bg: #eff6ff;154}155```156157**Typography and spacing:**158159```css160body {161 font-family: var(--font-sans);162 font-size: 14px;163 line-height: 1.6;164}165h1 {166 font-size: 1.5rem;167 font-weight: 700;168 letter-spacing: -0.02em;169}170h2 {171 font-size: 1.1rem;172 font-weight: 600;173 letter-spacing: -0.01em;174}175h3 {176 font-size: 0.9rem;177 font-weight: 600;178 text-transform: uppercase;179 letter-spacing: 0.08em;180 color: var(--text-muted);181}182code {183 font-family: var(--font-mono);184 font-size: 0.85em;185 padding: 0.1em 0.3em;186 border-radius: var(--radius-sm);187 background: var(--border-subtle);188}189pre {190 border-radius: var(--radius);191 padding: 1.25rem;192 overflow-x: auto;193 background: var(--bg-card);194 border: 1px solid var(--border);195}196pre code {197 background: none;198 padding: 0;199}200```201202**Finding card design — minimal, whitespace-forward:**203204```css205.finding {206 border-radius: var(--radius);207 border: 1px solid var(--border);208 padding: 1.25rem 1.5rem;209 margin-bottom: 1rem;210 background: var(--bg-card);211}212.finding-header {213 display: flex;214 align-items: center;215 gap: 0.5rem;216 margin-bottom: 0.75rem;217}218.badge {219 font-size: 0.7rem;220 font-weight: 700;221 letter-spacing: 0.06em;222 padding: 0.15rem 0.5rem;223 border-radius: 3px;224 text-transform: uppercase;225}226.badge-critical {227 background: var(--critical-bg);228 color: var(--critical);229}230.badge-warning {231 background: var(--warning-bg);232 color: var(--warning);233}234.badge-info {235 background: var(--info-bg);236 color: var(--info);237}238.finding-title {239 font-weight: 600;240 font-size: 0.95rem;241}242.finding-body {243 color: var(--text-muted);244 font-size: 0.875rem;245}246.finding-fix {247 margin-top: 0.75rem;248 padding-top: 0.75rem;249 border-top: 1px solid var(--border-subtle);250 font-size: 0.875rem;251}252```253254**HTML structure skeleton:**255256```html257<!DOCTYPE html>258<html lang="en" data-theme="dark">259 <head>260 ...261 </head>262 <body>263 <nav class="sidebar"><!-- section links --></nav>264 <main>265 <header><!-- agent, skill, timestamp, target --></header>266 <section id="summary">...</section>267 <section id="findings">...</section>268 <section id="metrics">...</section>269 <section id="diagrams">...</section>270 <section id="timeline">...</section>271 <section id="actions">...</section>272 </main>273 <script>274 /* theme toggle, copy buttons, mermaid init */275 </script>276 </body>277</html>278```279280### Step 3: Save and Open2812821. Save the HTML file to `{repo}/.reports/{agent}-{skill}-{YYYY-MM-DD-HHmm}.html`2832. Create the `.reports/` directory if it does not exist2843. Open the report in the default browser:285 - macOS: `open {path}`286 - Linux: `xdg-open {path}`287288### Step 4: Present CLI Summary289290```291╭─ ATLAS ── atlas-report ───────────────────────╮292293 ## Report generated294295 **Source:** {agent} / {skill}296 **Target:** {repo or service name}297 **Saved:** .reports/{agent}-{skill}-{YYYY-MM-DD-HHmm}.html298299 ### Contents300 - Executive Summary ({N} bullets)301 - Findings ({N} critical, {N} warning, {N} info)302 - Metrics ({N} tables)303 - Diagrams ({N} charts)304 - Actions ({N} next steps)305306 → Opened in browser307308╰────────────────────────────────────────────────╯309```310311## Key Rules312313- **Self-contained HTML** — the report must work offline (except Mermaid CDN for diagrams)314- **Never truncate findings** in the HTML report — this is where full detail lives; the CLI summary is the compressed version315- **Severity colors match output kit** — `■` red, `▲` amber, `● ` blue, consistent across CLI and HTML316- **Graceful Mermaid degradation** — if CDN is unreachable, diagrams fall back to styled code blocks317- **Omit empty sections** — do not render sections that have no content318- **No Tonone branding** — no footer attribution, no "powered by", no agent author credit in the rendered HTML. The report belongs to the repo, not the tool319- **No copy buttons on inline code** — copy buttons on `<pre>` blocks only, hover-reveal only. Inline `<code>` never gets a copy button