html
Installation
SKILL.md
HTML Artifact
Turn complex agent output into a single self-contained HTML file a human will actually read. The goal is not a pretty page — it is a clear artifact. Structure before style. Reading before interaction.
This skill follows one rule: Markdown when the idea is still being shaped. HTML when the idea needs to be understood by a human — reviewed, compared, or shared.
When to use HTML vs Markdown
Reach for an HTML artifact when the output is something a person needs to read once and understand:
| Use Markdown for | Use HTML for |
|---|---|
| Notes, raw plans, scratch thinking | Reports, explainers |
| Source-of-truth files Claude re-reads | Code reviews, design comparisons |
| Project memory, docs edited many times | Decision pages, visual plans, prototypes |
| Anything still being shaped | Stakeholder summaries, anything someone else reads |
Do not turn everything into HTML — that gets messy. Write the source clearly (Markdown), then produce HTML when the output needs to be read, reviewed, or shared. When work belongs in a repo, keep the Markdown source and treat HTML as the presentation layer.