Answers from the documentation; checking which model is on duty
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.
explaining-code - Skill - OpenSmartRoute
Skillv1.0.0
explaining-code
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
Imported from patricio0312rev/skills (foundation/explaining-code/SKILL.md) via skills.sh. Install upstream with npx skills add patricio0312rev/skills --skill explaining-code. Copyright stays with the author.
When explaining code, always include:
Start with an analogy: Compare the code to something from everyday life
Draw a diagram: Use ASCII art to show the flow, structure, or relationships
Walk through the code: Explain step-by-step what happens
Highlight a gotcha: What's a common mistake or misconception?
Keep explanations conversational. For complex concepts, use multiple analogies.
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 slotcurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install explaining-code and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
{
"ocm": "1",
"id": "patricio0312rev-skills-explaining-code",
"kind": "skill",
"name": "explaining-code",
"description": "Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks \"how does this work?\"",
"publisher": "patricio0312rev",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks \"how does this work?\""
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/patricio0312rev/skills",
"path": "foundation/explaining-code/SKILL.md",
"ref": "HEAD",
"url": "https://www.skills.sh/patricio0312rev/skills/explaining-code",
"key": "patricio0312rev/skills/foundation/explaining-code/SKILL.md"
}
},
"instructions": "When explaining code, always include:\n\n1. **Start with an analogy**: Compare the code to something from everyday life\n2. **Draw a diagram**: Use ASCII art to show the flow, structure, or relationships\n3. **Walk through the code**: Explain step-by-step what happens\n4. **Highlight a gotcha**: What's a common mistake or misconception?\n\nKeep explanations conversational. For complex concepts, use multiple analogies.",
"cost": {
"context_tokens": 103
}
}
Fetch it by URL: GET /api/v1/registry/patricio0312rev-skills-explaining-code/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.
