alirezarezvani/claude-skills / markdown-html/skills/markdown-html-orchestrator
markdown-html-orchestrator
VerifiedUse when the user wants a markdown file turned into a single-file interactive HTML page (document, code review or slide deck). Classifies it with doctype_classifier.py and routes to md-document, md-review or md-slides.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.5 KB |
| references/information_density_canon.md | markdown | 4.0 KB |
| references/orchestrator_routing_patterns.md | markdown | 4.0 KB |
| references/single_file_html_discipline.md | markdown | 5.2 KB |
| scripts/doctype_classifier.py | script | 9.3 KB |
| scripts/output_path_resolver.py | script | 6.3 KB |
| scripts/route_explainer.py | script | 6.1 KB |
references/orchestrator_routing_patterns.md
View on GitHub# Orchestrator Routing Patterns
**Why this exists:** The two-signal routing discipline (silent-route only above a confidence threshold; otherwise ask one question with a recommended answer) is not original to this plugin. It's been established in the research-ops, commercial, and business-operations domains. This document records the canon so the orchestrator never silently chains or guesses below threshold.
## The pattern
Three discrete behaviors based on the classifier's score:
1. **Silent route** — winner ≥ 3 points AND (runner-up = 0 OR winner ≥ 2× runner-up). Hand off to the sub-skill without asking.
2. **Clarify** — winner ≥ 2 points but ratio against runner-up is too close. Ask ONE question, recommend the winner, take the user's confirmation or override.
3. **Ambiguous** — no signals matched. Ask which lane, default to md-document if the user shrugs.
Filename hint counts double (2 points each) because filename is high-signal user intent — a file named `pr-review.md` is almost certainly a code review.
## Sources
### 1. research-ops/skills/research-ops-skills/SKILL.md §"Routing logic (deterministic)"
The two-signal threshold pattern formalized: "Same two-signal threshold pattern as `commercial-skills`. Single-signal → clarifying question. Mixed signals → highest-confidence first, chain second in a follow-up turn. Never silently chain."
### 2. commercial/skills/commercial-skills/SKILL.md
First domain to ship the explicit "never silently chain" rule, with named signal classes (PRICING / DEAL / PARTNERSHIPS / RFP / FORECAST). The discipline is independent of subject matter — same shape for research, for commercial deals, for markdown docs.
### 3. business-operations/skills/business-operations-skills/SKILL.md
The "explore the workspace first" pattern: filenames like `vendor-list.csv` or `sla-tracker.xlsx` resolve the lane without asking. Filename hint = 2 points is calibrated here.
### 4. Matt Pocock — *grill-with-docs* (engineering/grill-with-docs/SKILL.md, MIT)
Five rules formalized:
1. One question per turn — never bundle.
2. Always recommend an answer with citation-backed rationale.
3. Explore before asking.
4. Walk the decision tree depth-first.
5. Track dependencies (don't ask Q3 before Q1's answer determines whether Q3 applies).
### 5. Anthropic — `context: fork` (SKILL.md frontmatter)
The mechanism that makes orchestrator routing efficient: forked sub-skills run in isolated context, so the parent thread doesn't bloat with the full markdown body, the diff hunks, or the slide bodies. Documented in research-ops, commercial, and business-operations orchestrators.
### 6. The "never silently chain" hard rule
Originates from research-ops Sprint 1 design (`documentation/implementation/research-ops-expansion-plan.md`). The rule prevents the worst orchestrator failure mode: routing to two sub-skills in sequence without explicit user acknowledgment of the chain. Markdown-html applies it: "convert this markdown to HTML and also make slides from it" is two operations, asked explicitly.
### 7. NN/g — *Defaults Are the Best Friend of UX* (Jakob Nielsen, 2007)
Recommended answers in clarifying questions reduce decision fatigue. The orchestrator never asks an open question — every clarification ships with "Recommended: <answer>, because <rationale>" so the user can just say "yes."
## Applied to markdown-html
The classifier produces a `total_scores` dict. The orchestrator's decision tree:
```
if below_min_lines: → REFUSE (Shihipar 100-line rule)
elif not setup_completed_at: → REFUSE (point at onboarding)
elif winner_score == 0: → ASK_USER (lane + recommend md-document)
elif silent_route_allowed: → ROUTE_SILENTLY to md-<winner>
elif winner_score >= 2: → ASK_USER (recommend md-<winner>)
else: → ASK_USER (treat as md-document by default)
```
Never two routes in one turn. Never "I'll just do both."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |