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.

database-change - Skill - OpenSmartRoute

Name: database-change
Author: work-w-chrstnrpj

Imported from work-w-chrstnrpj/lumina-studio-web (.agents/skills/database-change/SKILL.md). Install upstream with npx skills add work-w-chrstnrpj/lumina-studio-web --skill database-change. Copyright stays with the author.

Database Change

Workflow

Read project persistence docs and maps.
Inspect exact schema/model, repository/query, service usage, and tests.
Plan compatibility, migration, backfill, and rollback needs.
Make the smallest safe persistence change.
Add or update schema, repository, migration, or integration tests.
Update database docs and context maps when shape or ownership changes.

Boundaries

Do not run destructive data operations without approval.
Do not store secrets or sensitive values insecurely.
Do not make incompatible schema changes without a migration or compatibility plan.

Output

Relevant files or docs inspected.
Work completed or plan produced.
Tests or verification run or recommended.
Docs updated or skipped with reason.
Remaining risks, assumptions, and handoffs.

# 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}'

Install database-change 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": "work-w-chrstnrpj-lumina-studio-web-database-change", "kind": "skill", "name": "database-change", "description": "Safely change database schema, model, repository, index, migration, or persistence behavior.", "publisher": "work-w-chrstnrpj", "version": "1.0.0", "capabilities": { "domains": [ "coding", "data_analysis" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Safely change database schema, model, repository, index, migration, or persistence behavior." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/work-w-chrstnrpj/lumina-studio-web", "path": ".agents/skills/database-change/SKILL.md", "ref": "33762c6ce0359b68e4bb81c27fbade4ab40f23e3", "url": "https://github.com/work-w-chrstnrpj/lumina-studio-web/blob/33762c6ce0359b68e4bb81c27fbade4ab40f23e3/.agents/skills/database-change/SKILL.md", "key": "work-w-chrstnrpj/lumina-studio-web/.agents/skills/database-change/SKILL.md" } }, "instructions": "# Database Change\n\n## Workflow\n\n1. Read project persistence docs and maps.\n2. Inspect exact schema/model, repository/query, service usage, and tests.\n3. Plan compatibility, migration, backfill, and rollback needs.\n4. Make the smallest safe persistence change.\n5. Add or update schema, repository, migration, or integration tests.\n6. Update database docs and context maps when shape or ownership changes.\n\n## Boundaries\n\n- Do not run destructive data operations without approval.\n- Do not store secrets or sensitive values insecurely.\n- Do not make incompatible schema changes without a migration or c", "cost": { "context_tokens": 207 } }

database-change

About

Database Change

Workflow

Boundaries

Output

Use it

Install database-change 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