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.
sample-plugin - Skill - OpenSmartRoute
Skillv1.0.0
sample-plugin
Phase 1 sample plugin synthesizing a SKILL.md frontmatter for backwards-compat tests.
Imported from nexu-io/open-design (apps/daemon/tests/fixtures/plugin-fixtures/sample-plugin/SKILL.md). Install upstream with npx skills add nexu-io/open-design --skill sample-plugin. Copyright stays with the author.
Sample Plugin
This is the SKILL.md half of the Phase 1 e2e fixture. The companion
open-design.json sidecar carries the canonical OpenDesign plugin
manifest fields; this file proves the SKILL-only adapter path stays
honest when an install lacks an explicit sidecar (just delete
open-design.json to test the legacy compat tier).
Workflow
Acknowledge the user's brief via the discovery question form atom.
Use TodoWrite to plan the brief.
Emit the brief as a deck artifact.
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 sample-plugin 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.
