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.
tapps-docs-generate - Skill - OpenSmartRoute
Skillv1.0.0
tapps-docs-generate
Quick doc generation: README, llms.txt, changelog. Use for a minimal generate pass; prefer tapps-docs-bootstrap for new projects.
Imported from wtthornton/agentforge-federation-plugin (.tapps-mcp/backups/2026-08-03-213336/.claude/skills/tapps-docs-generate/SKILL.md). Install upstream with npx skills add wtthornton/agentforge-federation-plugin --skill tapps-docs-generate. Copyright stays with the author.
mcp__nlt-project-docs__docs_generate_changelog when git tags exist
For operational docs: docs_generate_runbook / docs_generate_postmortem with structured fields
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 tapps-docs-generate 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.
