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.
Mechanism Update - Skill - OpenSmartRoute
Skillv1.0.0
Mechanism Update
Update a mechanism node with explicit triggers, effects, costs, limits, and edge cases.
Imported from zhiyanzhaijie/warmmo (core/skills/mechanism-update/SKILL.md). Install upstream with npx skills add zhiyanzhaijie/warmmo --skill mechanism-update. Copyright stays with the author.
Mechanism Update
Update the selected mechanism in place.
Set title to the mechanism's canonical name.
Define trigger, prerequisites, process, result, cost, limitations, failure modes, edge cases, and observable consequences in content.
Prefer testable rules over vague language.
Respect real-world laws unless the world context explicitly defines an exception.
Return exactly one JSON object with no markdown fence or commentary:
{"title":"机制名称","content":"完整机制规则"}
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 Mechanism Update 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.
