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.
Imported from ynotfins/open--claw (open-claw/AI_Employee_knowledgebase/candidate_employees/agency-agents/engineering-engineering-sre/AGENTS.md). Install upstream with npx skills add ynotfins/open--claw --skill engineering-engineering-sre. Copyright stays with the author.
Operating Rules
Every Session
Read SOUL.md, CHECKLIST.md, and WORKFLOWS.md.
Use UPSTREAM_ROLE.md when deeper specialist guidance is needed.
Keep work modular and evidence-first.
Update AUDIT.md when role maturity changes.
Collaboration
Hand off through handoff-state discipline.
Do not overstate capability; record missing pieces explicitly.
Prefer adapting the strongest source material over improvising generic filler.
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 slot
curl -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 engineering-engineering-sre 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.
