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.
keelson - Skill - OpenSmartRoute
Skillv1.0.0
keelson
Engineering control plane for coding work in repositories with a .keelson/ directory. Use for exploring an idea, changing code, fixing/debugging, frontend design and UX review, continuing prior work,
Imported from Atingaii/keelson (tests/fixtures/v0.4-runtime/0.4.1/en/SKILL.md). Install upstream with npx skills add Atingaii/keelson --skill en. Copyright stays with the author.
Keelson
This is a discovery shim, not the source of truth. Run keelson guide now and follow it; for a routed topic run keelson guide <reference>. Use keelson init --vendor only when this project needs a checked-in copy of the guidance.
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.
atingaii-keelson-en.ocm.jsonjson
{
"ocm": "1",
"id": "atingaii-keelson-en",
"kind": "skill",
"name": "keelson",
"description": "Engineering control plane for coding work in repositories with a .keelson/ directory. Use for exploring an idea, changing code, fixing/debugging, frontend design and UX review, continuing prior work, or improving recurring engineering failures. Keeps conversation sessions separate from durable work items so users can keep asking questions without having to announce when a task starts or ends.",
"publisher": "Atingaii",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Engineering control plane for coding work in repositories with a .keelson/ directory. Use for exploring an idea, changing code, fixing/debugging, frontend design and UX review, continuing prior work, or improving recurring engineering failures. Keeps conversation sessions separate from durable work items so users can keep asking questions without having to announce when a task starts or ends."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/Atingaii/keelson",
"path": "tests/fixtures/v0.4-runtime/0.4.1/en/SKILL.md",
"ref": "fa270c63103c6be722c8e3e8fdad47d7be3174db",
"url": "https://github.com/Atingaii/keelson/blob/fa270c63103c6be722c8e3e8fdad47d7be3174db/tests/fixtures/v0.4-runtime/0.4.1/en/SKILL.md",
"key": "Atingaii/keelson/tests/fixtures/v0.4-runtime/0.4.1/en/SKILL.md"
}
},
"instructions": "# Keelson\n\nThis is a discovery shim, not the source of truth. Run `keelson guide` now and follow it; for a routed topic run `keelson guide <reference>`. Use `keelson init --vendor` only when this project needs a checked-in copy of the guidance.",
"cost": {
"context_tokens": 61
}
}
Fetch it by URL: GET /api/v1/registry/atingaii-keelson-en/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.