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.
pr-description - Skill - OpenSmartRoute
Skillv1.0.0
pr-description
Write a clear pull request description from code changes, commits, or a user-provided summary.
Imported from ErnestKostevich/horizon-genesis (builtin-skills/pr-description/SKILL.md). Install upstream with npx skills add ErnestKostevich/horizon-genesis --skill pr-description. Copyright stays with the author.
Pull request description
Use this skill when the user needs a PR body or changelog.
Procedure
Determine the base branch and changed files if available.
Group changes by user-visible behavior, not by file name.
Mention tests run and tests not run.
Avoid claiming deploys, screenshots, or tests that were not actually performed.
Template
## Summary
- ...
## Tests
- ...
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 pr-description 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.
