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.
Claude Code Skill (Slash Command): review-and-commit.md - Persona - OpenSmartRoute
Personav1.0.0
Claude Code Skill (Slash Command): review-and-commit.md
--- allowed-tools: Bash(git add:), Bash(git status:), Bash(git commit:) description: Create a git commit --- ## Context - Current git status: !git status - Current git diff (staged and unstage...
Role from Awesome ChatGPT Prompts (prompts.csv, CC0-1.0). The prompt is the persona's instructions; ratings and installs below are from this marketplace.
Current git diff (staged and unstaged changes): !git diff HEAD
Current branch: !git branch --show-current
Recent commits: !git log --oneline -10
Your task
Review the existing changes and then create a git commit following the conventional commit format. If you think there are more than one distinct change you can create multiple commits.
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 Claude Code Skill (Slash Command): review-and-commit.md 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.
