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.
gather-context - Skill - OpenSmartRoute
Skillv1.0.0
gather-context
Gathers context before implementing a task by identifying relevant files, rules, and edge cases. Use for any non-trivial change.
Imported from katiecha/katie-chai (.claude/skills/gather-context/SKILL.md). Install upstream with npx skills add katiecha/katie-chai --skill gather-context. Copyright stays with the author.
Context Gathering
Used when retrieval is needed before implementation.
If a file cannot be found → note as gap, check for renames/moves
If pattern is ambiguous → list multiple interpretations, ask for clarification
If prerequisites are missing → stop and list what's needed
If gaps remain after retrieval → explicitly state "NOT READY" with blockers
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://api.opensmartroute.ai/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 gather-context 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.