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.
better-stripe - Skill - OpenSmartRoute
Skillv1.0.0
better-stripe
Run pnpm run check:all before handing off changes. Fix failures without weakening gate policy, lowering coverage or Shadscan floors, or raising existing budgets.
Imported from FantasticDevHQ/better-stripe (AGENTS.md). Install upstream with npx skills add FantasticDevHQ/better-stripe. Copyright stays with the author.
Repository checks
Run pnpm run check:all before handing off changes. Fix failures without
weakening gate policy, lowering coverage or Shadscan floors, or raising existing
budgets. Repository policy is in repo-gates.config.json; baselines are in
gates/.
Release PR metadata
Keep Release Please's generated description and standalone notes delimiters intact.
Post review evidence in comments. When editing release notes, use the local
scripts/release-description.mjs build/check commands and preserve fresh acceptance
and evidence; see docs/releasing.md. Workflow success with Publish skipped is not
publication. Never replace a newer reviewed body with a stale local copy.
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 better-stripe 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.
