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.

verify - Skill - OpenSmartRoute

Name: verify
Author: swt-labs

Imported from swt-labs/vibe-better-with-claude-code-vbw (plugin/skills/verify/SKILL.md). Install upstream with npx skills add swt-labs/vibe-better-with-claude-code-vbw --skill verify. Copyright stays with the author.

"${CLAUDE_PLUGIN_ROOT}/bin/vbw" show requirements 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" interview 2>&1 || true

Write to the user's level, explanation depth and involvement (above; "-": plain words).

The requirements to check are the [human, open] or [human, rejected] ones marked built above. None: say what is still being built and stop.

For each one, one at a time: show the user the thing to judge. Run it yourself when you can (the program's actual output, the page's text) and put that, or one concrete thing to try, in the question and the preview of "Works". Something visual: if you can open it (a browser tool), save a screenshot in .vbw/runtime/ and open it for the user (open, xdg-open); otherwise give the exact way to see it. Ask with AskUserQuestion: "Works", "Something's wrong", "Skip for now".

Works: vbw req accept <id>.
Something's wrong: ask what, in their words, then vbw req reject <id> "<their words>" (VBW fixes it and asks again).
Skip for now: vbw req skip <id> (it stays open; /vbw:vibe offers to ship and judge it in the next milestone).

Close with what was accepted and what goes back for fixing; /vbw:vibe continues.

Install verify 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.

{ "ocm": "1", "id": "swt-labs-vibe-better-with-claude-code-vbw-verify", "kind": "skill", "name": "verify", "description": "Check, one at a time, the things only you can judge (look, feel, wording) for the work that is built, and record your verdict.", "publisher": "swt-labs", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Check, one at a time, the things only you can judge (look, feel, wording) for the work that is built, and record your verdict." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/swt-labs/vibe-better-with-claude-code-vbw", "path": "plugin/skills/verify/SKILL.md", "ref": "5aae4d381e9c3e2ecbdc6589cd1ec7592a1d5d78", "url": "https://github.com/swt-labs/vibe-better-with-claude-code-vbw/blob/5aae4d381e9c3e2ecbdc6589cd1ec7592a1d5d78/plugin/skills/verify/SKILL.md", "key": "swt-labs/vibe-better-with-claude-code-vbw/plugin/skills/verify/SKILL.md" }, "allowed_tools": [ "Bash(\"${CLAUDE_PLUGIN_ROOT}/bin/vbw\"", "*)", "Bash(vbw", "*)" ] }, "instructions": "```!\n\"${CLAUDE_PLUGIN_ROOT}/bin/vbw\" show requirements 2>&1 || true\n\"${CLAUDE_PLUGIN_ROOT}/bin/vbw\" interview 2>&1 || true\n```\n\nWrite to the user's level, explanation depth and involvement (above; \"-\": plain words).\n\nThe requirements to check are the `[human, open]` or `[human, rejected]` ones\nmarked `built` above. None: say what is still being built and stop.\n\nFor each one, one at a time: show the user the thing to judge. Run it yourself\nwhen you can (the program's actual output, the page's text) and put that, or\none concrete thing to try, in the question and the `preview` of \"Works\".\nSomethi", "cost": { "context_tokens": 299 } }

verify

About

Use it

Install verify 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

Manifest

Reviews