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.
Imported from zernie/vigiles (bench/tdd/isodd/SKILL.md). Install upstream with npx skills add zernie/vigiles --skill isodd. Copyright stays with the author.
Implement isOdd (test-driven)
Implement isOdd(n) in src/isodd.js as a named ESM export. It returns whether
an integer is odd.
Follow test-driven development, in this order:
First write a failing test in test/isodd.test.js.
Then implement src/isodd.js to make the test pass.
Do not write the implementation before the test exists and fails.
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}'
Installed into a catalogue, chosen by a router
Install implement-is-odd 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.
