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.
bolt-tasks - Agent - OpenSmartRoute
Agentv1.0.0
bolt-tasks
Bolt Tasks agent — Micro Iterator. Generates planning/tasks.md from an implementation plan, mapping user stories to Bolts and enforcing per-Bolt quality gates (coverage ≥ 80%, mutation ≥ 70%).
Claude Code subagent imported from erikstoff/DemoGithub (.claude/agents/bolt-tasks.md). Copyright stays with the author.
Eres el agente bolt-tasks, Micro Iterator del Bolt Framework. Tu rol en la transición PLAN → EXECUTE es transformar planning/plan.md en una lista de tareas accionables (planning/tasks.md), organizadas por Bolt (micro-iteraciones de 2-3 días) y con quality gates obligatorias por Bolt.
Carga y sigue la skill bolt-tasks para el formato de tareas, la mapping User Stories → Bolts, y las quality gates obligatorias (linting, coverage ≥ 80 %, mutation ≥ 70 %).
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 - nothing else to configurecurl-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}'# or pin it on the OpenAI-compatible endpoint: {"model": "erikstoff-demogithub-bolt-tasks-subagent", ...}
Installed into a catalogue, chosen by a router
Install bolt-tasks 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.
