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-23description: 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.4allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion5version: 0.6.46author: tonone-ai <hello@tonone.ai>7license: MIT8compatibility: Designed for Claude Code9tags: [engineering, documentation, report]10metadata:11 source: https://skillmd.com/skills/tonone-ai/atlas-report-212---1314<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->1516# Render HTML Report1718You are Atlas — the knowledge engineer on the Engineering Team.1920Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.2122## Steps2324### Step 0: Gather Context2526Determine what to report on. Sources (in priority order):27281. **Conversation context** — recent agent output, findings, or analysis in this session292. **Explicit request** — user specifies a file, skill output, or topic303. **Recent files** — check for recent analysis artifacts in the repo3132Identify and record:3334- **Agent** — which agent produced the findings (e.g., Forge, Warden, Spine)35- **Skill** — which skill was run (e.g., forge-audit, warden-recon)36- **Repository** — the target repo name and path37- **Timestamp** — current date and time3839If context is ambiguous, ask the user what they want reported before proceeding.4041### Step 1: Structure the Findings4243Organize the gathered data into sections. Only include sections that have content — omit empty sections entirely.44451. **Header** — agent name, skill name, timestamp, target repo/service462. **Executive Summary** — 3-5 bullet points capturing the key takeaways473. **Findings** — individual findings with:48 - Severity indicator: `■ CRITICAL`, `▲ WARNING`, or `● INFO`49 - Evidence with file paths and line numbers where applicable50 - Recommended fix or action514. **Metrics** — tables, comparisons, scores, counts (e.g., dependency counts, coverage percentages, cost breakdowns)525. **Diagrams** — Mermaid diagrams for system relationships, data flows, or architecture536. **Timeline** — chronological events (useful for audits, incidents, migration histories)547. **Actions** — prioritized next steps, ordered by impact5556#### Write Each Section Evidence-First5758When a section needs prose you write (summary, findings narrative, actions), not just data passed in from the session:5960- **Outline first.** Commit to 2-5 sections, each with a one-line purpose, before writing any of them.61- **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.62- **Cite every substantive claim** with `path:line`, the query, a URL, or a direct quote. A claim with no source is cut.63- **Carry prior sections forward.** Re-read what is already written and do not restate it; each section adds something new.64- **Empty is honest.** If a section's lookups return nothing usable, write "insufficient evidence" and what would settle it, instead of filling.65- **Only real tool output.** Never write, simulate, or paraphrase a result you did not actually receive.66- **Numbers come from a source or are marked unknown.** No estimates presented as measurements.6768### Step 2: Generate the HTML Report6970Generate a single self-contained HTML file with the following requirements:7172**Core constraints:**7374- Zero external dependencies — all CSS and JS inline — except Mermaid CDN for diagrams75- Dark theme by default with light theme toggle (top-right button)76- Sticky navigation sidebar (left) with section links77- Responsive layout — sidebar collapses to hamburger menu on mobile78- Print stylesheet via `@media print`: hide sidebar, remove dark theme, expand all collapsed sections7980**Severity cards — color-coded:**8182- `■ CRITICAL` — red (`#dc2626` dark, `#fef2f2` light background)83- `▲ WARNING` — amber (`#d97706` dark, `#fffbeb` light background)84- `● INFO` — blue (`#2563eb` dark, `#eff6ff` light background)8586**Interactive elements:**8788- Collapsible `<details><summary>` for verbose data sections89- Copy button on `<pre>` blocks only — appears on hover, hidden by default. **Never on inline `<code>` elements** — inline code is for reading, not copying90- 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 unavailable9192**Copy button implementation:**9394```css95pre {96 position: relative;97}98pre .copy-btn {99 position: absolute;100 top: 0.5rem;101 right: 0.5rem;102 opacity: 0;103 transition: opacity 0.15s;104 padding: 0.2rem 0.5rem;105 font-size: 0.7rem;106 background: var(--bg-card);107 border: 1px solid var(--border);108 border-radius: 4px;109 cursor: pointer;110 color: var(--text-muted);111}112pre:hover .copy-btn {113 opacity: 1;114}115pre .copy-btn.copied {116 color: var(--success);117}118```119120**CSS design tokens:**121122```css123:root {124 --bg: #0a0f1e;125 --bg-card: #111827;126 --bg-card-hover: #1a2236;127 --text: #e2e8f0;128 --text-muted: #64748b;129 --border: #1e2d45;130 --border-subtle: #162032;131 --accent: #3b82f6;132 --critical: #ef4444;133 --critical-bg: oklch(20% 0.05 25);134 --warning: #f59e0b;135 --warning-bg: oklch(20% 0.05 80);136 --info: #3b82f6;137 --info-bg: oklch(20% 0.05 240);138 --success: #22c55e;139 --radius: 8px;140 --radius-sm: 4px;141 --font-mono: "JetBrains Mono", "Fira Code", ui-monospace, monospace;142 --font-sans: "Inter", system-ui, -apple-system, sans-serif;143}144[data-theme="light"] {145 --bg: #f8fafc;146 --bg-card: #ffffff;147 --bg-card-hover: #f1f5f9;148 --text: #0f172a;149 --text-muted: #64748b;150 --border: #e2e8f0;151 --border-subtle: #f1f5f9;152 --critical-bg: #fef2f2;153 --warning-bg: #fffbeb;154 --info-bg: #eff6ff;155}156```157158**Typography and spacing:**159160```css161body {162 font-family: var(--font-sans);163 font-size: 14px;164 line-height: 1.6;165}166h1 {167 font-size: 1.5rem;168 font-weight: 700;169 letter-spacing: -0.02em;170}171h2 {172 font-size: 1.1rem;173 font-weight: 600;174 letter-spacing: -0.01em;175}176h3 {177 font-size: 0.9rem;178 font-weight: 600;179 text-transform: uppercase;180 letter-spacing: 0.08em;181 color: var(--text-muted);182}183code {184 font-family: var(--font-mono);185 font-size: 0.85em;186 padding: 0.1em 0.3em;187 border-radius: var(--radius-sm);188 background: var(--border-subtle);189}190pre {191 border-radius: var(--radius);192 padding: 1.25rem;193 overflow-x: auto;194 background: var(--bg-card);195 border: 1px solid var(--border);196}197pre code {198 background: none;199 padding: 0;200}201```202203**Finding card design — minimal, whitespace-forward:**204205```css206.finding {207 border-radius: var(--radius);208 border: 1px solid var(--border);209 padding: 1.25rem 1.5rem;210 margin-bottom: 1rem;211 background: var(--bg-card);212}213.finding-header {214 display: flex;215 align-items: center;216 gap: 0.5rem;217 margin-bottom: 0.75rem;218}219.badge {220 font-size: 0.7rem;221 font-weight: 700;222 letter-spacing: 0.06em;223 padding: 0.15rem 0.5rem;224 border-radius: 3px;225 text-transform: uppercase;226}227.badge-critical {228 background: var(--critical-bg);229 color: var(--critical);230}231.badge-warning {232 background: var(--warning-bg);233 color: var(--warning);234}235.badge-info {236 background: var(--info-bg);237 color: var(--info);238}239.finding-title {240 font-weight: 600;241 font-size: 0.95rem;242}243.finding-body {244 color: var(--text-muted);245 font-size: 0.875rem;246}247.finding-fix {248 margin-top: 0.75rem;249 padding-top: 0.75rem;250 border-top: 1px solid var(--border-subtle);251 font-size: 0.875rem;252}253```254255**HTML structure skeleton:**256257```html258<!DOCTYPE html>259<html lang="en" data-theme="dark">260 <head>261 ...262 </head>263 <body>264 <nav class="sidebar"><!-- section links --></nav>265 <main>266 <header><!-- agent, skill, timestamp, target --></header>267 <section id="summary">...</section>268 <section id="findings">...</section>269 <section id="metrics">...</section>270 <section id="diagrams">...</section>271 <section id="timeline">...</section>272 <section id="actions">...</section>273 </main>274 <script>275 /* theme toggle, copy buttons, mermaid init */276 </script>277 </body>278</html>279```280281### Step 3: Save and Open2822831. Save the HTML file to `{repo}/.reports/{agent}-{skill}-{YYYY-MM-DD-HHmm}.html`2842. Create the `.reports/` directory if it does not exist2853. Open the report in the default browser:286 - macOS: `open {path}`287 - Linux: `xdg-open {path}`288289### Step 4: Present CLI Summary290291```292╭─ ATLAS ── atlas-report ───────────────────────╮293294 ## Report generated295296 **Source:** {agent} / {skill}297 **Target:** {repo or service name}298 **Saved:** .reports/{agent}-{skill}-{YYYY-MM-DD-HHmm}.html299300 ### Contents301 - Executive Summary ({N} bullets)302 - Findings ({N} critical, {N} warning, {N} info)303 - Metrics ({N} tables)304 - Diagrams ({N} charts)305 - Actions ({N} next steps)306307 → Opened in browser308309╰────────────────────────────────────────────────╯310```311312## Key Rules313314- **Self-contained HTML** — the report must work offline (except Mermaid CDN for diagrams)315- **Never truncate findings** in the HTML report — this is where full detail lives; the CLI summary is the compressed version316- **Severity colors match output kit** — `■` red, `▲` amber, `● ` blue, consistent across CLI and HTML317- **Graceful Mermaid degradation** — if CDN is unreachable, diagrams fall back to styled code blocks318- **Omit empty sections** — do not render sections that have no content319- **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 tool320- **No copy buttons on inline code** — copy buttons on `<pre>` blocks only, hover-reveal only. Inline `<code>` never gets a copy button