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.
PDFPundit - Skill - OpenSmartRoute
Skillv1.0.0
PDFPundit
Issues are tracked as GitHub Issues on shythulu/PDFPundit, via the gh CLI. See docs/agents/issue-tracker.md.
Imported from shythulu/PDFPundit (AGENTS.md). Install upstream with npx skills add shythulu/PDFPundit. Copyright stays with the author.
PDFPundit
Agent skills
Issue tracker
Issues are tracked as GitHub Issues on shythulu/PDFPundit, via the gh CLI. See docs/agents/issue-tracker.md.
Triage labels
The five canonical triage labels are used as-is: needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. See docs/agents/triage-labels.md.
Domain docs
Single-context: one CONTEXT.md and docs/adr/ at the repo root. See docs/agents/domain.md.
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://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 PDFPundit 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.
