How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

registry-pick - Prompt - OpenSmartRoute

Name: registry-pick
Author: 0x4cb-caramelo

Prompt file imported from 0x4cb-caramelo/Bakedtruth (.claude/commands/registry-pick.md). Copyright stays with the author.

/registry-pick

Recommend external repository packs from the registry that fit the current project.

Expected input

/registry-pick

Optional arguments:

/registry-pick stack="<stack>" domain="<domain>" compliance="<compliance>"

If arguments are omitted, the skill reads project signals from whatever exists at that point in the wizard — the input contract differs per pass:

Pass	Lê	NÃO lê
3.1 design	`docs/business/BUSINESS-PLAN.md` v0.0.2, `knowledge-base/`	Product Brief e Technical Plan — ainda não existem
4.3 stack	tudo acima + `docs/product/PRODUCT-BRIEF.md`, `docs/technical/TECHNICAL-PLAN.md`, `prototype-lab/`, manifestos (`package.json`, `Anchor.toml`…)	—

Pedir na passada de design um arquivo que a Fase 3 ainda não produziu trava o wizard sem motivo.

Actions

Invoke the registry-pick skill.
Read docs/registry/INDEX.md and the relevant packs/<slug>.md one-pagers.
Match project signals against pack tags and fit-signals.
Output a prioritized recommendation: must-install / recommended / optional / skipped.
Stop before installing — surface install commands but defer execution to the user.

When to use

At WIZARD.md stage 3.1 — design-scoped pass, before the Prototype Lab. Output: docs/technical/registry-pick-design.md.
At WIZARD.md stage 4.3 — full stack pass, after the Technical Plan. Output: docs/technical/registry-pick.md.
When a new domain need surfaces mid-build.
After a new pack is added to docs/registry/.

Cross-references

Skill: .claude/skills/registry-pick/SKILL.md
Registry: docs/registry/INDEX.md

Install registry-pick 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.

{ "prompt": "# /registry-pick\n\nRecommend external repository packs from the registry that fit the current project.\n\n## Expected input\n\n```txt\n/registry-pick\n```\n\nOptional arguments:\n\n```txt\n/registry-pick stack=\"<stack>\" domain=\"<domain>\" compliance=\"<compliance>\"\n```\n\nIf arguments are omitted, the skill reads project signals from whatever exists at that point in the wizard — the input contract differs per pass:\n\n| Pass | Lê | NÃO lê |\n|---|---|---|\n| **3.1** design | `docs/business/BUSINESS-PLAN.md` v0.0.2, `knowledge-base/` | Product Brief e Technical Plan — ainda não existem |\n| **4.3** stack | tudo acima + `docs/product/PRODUCT-BRIEF.md`, `docs/technical/TECHNICAL-PLAN.md`, `prototype-lab/`, manifestos (`package.json`, `Anchor.toml`…) | — |\n\nPedir na passada de design um arquivo que a Fase 3 ainda não produziu trava o wizard sem motivo.\n\n## Actions\n\n1. Invoke the `registry-pick` skill.\n2. Read `docs/registry/INDEX.md` and the relevant `packs/<slug>.md` one-pagers.\n3. Match project signals against pack tags and fit-signals.\n4. Output a prioritized recommendation: must-install / recommended / optional / skipped.\n5. Stop before installing — surface install commands but defer execution to the user.\n\n## When to use\n\n- At `WIZARD.md` **stage 3.1** — design-scoped pass, before the Prototype Lab. Output: `docs/technical/registry-pick-design.md`.\n- At `WIZARD.md` **stage 4.3** — full stack pass, after the Technical Plan. Output: `docs/technical/registry-pick.md`.\n- When a new domain need surfaces mid-build.\n- After a new pack is added to `docs/registry/`.\n\n## Cross-references\n\n- Skill: `.claude/skills/registry-pick/SKILL.md`\n- Registry: `docs/registry/INDEX.md`", "variables": [], "notes": "Recomenda packs externos do registry que servem pro projeto atual. Roda duas vezes no wizard — packs de design no 3.1, stack completa no 4.3. Nunca instala nada.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/0x4cb-caramelo/Bakedtruth", "path": ".claude/commands/registry-pick.md", "ref": "30b0d915f681310436ce733698b6ae5ef434f897", "url": "https://github.com/0x4cb-caramelo/Bakedtruth/blob/30b0d915f681310436ce733698b6ae5ef434f897/.claude/commands/registry-pick.md", "key": "0x4cb-caramelo/Bakedtruth/.claude/commands/registry-pick.md" } } }

registry-pick

About

/registry-pick

Expected input

Actions

When to use

Cross-references

Install registry-pick and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews