Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
explain-visually - Skill - OpenSmartRoute
Skillv1.0.0
explain-visually
Render an explanation as a diagram, comparison, trace with real values, or annotated code. Use when the user asks to have a concept, decision, flow, or code explained, or says they do not follow.
Imported from toy-crane/claude-code-playbook-template (.claude/skills/explain-visually/SKILL.md). Install upstream with npx skills add toy-crane/claude-code-playbook-template --skill explain-visually. Copyright stays with the author.
Explain Visually
Render the subject when a visual explanation is needed.
First decide whether one sentence fully answers the question. Rendering costs
the user's time, so when one sentence is enough, write it and stop.
Otherwise choose a form suited to the question: a diagram for structure, a table
for comparison, a trace with real numbers for a mechanism, or annotated code.
Check the available tools and use the best renderer the session provides. Use
text in the reply only when nothing in the session can draw.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "toy-crane-claude-code-playbook-template-explain-visually",
"kind": "skill",
"name": "explain-visually",
"description": "Render an explanation as a diagram, comparison, trace with real values, or annotated code. Use when the user asks to have a concept, decision, flow, or code explained, or says they do not follow.",
"publisher": "toy-crane",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Render an explanation as a diagram, comparison, trace with real values, or annotated code. Use when the user asks to have a concept, decision, flow, or code explained, or says they do not follow."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/toy-crane/claude-code-playbook-template",
"path": ".claude/skills/explain-visually/SKILL.md",
"ref": "fca086100fc315a1e63821587e3376f312da4f08",
"url": "https://github.com/toy-crane/claude-code-playbook-template/blob/fca086100fc315a1e63821587e3376f312da4f08/.claude/skills/explain-visually/SKILL.md",
"key": "toy-crane/claude-code-playbook-template/.claude/skills/explain-visually/SKILL.md"
}
},
"instructions": "# Explain Visually\n\nRender the subject when a visual explanation is needed.\n\nFirst decide whether one sentence fully answers the question. Rendering costs\nthe user's time, so when one sentence is enough, write it and stop.\n\nOtherwise choose a form suited to the question: a diagram for structure, a table\nfor comparison, a trace with real numbers for a mechanism, or annotated code.\n\nCheck the available tools and use the best renderer the session provides. Use\ntext in the reply only when nothing in the session can draw.",
"cost": {
"context_tokens": 130
}
}
Fetch it by URL: GET /api/v1/registry/toy-crane-claude-code-playbook-template-explain-visually/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
