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.
continual-learning - Skill - OpenSmartRoute
Skillv1.0.0
continual-learning
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to agents-memory-updater.
Imported from cursor/plugins (continual-learning/skills/continual-learning/SKILL.md) via skills.sh. Install upstream with npx skills add cursor/plugins --skill continual-learning. Copyright stays with the author.
Continual Learning
Keep AGENTS.md current by delegating the memory update flow to one subagent.
Trigger
Use when the user asks to mine prior chats, maintain AGENTS.md, or run the continual-learning loop.
Workflow
Call agents-memory-updater.
Return the updater result.
Guardrails
Keep the parent skill orchestration-only.
Do not mine transcripts or edit files in the parent flow.
Do not bypass the subagent.
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 continual-learning 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.
