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.
demo-present - Skill - OpenSmartRoute
Skillv1.0.0
demo-present
Passing member: this directory exists, has a SKILL.md, and references the family contract path docs/reference/skill-families/demo-family-contract.md so the contract-reference branch passes.
Imported from product-on-purpose/pm-skills (scripts/fixtures/family-registration/repo/skills/demo-present/SKILL.md). Install upstream with npx skills add product-on-purpose/pm-skills --skill demo-present. Copyright stays with the author.
Demo present member (fixture)
Passing member: this directory exists, has a SKILL.md, and references the family
contract path docs/reference/skill-families/demo-family-contract.md so the
contract-reference branch passes.
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 demo-present 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.