| name | glyph |
| license | MIT |
| compatibility | Claude Code 2.1.220+. |
| description | Render an answer as ASCII art plus semantic emojis inline, right now, with no setup questions. Use for a fast visual take on status, comparisons, trade-offs, architecture, or any ad-hoc 'show me X visually' ask. For a full multi-artifact plan playground, use visualize-plan instead. |
| tags | ["ascii","diagrams","visualization","box-drawing","terminal","quick"] |
| version | 2.0.0 |
| author | OrchestKit |
| user-invocable | true |
| disable-model-invocation | false |
| context | inherit |
| allowed-tools | ["Read","Grep","Glob"] |
| argument-hint | [topic-to-render] |
| complexity | low |
| persuasion-type | reference |
| effort | low |
| metadata | {"category":"document-asset-creation"} |
Glyph
Render the answer as ASCII art plus semantic emojis, inline, immediately. All output renders in a monospace terminal with no external tools.
Core principle: Encode information into structure, not decoration. Every diagram element should communicate something meaningful.
Execution (run this, do not ask first)
The whole point is speed, so there is no setup phase.
With no argument, the topic is the current conversation. Measured over a real 13-prompt session: zero asks supplied a self-contained topic, and the one direct invocation passed nothing at all. /ork:glyph on its own means "render where we are right now" โ the open work, the decision just reached, the state of the thing being discussed. Render that; do not ask what to draw.
Given a topic (or the conversation, when none is given):
-
Render immediately. Do NOT call AskUserQuestion to pick a format, do NOT call TaskCreate, do NOT spawn an Agent. Choose the form yourself from the topic shape and draw it. Asking first defeats the skill.
-
Pick the form from the shape of the data, using the pattern library below:
| Topic shape | Form |
|---|
| state / progress / health | status box + bar meters |
| A vs B, options, trade-offs | comparison table or side-by-side boxes |
| steps, pipeline, hand-offs | left-to-right flow with โโโถ |
| containment, layers, layout | nested boxes / tree |
| ranked list, scores, counts | table + bar meters |
| over time | sparkline or milestone track |
-
Emit inline in the reply. Never write a file unless the user asked for one. This is a chat answer, not an artifact.
-
Use the 12-emoji semantic set and box-drawing vocabulary defined in rules/visual-style.md (shipped with this skill). Semantic, never decorative: an emoji must mean something (โ
pass, โ fail, โ ๏ธ risk, ๐ด blocked).
-
Lead with the answer. The visual comes first; prose after it only if it adds something the diagram cannot carry.
-
Stay honest. If a number is unknown, print rather than inventing one. A confident-looking chart built on guesses is worse than prose.
