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.
user-operations-skill - Skill - OpenSmartRoute
Skillv1.0.0
user-operations-skill
这是一个用于沉淀项目专属用户运营 skill 的项目，服务于原创 IP 陪伴型产品的冷启动、种子用户获取、IP 验证与 IP 到实体化的运营判断。
Imported from wuziyi0311-coder/user-operations-skill (AGENTS.md). Install upstream with npx skills add wuziyi0311-coder/user-operations-skill. Copyright stays with the author.
用户运营项目协作规则
项目定位
这是一个用于沉淀项目专属用户运营 skill 的项目，服务于原创 IP 陪伴型产品的冷启动、种子用户获取、IP 验证与 IP 到实体化的运营判断。
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 user-operations-skill 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.
