Skip to content
Conduit

skill

human-html

Agent Skill: HTML review surfaces humans actually read. Nine kinds plus a dynamic mode for when the shape is the argument, a validated content contract, an offline validator that can render your page

rhnfzl/human-htmlcommunitylistedunreviewed

Set up

Skills are installed by placing their folder where your agent loads skills.

The download comes from github.com/rhnfzl/human-html itself, not from our server, so what you get is exactly what its author published.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below.

README

synced Oct 14, 2026

human-html

skills.sh Release License

An Agent Skill for the documents an agent writes for a person, plans, reviews, postmortems, architecture explainers, decisions. Each one lands as a single self-contained HTML page instead of a Markdown wall, and an offline validator holds it to that shape.

npx skills add rhnfzl/human-html

That auto-detects your installed agents. Then ask for a plan, or a review, or a postmortem.

It is a standard Agent Skill, native in Claude Code, Codex, Cursor and ten others, and covered by the universal installers everywhere else.

Every one of them opens the same way

That is the part worth having. You are not scrolling to find where the risks went, they are where they were last time, and so is the summary and so is the rollback. It pays off hardest on anything recurring: when this week's status report looks like last week's, the difference is what stands out.

Nine kinds, each with its own sections and a worked example:

KindThe reader wants to
planexecute: outcome, sequence, risks, rollback
reviewinspect a change: verdict first, concerns ranked
architectureunderstand a proposed change to system shape
understandingunderstand how something works today
researchlearn what the digging found
decisiondecide: options, consequences, reversibility
prototypefeel a proposed thing before it exists
statuscatch up: where we are, blockers, next
incidentlearn from failure: timeline, root cause, actions

Except when the shape is the argument

A findings taxonomy, a four-way design exploration, a line-by-line map of a port. Each of those has a natural shape that carries part of what it is saying, and forcing it into plan sections makes the document worse. So the shape can be the agent's call instead:

python3 <skill-dir>/human_html_artifacts.py new review "Blindspot pass on RFC 214" --mode dynamic

One question decides which you want, does the reader benefit from this looking like the last one? Yes means use a kind, because comparability is the whole payoff. No means go dynamic. Unclear means use the kind, since a kind that fits slightly badly costs a reader less than an invented structure that fits nothing.

Structure is the agent's, style is not. Dynamic mode stands down three rules, all of them about which sections exist. Nothing aimed at the reader is relaxed: it still renders on a phone, still exists with JavaScript off, still answers first, still puts a real visual in every comparison.

How it differs

  • The shape is a contract, not an intention. Style guidance evaporates the moment an agent regenerates a file. check runs offline, blocks on four rules, warns on the rest, and every rule is suppressible per artifact.
  • The checks are markers, not proofs. artifact-spine.md says what each one does and does not establish, next to the standard no validator can reach.
  • Local unless you say otherwise. No telemetry, no phone-home, no postinstall scripts, no network calls in the core loop. Sharing is a menu: GitHub Pages, an optional bring-your-own-bucket S3 script, or any static host.
  • An agent can see its own output. render screenshots through headless Chrome, and render --no-js shows what an iOS Quick Look or email preview sees. First time it ran, it found a broken static floor in this repo's own prototype example, hidden behind a rule that reported clean.

references/ holds the patterns worth stealing on their own, whether or not you use the rest: a pre-merge self-check for a review attached to a PR (never scored, never a gate), open questions routed with an owner, a date, and where they land if nobody answers, non-goals, and a files-read list carrying the revision it was read at, so staleness is one git diff away.

The contract is stolen craft in the Steal Like an Artist sense: the inverted pyramid, postmortem timelines, C4 diagrams, first-use glossing. The examples exist to be stolen from too, and so does the repo. Fork it, re-theme it, suppress what you disagree with.

Python 3.11+ is all you need, tested on 3.11, 3.12 and 3.13.

Optional hooks, an advisory nudge and a gallery autoindex, both advisory-only and always exit 0:

python3 <skill-dir>/activate_hooks.py

That merges with existing settings for Claude Code, Codex, Cursor and Windsurf, and is safe to rerun. Replace <skill-dir> with the path your installer reports, commonly ~/.agents/skills/human-html.

Other routes:

  • npx openskills install rhnfzl/human-html for AGENTS.md ecosystems
  • Claude Code natively: /plugin marketplace add rhnfzl/human-html, then /plugin install human-html@rhnfzl
  • Manual: clone and symlink skills/human-html/ into your agent's skills directory
  • The CLI directly: python3 <skill-dir>/human_html_artifacts.py new|check|index|render|embed-svg|deps

Optional tools, each one adds something rather than gating anything. Run deps to see what is present.

ToolEnables
jqthe two hooks, which no-op silently without it
mmdcMermaid rendered to inline SVG, for a fully offline artifact
excalidraw-mcphand-drawn diagrams

Mermaid otherwise loads a CDN at view time, so use embed-svg for artifacts that must work offline.

A standard Agent Skill, so it works anywhere that reads the format. Native, meaning SKILL.md auto-loads with no installer: Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Zed, Amp, Warp, Kiro, Crush, Qwen Code, Pi. Everything else is covered by the universal installers, which target 70+ agents including Windsurf, Cline and Aider.

Inside: SKILL.md is the contract, examples/ holds twelve warning-free artifacts (nine kinds plus three dynamic ones that share no structure on purpose), references/ holds the spine, the patterns, the diagram decision tree and workflow integrations, and tests/ holds 95 stdlib unittest tests (python3 -m unittest discover -s tests).

As with any skill, read skills/human-html/SKILL.md before installing.

License

MIT

↑↓ navigate openesc close