Visual Artifact Router
Choose the artifact pipeline and enforce its completion gate. Do not author document content,
style a diagram, or implement a renderer in this skill.
Route
- Read routing-policy.md and classify the requested outcome,
style intent, editability needs, and final formats.
- Prefer plain text or a table when either communicates the relationship more clearly than a
diagram. Record
diagram: none instead of generating decorative visuals.
- Select the smallest sufficient pipeline:
- Editable document:
document-designer -> markdown-publisher
- PDF document:
document-designer -> markdown-publisher -> pdf-qa
- Structural or process diagram:
mermaid-diagrams -> diagram-styler
- Rendered diagram: append the relevant rendered-output inspection gate.
- Whiteboard or hand-drawn intent: route only to an installed
excalidraw-diagrams skill.
- Precise branded architecture: route only to an installed SVG architecture renderer.
- If an optional renderer is unavailable, preserve an editable semantic brief and report the
missing capability. Do not silently substitute a visually different format or install a
dependency.
- Give every selected skill explicit input paths, output paths, target format, theme intent, and
completion evidence. Keep semantic generation separate from styling and rendering.
- Apply artifact-contract.md to the assembled result.
Completion gate
For source-only Markdown or Mermaid, validate structure and syntax before delivery. For PDF,
SVG, PNG, or other rendered output, require this loop:
Generate -> Render -> Inspect -> Fix -> Re-render
Do not mark a rendered artifact complete from source generation or a successful renderer exit
alone. Completion requires inspected final output with no obvious clipping, overlap, broken
glyph, unreadable scale, inconsistent spacing, or pagination defect. A failed or unavailable QA
stage is a blocker, not a warning.
Output
Return a route record containing:
- requested outputs and selected skills in execution order
- editable source-of-truth paths and derived artifact paths
- chosen format and theme, with the routing reason
- renderer and runtime dependencies actually used
- inspection evidence, unresolved issues, and
pass, revise, or blocked
Never claim that a deferred optional skill ran. Never discard editable sources after rendering.
1---2name: visual-artifact-router3description: Route requests for polished Markdown, HTML, PDF, Mermaid, SVG, PNG, and technical diagrams to the smallest suitable visual-artifact workflow. Use when the agent must choose a document or diagram format, preserve editable sources, attach render-based QA, or decide whether a diagram adds value. Do not use for ordinary prose where visual publishing is not requested or useful.4---56# Visual Artifact Router78Choose the artifact pipeline and enforce its completion gate. Do not author document content,9style a diagram, or implement a renderer in this skill.1011## Route12131. Read [routing-policy.md](references/routing-policy.md) and classify the requested outcome,14 style intent, editability needs, and final formats.152. Prefer plain text or a table when either communicates the relationship more clearly than a16 diagram. Record `diagram: none` instead of generating decorative visuals.173. Select the smallest sufficient pipeline:18 - Editable document: `document-designer` -> `markdown-publisher`19 - PDF document: `document-designer` -> `markdown-publisher` -> `pdf-qa`20 - Structural or process diagram: `mermaid-diagrams` -> `diagram-styler`21 - Rendered diagram: append the relevant rendered-output inspection gate.22 - Whiteboard or hand-drawn intent: route only to an installed `excalidraw-diagrams` skill.23 - Precise branded architecture: route only to an installed SVG architecture renderer.244. If an optional renderer is unavailable, preserve an editable semantic brief and report the25 missing capability. Do not silently substitute a visually different format or install a26 dependency.275. Give every selected skill explicit input paths, output paths, target format, theme intent, and28 completion evidence. Keep semantic generation separate from styling and rendering.296. Apply [artifact-contract.md](references/artifact-contract.md) to the assembled result.3031## Completion gate3233For source-only Markdown or Mermaid, validate structure and syntax before delivery. For PDF,34SVG, PNG, or other rendered output, require this loop:3536`Generate -> Render -> Inspect -> Fix -> Re-render`3738Do not mark a rendered artifact complete from source generation or a successful renderer exit39alone. Completion requires inspected final output with no obvious clipping, overlap, broken40glyph, unreadable scale, inconsistent spacing, or pagination defect. A failed or unavailable QA41stage is a blocker, not a warning.4243## Output4445Return a route record containing:4647- requested outputs and selected skills in execution order48- editable source-of-truth paths and derived artifact paths49- chosen format and theme, with the routing reason50- renderer and runtime dependencies actually used51- inspection evidence, unresolved issues, and `pass`, `revise`, or `blocked`5253Never claim that a deferred optional skill ran. Never discard editable sources after rendering.
ch4570