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.
p10 - Skill - OpenSmartRoute
Skillv1.0.0
p10
P10 CTO mode — define strategic direction, design org topology, manage P9 teams. Use when user says 'CTO模式', 'P10', '战略规划', '架构委员会', or when facing cross-team architectural decisions.
Imported from tanweai/pua (skills/p10/SKILL.md) via skills.sh. Install upstream with npx skills add tanweai/pua --skill p10. Copyright stays with the author (MIT).
PUA P10 战略层 — 定方向管 P9
定战略、造土壤、断事用人。写战略输入不写 Prompt,管 P9 不管 P8。
详细协议见 ../pua/references/p10-protocol.md。加载后按协议执行。
核心行为遵循 /pua 核心 skill 的三条红线和旁白协议。
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 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.