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.

validate-incident-fixtures - Skill

Name: validate-incident-fixtures
Author: openshift

Imported from openshift/monitoring-plugin (.agents/skills/validate-incident-fixtures/SKILL.md). Install upstream with npx skills add openshift/monitoring-plugin --skill validate-incident-fixtures. Copyright stays with the author.

Validate incident fixtures

The schema and validator live under web/cypress/support/incidents_prometheus_query_mocks/schema/. Run them from web/ so package scripts and dependencies resolve correctly.

For all YAML fixtures:

npm run ts-node cypress/support/incidents_prometheus_query_mocks/schema/validate-fixtures.ts -- --all

For explicit files, pass paths relative to web/ after --:

npm run ts-node cypress/support/incidents_prometheus_query_mocks/schema/validate-fixtures.ts -- cypress/fixtures/incident-scenarios/<file>.yaml

Report each file's result and the validator's concrete schema errors. Validation alone does not authorize edits: suggest fixes, and modify invalid fixtures only when the user asks to fix them. When editing, first read .agents/references/incidents-testing-guidelines.md and the current JSON Schema.

Install validate-incident-fixtures 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": "openshift-monitoring-plugin-validate-incident-fixtures", "kind": "skill", "name": "validate-incident-fixtures", "description": "Validate one or all Cypress incident YAML fixtures against the repository schema. Use when the user asks to check fixture validity or diagnose fixture validation errors.", "publisher": "openshift", "version": "1.0.0", "capabilities": { "domains": [ "observability" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Validate one or all Cypress incident YAML fixtures against the repository schema. Use when the user asks to check fixture validity or diagnose fixture validation errors." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/openshift/monitoring-plugin", "path": ".agents/skills/validate-incident-fixtures/SKILL.md", "ref": "92791ddeacccf2a9f0a5c4bfd8d91623dd26db05", "url": "https://github.com/openshift/monitoring-plugin/blob/92791ddeacccf2a9f0a5c4bfd8d91623dd26db05/.agents/skills/validate-incident-fixtures/SKILL.md", "key": "openshift/monitoring-plugin/.agents/skills/validate-incident-fixtures/SKILL.md" } }, "instructions": "# Validate incident fixtures\n\nThe schema and validator live under `web/cypress/support/incidents_prometheus_query_mocks/schema/`. Run them from `web/` so package scripts and dependencies resolve correctly.\n\nFor all YAML fixtures:\n\n```bash\nnpm run ts-node cypress/support/incidents_prometheus_query_mocks/schema/validate-fixtures.ts -- --all\n```\n\nFor explicit files, pass paths relative to `web/` after `--`:\n\n```bash\nnpm run ts-node cypress/support/incidents_prometheus_query_mocks/schema/validate-fixtures.ts -- cypress/fixtures/incident-scenarios/<file>.yaml\n```\n\nReport each file's result and the ", "cost": { "context_tokens": 216 } }

validate-incident-fixtures

About

Validate incident fixtures

Install validate-incident-fixtures 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