markdown-html-orchestrator
Use when a user wants to convert any markdown file in their Claude project into a single-file, lightly-interactive HTML — long-form documents (specs, plans, RFCs, reports, explainers), code reviews with diffs and severity-tagged annotations, or slide decks. Triggers on "convert this markdown to HTML", "make this an HTML file", "turn this into an interactive document", "render this report as HTML", "PR writeup as HTML", "slides from this markdown". Forks context to route to one of three converter sub-skills (md-document, md-review, md-slides) based on a deterministic doctype classifier, after t
Profile →npx skills add alirezarezvani/claude-skills --skill markdown-html-orchestrator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Markdown → HTML — Domain Orchestrator Thariq Shihipar's argument (Claude Code HTML output essay, Medium 2026): **markdown collapses past 100 lines for agent-generated artifacts.** Long specs, code reviews, and architecture explainers lose density, hierarchy, and lightweight interaction the moment they exceed a screen of text. HTML restores all three — single-file, browser-native, shareable. This orchestrator forks context, classifies the input markdown deterministically, routes to the right converter sub-skill, and returns a digest with the output path. Heavy intake (full markdown bodies, diffs, slide decks) stays in the forked context. **Domain status (complete):** all five skills are live — orchestrator + `design-system` (onboarding + shared brand tokens) + the three converter sub-skills (`md-document`, `md-review`, `md-slides`). Always route conversions to the shipped converter's scripts; never hand-render HTML inline. ## When to invoke | Symptom | Sub-skill | |---|---| | "Convert this RFC / spec / report / explainer to HTML" — long-form doc | `md-document` | | "Turn this PR writeup / code review into HTML" — markdown with diff blocks | `md-review` | | "Make a slide deck from
- When to invoke
- Pre-flight gates (hard refusals)
- Routing logic (deterministic)
- Signal table
- Step 5 — Hand off to the sub-skill
- Forcing-question library (Matt Pocock grill-with-docs pattern)
- Assumptions
- Non-goals
- Distinct from
- Output artifacts
- Anti-patterns (do not)
- References
python3 markdown-html/skills/markdown-html-orchestrator/scripts/doctype_classifier.py \ python3 markdown-html/skills/design-system/scripts/onboard.py python3 markdown-html/skills/markdown-html-orchestrator/scripts/output_path_resolver.py \
What does the markdown-html-orchestrator skill do?
Use when a user wants to convert any markdown file in their Claude project into a single-file, lightly-interactive HTML — long-form documents (specs, plans, RFCs, reports, explainers), code reviews with diffs and severity-tagged annotations, or slide decks. Triggers on "convert this markdown to HTML", "make this an HTML file", "turn this into an interactive document", "render this report as HTML", "PR writeup as HTML", "slides from this markdown". Forks context to route to one of three converter sub-skills (md-document, md-review, md-slides) based on a deterministic doctype classifier, after t
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill markdown-html-orchestrator --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 alirezarezvani/claude-skills, a repository with 23,791 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.