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.

herdr-pre-release-audit - Skill

Name: herdr-pre-release-audit
Author: herdrdev

Imported from herdrdev/herdr (.agents/skills/herdr-pre-release-audit/SKILL.md) via skills.sh. Install upstream with npx skills add herdrdev/herdr --skill herdr-pre-release-audit. Copyright stays with the author.

Herdr Pre-release Audit

Use this skill only inside the herdr repository.

Read references/pre-release-audit.md and follow its workflow. Treat it as the source of truth for:

choosing the release base ref
inspecting first-parent history and merged PRs
auditing docs/next/CHANGELOG.md
auditing docs/next/README.md and staged website docs
checking skills/herdr/SKILL.md against shipped CLI and agent-control behavior
checking issue reference lines
deciding when to run just pre-release-check or its component checks
running and assessing just bench-render-scale
producing the final release-readiness report

Do not edit files during the audit unless the user explicitly asks to apply fixes. When applying fixes, keep changes scoped to the files named in the reference workflow.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install herdr-pre-release-audit 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": "herdrdev-herdr-herdr-pre-release-audit", "kind": "skill", "name": "herdr-pre-release-audit", "description": "Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's pre-release audit, validate docs/next before release, inspect issue refs that release CI will close, or finalize release docs for herdr.", "publisher": "herdrdev", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's pre-release audit, validate docs/next before release, inspect issue refs that release CI will close, or finalize release docs for herdr." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/herdrdev/herdr", "path": ".agents/skills/herdr-pre-release-audit/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/herdrdev/herdr/herdr-pre-release-audit", "key": "herdrdev/herdr/.agents/skills/herdr-pre-release-audit/SKILL.md" } }, "instructions": "# Herdr Pre-release Audit\n\nUse this skill only inside the herdr repository.\n\nRead `references/pre-release-audit.md` and follow its workflow. Treat it as the source of truth for:\n\n- choosing the release base ref\n- inspecting first-parent history and merged PRs\n- auditing `docs/next/CHANGELOG.md`\n- auditing `docs/next/README.md` and staged website docs\n- checking `skills/herdr/SKILL.md` against shipped CLI and agent-control behavior\n- checking issue reference lines\n- deciding when to run `just pre-release-check` or its component checks\n- running and assessing `just bench-render-scale`\n- producin", "cost": { "context_tokens": 201 } }

herdr-pre-release-audit

About

Herdr Pre-release Audit

Use it

Install herdr-pre-release-audit 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