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.
pua-p10 - Skill - OpenSmartRoute
Skillv1.0.0
pua-p10
PUA P10 alias for Codex. Codex subcommand mapping for Claude Code /pua:p10 style usage; invoke with $pua-p10.
Imported from tanweai/pua (codex/pua-p10/SKILL.md). Install upstream with npx skills add tanweai/pua --skill pua-p10. Copyright stays with the author (MIT).
pua-p10
This is a Codex CLI alias for the Claude Code /pua:p10 command.
Load and follow the p10 skill/protocol. Operate as P10/CTO: define strategic direction, org topology, and P9 management boundaries.
When this alias changes ~/.pua/config.json, preserve unknown fields and create ~/.pua/ if missing. Do not claim completion without command/output evidence.
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 pua-p10 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.
