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.
check-compiler-errors - Skill - OpenSmartRoute
Skillv1.0.0
check-compiler-errors
Run compile and type-check commands and report failures
Imported from cursor/plugins (cursor-team-kit/skills/check-compiler-errors/SKILL.md) via skills.sh. Install upstream with npx skills add cursor/plugins --skill check-compiler-errors. Copyright stays with the author.
Check compiler errors
Trigger
Compile or type-check failures are blocking local validation or CI.
Workflow
Run the repo's compile and type-check commands.
Summarize errors by file and type.
Fix the highest-confidence issues first.
Re-run checks until clean or blocked.
Output
Current compile and type-check status
Error summary grouped by file and category
Fixes applied and remaining blockers
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://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/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 check-compiler-errors 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.
