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.
orbit - Skill - OpenSmartRoute
Skillv1.0.0
orbit
Issues and tickets live in GitHub Issues for taekwondodev/orbit. See docs/agents/issue-tracker.md.
Imported from taekwondodev/orbit (AGENTS.md). Install upstream with npx skills add taekwondodev/orbit. Copyright stays with the author.
Dev cycle
Issue tracker
Issues and tickets live in GitHub Issues for taekwondodev/orbit. See docs/agents/issue-tracker.md.
Issue labels
Category (bug/enhancement), readiness (needs-grilling/ready-for-agent) and activity (parked/in-flight). See docs/agents/triage-labels.md.
Delivery
Direct push to main by default. Before implementation or delivery, read docs/agents/delivery.md for route and target defaults.
Domain docs
Single-context: GLOSSARY.md and docs/adr/ at the repo root. See docs/agents/domain.md.
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 orbit 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.
When a provider is down or over quota the request moves on; the trace says it did.
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
taekwondodev-orbit-orbit.ocm.jsonjson
{
"ocm": "1",
"id": "taekwondodev-orbit-orbit",
"kind": "skill",
"name": "orbit",
"description": "Issues and tickets live in GitHub Issues for `taekwondodev/orbit`. See `docs/agents/issue-tracker.md`.",
"publisher": "taekwondodev",
"version": "1.0.0",
"capabilities": {
"domains": [
"customer_support",
"coding"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Issues and tickets live in GitHub Issues for `taekwondodev/orbit`. See `docs/agents/issue-tracker.md`."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/taekwondodev/orbit",
"path": "AGENTS.md",
"ref": "7c0d16cb55e4af637deb3ddcd3469b20bca02330",
"url": "https://github.com/taekwondodev/orbit/blob/7c0d16cb55e4af637deb3ddcd3469b20bca02330/AGENTS.md",
"key": "taekwondodev/orbit/AGENTS.md"
}
},
"instructions": "## Dev cycle\n\n### Issue tracker\n\nIssues and tickets live in GitHub Issues for `taekwondodev/orbit`. See `docs/agents/issue-tracker.md`.\n\n### Issue labels\n\nCategory (`bug`/`enhancement`), readiness (`needs-grilling`/`ready-for-agent`) and activity (`parked`/`in-flight`). See `docs/agents/triage-labels.md`.\n\n### Delivery\n\nDirect push to `main` by default. Before implementation or delivery, read `docs/agents/delivery.md` for route and target defaults.\n\n### Domain docs\n\nSingle-context: `GLOSSARY.md` and `docs/adr/` at the repo root. See `docs/agents/domain.md`.",
"cost": {
"context_tokens": 140
}
}
Fetch it by URL: GET /api/v1/registry/taekwondodev-orbit-orbit/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.