Agent skill · software engineering · jeremylongshore
atlas-report
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.
Why this skill is useful
Adds a complete HTML report generation script with specific styling and interactive features that the AI cannot generate on its own.
What it needs
Requires mermaid installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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): 1. Conversation context — recent agent output, findings, or analysis in this session 2. Explicit request — user specifies a file, skill output, or topic 3. 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. 1. Header — agent name, skill name, timestamp, target repo/service 2. Executive Summary — 3-5 bullet points capturing the key takeaways 3. Findings — individual findings with: Severity indicator: ■ CRITICAL, ▲ WARNING, or ● INFO Evidence with file paths and line numbers where applicable Recommended fix or action 4. Metrics — tables, comparisons, scores, counts (e.g., dependency counts, coverage percentages, cost breakdowns) 5. Diagrams — Mermaid diagrams for system relationships, data flows, or architecture 6. Timeline — chronological events (useful for audits, incidents, migration histories) 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/atlas-report