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.
store-data-structures - Skill - OpenSmartRoute
Skillv1.0.0
store-data-structures
Explicit compatibility entry for Zustand data-shape guidance.
Imported from lobehub/lobehub (.agents/skills/store-data-structures/SKILL.md) via skills.sh. Install upstream with npx skills add lobehub/lobehub --skill store-data-structures. Copyright stays with the author.
Store Data Structures
Read Zustand data structures for
list/detail types, maps, reducers and shared type sources. The zustand skill
is the automatic entry for store work.
A domain whose reads go through local-replica keeps its data in the same
id-keyed <domain>Map views, plus one <domain>Replica bookkeeping field per
view; its resources live in a sibling projection.ts. See
replica-backed server data.
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://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/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 store-data-structures 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.
