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.
Use this skill when developing or maintaining browser extension code in the browser/ directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
Imported from yamadashy/repomix (browser/.claude/skills/browser-extension-developer/SKILL.md). Install upstream with npx skills add yamadashy/repomix --skill browser-extension-developer. Copyright stays with the author.
Browser Extension Developer
Cross-browser extension (Chrome/Firefox/Edge) using WXT framework with Manifest V3. Injects "Repomix" button into GitHub repository pages.
12 languages: en, ja, de, fr, es, pt_BR, id, vi, ko, zh_CN, zh_TW, hi
New language: Create public/_locales/[code]/messages.json with keys: appDescription, openWithRepomix
Notes
Chrome/Edge use chrome.* APIs, Firefox may need polyfills
Run lint and tests before completion
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 browser-extension-developer 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.
