Agent skill · Testing & QA

html-summary

Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette and self-contained mermaid diagrams. Use when the user wants to turn a stakeholder summary, executive summary, or business summary into an HTML report, generate an HTML version of a summary doc, or produce a shareable HTML file from a summary markdown. Produces an HTML sibling file only; does not publish anything.

testdoublegithub.com/testdoubleGitHub ↗
claude-codecan modify filesships scriptsMIT
Install
npx skills add testdouble/han --skill html-summary --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 8
SKILL.md size: 11 KB
Bundled scripts: yes
Allowed tools: ReadWrite
Path: han-reporting/skills/html-summary/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 154
Language: Shell

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Project Context - personal config directory: !`echo "${CLAUDE_CONFIG_DIR:-$HOME/.claude}"` - project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""` As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md` probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used. # HTML Summary Convert a stakeholder summary markdown file into a single self-contained HTML report tailored for executive readers — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette. The skill produces one HTML file next to the source markdown and stops there. ## Inputs - **Source markdown file** — usually a `stakeholder-summary.md` inside a planning folder. If the user does not name one, ask. Do not guess. ## Output - **HTML sibling file** — written next to the source markdown, same basename, `.html` extension. Exa

What's inside
Steps it walks through
  1. Project Context
  2. Inputs
  3. Output
  4. Hard rules
  5. Process
  6. 1. Locate the source markdown
  7. 2. Read the source end-to-end
  8. 3. Load the references
  9. 4. Produce the HTML
  10. 5. Verify the HTML
  11. 6. Inline the mermaid bundle
  12. 7. Report
Ships with 7 files
  • assets/.gitattributes
  • assets/mermaid.min.js
  • references/html-template.html
  • references/layout-principles.md
  • references/report-style.md
  • references/writing-conventions.md
  • scripts/inline-mermaid.sh
More from han
All skills →
About this skill
What does the html-summary skill do?

Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette and self-contained mermaid diagrams. Use when the user wants to turn a stakeholder summary, executive summary, or business summary into an HTML report, generate an HTML version of a summary doc, or produce a shareable HTML file from a summary markdown. Produces an HTML sibling file only; does not publish anything.

How do I install it?

Run `npx skills add testdouble/han --skill html-summary --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From testdouble/han, a repository with 154 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going