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.

rewasd-validate - Prompt - OpenSmartRoute

Name: rewasd-validate
Author: DatMoshu

Prompt file imported from DatMoshu/Claude-Code-reWASD-Powertools (.claude/commands/rewasd-validate.md). Fill in {{arguments}} before use. Copyright stays with the author.

Validate reWASD Profile: {{arguments}}

Step 1: Resolve Paths

Read rewasd.config.json at the repo root to get rewasdProfilesPath.

Step 2: Find Profiles to Validate

If argument given, search for matching profiles in:

Repo library: profiles/**/*.rewasd
Installed: {rewasdProfilesPath}/**/*.rewasd

If no argument given, validate ALL profiles in both locations.

Step 3: Validate Each Profile

For each profile, check:

Structural Checks

Valid JSON syntax (parse without errors)
schemaVersion is 3 or 3.0
appVersion is present and non-empty
config.appName is present

Mask Integrity

Mask IDs are sequential starting from 1 with no gaps
No duplicate mask IDs
Every mask has at least one button in set[]
Every mask button has deviceId, buttonId, and description

Mapping Integrity

Every mapping with a mask condition references a mask ID that exists in masks[]
Every mapping with a shiftId references a shift that exists in shifts[]
All keyboard outputs have a valid buttonId (check against DIK code table in docs/dik-keycodes.md)
All keyboard outputs have a description field matching the DIK name

Device Integrity

Device IDs referenced in masks match devices in devices.hardware[]
Virtual gamepad type is one of: "360", "ds4", "ds3", "xboxonebt"

Radial Menu Integrity (if present)

Radial menu sector/circle cross-references are valid

Sync Check

If found in repo library, check whether an installed copy exists at {rewasdProfilesPath} — warn if out of sync

Step 4: Report

For each issue found, report:

Severity: ERROR (will break in reWASD) or WARNING (may cause unexpected behavior)
Location: which array/index/field
Description: what's wrong and how to fix it

If no issues: "Profile is valid."

Present results as a checklist with pass/fail markers. At the end: total profiles checked, total errors, total warnings.

Install rewasd-validate 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.

# Validate reWASD Profile: {{arguments}} ## Step 1: Resolve Paths Read `rewasd.config.json` at the repo root to get `rewasdProfilesPath`. ## Step 2: Find Profiles to Validate If argument given, search for matching profiles in: 1. Repo library: `profiles/**/*.rewasd` 2. Installed: `{rewasdProfilesPath}/**/*.rewasd` If no argument given, validate ALL profiles in both locations. ## Step 3: Validate Each Profile For each profile, check: ### Structural Checks 1. Valid JSON syntax (parse without errors) 2. `schemaVersion` is `3` or `3.0` 3. `appVersion` is present and non-empty 4. `config.appName` is present ### Mask Integrity 5. Mask IDs are sequential starting from 1 with no gaps 6. No duplicate mask IDs 7. Every mask has at least one button in `set[]` 8. Every mask button has `deviceId`, `buttonId`, and `description` ### Mapping Integrity 9. Every mapping with a `mask` condition references a mask ID that exists in `masks[]` 10. Every mapping with a `shiftId` references a shift that exists in `shifts[]` 11. All keyboard outputs have a valid `buttonId` (check against DIK code table in `docs/dik-keycodes.md`) 12. All keyboard outputs have a `description` field matching the DIK name ### Device Integrity 13. Device IDs referenced in masks match devices in `devices.hardware[]` 14. Virtual gamepad type is one of: `"360"`, `"ds4"`, `"ds3"`, `"xboxonebt"` ### Radial Menu Integrity (if present) 15. Radial menu sector/circle cross-references are valid ### Sync Check 16. If found in repo library, check whether an installed copy exists at `{rewasdProfilesPath}` — warn if out of sync ## Step 4: Report For each issue found, report: - Severity: ERROR (will break in reWASD) or WARNING (may cause unexpected behavior) - Location: which array/index/field - Description: what's wrong and how to fix it If no issues: "Profile is valid." Present results as a checklist with pass/fail markers. At the end: total profiles checked, total errors, total warnings.

{ "prompt": "# Validate reWASD Profile: {{arguments}}\n\n## Step 1: Resolve Paths\n\nRead `rewasd.config.json` at the repo root to get `rewasdProfilesPath`.\n\n## Step 2: Find Profiles to Validate\n\nIf argument given, search for matching profiles in:\n1. Repo library: `profiles/**/*.rewasd`\n2. Installed: `{rewasdProfilesPath}/**/*.rewasd`\n\nIf no argument given, validate ALL profiles in both locations.\n\n## Step 3: Validate Each Profile\n\nFor each profile, check:\n\n### Structural Checks\n1. Valid JSON syntax (parse without errors)\n2. `schemaVersion` is `3` or `3.0`\n3. `appVersion` is present and non-empty\n4. `config.appName` is present\n\n### Mask Integrity\n5. Mask IDs are sequential starting from 1 with no gaps\n6. No duplicate mask IDs\n7. Every mask has at least one button in `set[]`\n8. Every mask button has `deviceId`, `buttonId`, and `description`\n\n### Mapping Integrity\n9. Every mapping with a `mask` condition references a mask ID that exists in `masks[]`\n10. Every mapping with a `shiftId` references a shift that exists in `shifts[]`\n11. All keyboard outputs have a valid `buttonId` (check against DIK code table in `docs/dik-keycodes.md`)\n12. All keyboard outputs have a `description` field matching the DIK name\n\n### Device Integrity\n13. Device IDs referenced in masks match devices in `devices.hardware[]`\n14. Virtual gamepad type is one of: `\"360\"`, `\"ds4\"`, `\"ds3\"`, `\"xboxonebt\"`\n\n### Radial Menu Integrity (if present)\n15. Radial menu sector/circle cross-references are valid\n\n### Sync Check\n16. If found in repo library, check whether an installed copy exists at `{rewasdProfilesPath}` — warn if out of sync\n\n## Step 4: Report\n\nFor each issue found, report:\n- Severity: ERROR (will break in reWASD) or WARNING (may cause unexpected behavior)\n- Location: which array/index/field\n- Description: what's wrong and how to fix it\n\nIf no issues: \"Profile is valid.\"\n\nPresent results as a checklist with pass/fail markers.\nAt the end: total profiles checked, total errors, total warnings.", "variables": [ "arguments" ], "notes": "Validate a reWASD profile for correctness Tools: Read, Bash, Glob, Grep.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/DatMoshu/Claude-Code-reWASD-Powertools", "path": ".claude/commands/rewasd-validate.md", "ref": "815b05b9242c02843165117f8dafef81d02d6e67", "url": "https://github.com/DatMoshu/Claude-Code-reWASD-Powertools/blob/815b05b9242c02843165117f8dafef81d02d6e67/.claude/commands/rewasd-validate.md", "key": "DatMoshu/Claude-Code-reWASD-Powertools/.claude/commands/rewasd-validate.md" } } }

rewasd-validate

About

Validate reWASD Profile: {{arguments}}

Step 1: Resolve Paths

Step 2: Find Profiles to Validate

Step 3: Validate Each Profile

Structural Checks

Mask Integrity

Mapping Integrity

Device Integrity

Radial Menu Integrity (if present)

Sync Check

Step 4: Report

Install rewasd-validate 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