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.
rubocop-neeto - Skill - OpenSmartRoute
Skillv1.0.0
rubocop-neeto
See LLM-shared.md (local | GitHub) for shared Neeto ecosystem context (NeetoZone, engines, and nanos).
Imported from neetozone/rubocop-neeto (AGENTS.md). Install upstream with npx skills add neetozone/rubocop-neeto. Copyright stays with the author.
LLM-shared
See LLM-shared.md (local | GitHub) for shared Neeto ecosystem
context (NeetoZone, engines, and nanos).
Pull requests
After you open a pull request, run the neeto:respond-to-bugwatch skill on it without waiting to be asked. It waits for NeetoBugWatch and Greptile, fixes valid comments, replies, and resolves threads. Do not merge or add labels.
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 rubocop-neeto 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.
