HTML Research, Reports & Learning

HTML reports get read; markdown reports of the same length don't. Use HTML whenever the goal is for a human (often someone other than the user) to actually absorb information — concept explainers, status reports, incident reports, knowledge transfer.

Pre-flight — run BEFORE writing the artifact

Invoke html-skills:html-skills-listen (Skill tool) first; it is idempotent. If it returns a URL, inject it verbatim as window.__CLAUDE_SUBMIT_URL__ in the HTML you are about to write, ?t= query string included (a local, single-session loopback handshake — not a credential). If it reported web/sandbox mode, leave that line out; submitToClaude then falls back to clipboard mode.

When to use this skill

• "Summarize how X works"
• "Explain the Y system to me / to my team / to leadership"
• "Write up the incident from yesterday"
• "Weekly status update for my manager"
• "I want to learn about X — synthesize from the codebase + git history + web"
• "Prepare a technical brief on Z"
• Any time the goal is comprehension or sharing, not implementation