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.
review - Skill - OpenSmartRoute
Skillv1.0.0
review
Code review with spec compliance and quality checks. Activate when user says: review this, code review, review my changes.
Imported from zereight/gitlab-mcp (.github/skills/review/SKILL.md). Install upstream with npx skills add zereight/gitlab-mcp --skill review. Copyright stays with the author.
Review
Systematic code review with severity-rated feedback.
Modes
Default: Full two-stage review (spec compliance + code quality)
--style: Lightweight style-only checks
--performance: Performance analysis and hotspot identification
--quality: Release readiness and quality gate assessment
Workflow
Delegate to @code-reviewer for spec compliance + code quality
Delegate to @security-reviewer for vulnerability detection
Compile findings with severity ratings
Output
Issues rated: CRITICAL / HIGH / MEDIUM / LOW
Each issue includes file:line, description, and fix suggestion
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 review 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.