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.

rill - Skill - OpenSmartRoute

Name: rill
Author: zrr1999

Imported from zrr1999/rill (AGENTS.md). Install upstream with npx skills add zrr1999/rill. Copyright stays with the author.

Working on Rill

Use CONTRIBUTING.md for development commands, generated files, validation, and Git delivery conventions. Check the current implementation before relying on older plans or acceptance notes.

Working notes (research, plans, acceptance records) live in .agents/notes/, indexed by .agents/notes/README.md; read them on demand and never treat them as current truth. Formal docs (docs/, README, CONTRIBUTING, site pages) must not reference notes; only AGENTS.md, skills, and the notes index may point to them.

Keep notes sparse and brief. Update an existing note first; create a new file only for distinct, lasting context. Record conclusions, essential evidence, and open questions; omit task diaries, transcripts, and full logs.

Repository layout

Preserve the existing repository layout. Do not add new tracked directories, including under .github/, without the user's explicit request or approval.
Do not commit PR screenshots, screen recordings, or temporary acceptance artifacts. Attach media to the PR and keep local evidence in the ignored .artifacts/ directory.

Delivery and reporting

Wait until every check for the current head commit has finished before reporting CI as passing; never reuse a green result from an older commit.

Pull requests

Independent changes should be separate PRs targeting main, even when created in the same conversation. Use a linear GitHub native stack only for real code dependencies; each dependent PR targets the branch it needs.

PRs that change UI must include screenshots in the PR body, as specified in CONTRIBUTING.md and the PR template.

Repository skills

Load the skill that matches the task. Combine skills only when the work crosses their boundaries; an ordinary edit does not require running all six workflows.

Task	Skill
Review a PR, commit range, or working-tree change	rill-code-review
Change workflow TOML, built-ins, compilation, or ordered execution	rill-workflow-change
Change Record storage, memberships, routing, capture, or delivery	rill-record-change
Diagnose recording, worker, cancellation, or shutdown failures	rill-runtime-debug
Verify macOS interaction, permissions, focus, or release artifacts	rill-macos-qa
Change visual presentation, materials, type, or floating chrome	rill-ui-change

These skills are maintained with this repository and require no personal skill installation. Keep shared project facts in the documents below and link to them from skills rather than maintaining another copy.

Project contracts

Install rill 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": "zrr1999-rill-rill", "kind": "skill", "name": "rill", "description": "Use [CONTRIBUTING.md](CONTRIBUTING.md) for development commands, generated files, validation, and Git delivery conventions. Check the current implementation before relying on older plans or acceptance notes.", "publisher": "zrr1999", "version": "1.0.0", "capabilities": { "domains": [ "coding", "customer_support" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use [CONTRIBUTING.md](CONTRIBUTING.md) for development commands, generated files, validation, and Git delivery conventions. Check the current implementation before relying on older plans or acceptance notes." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/zrr1999/rill", "path": "AGENTS.md", "ref": "6e56a4b73bca6b1779195ebeea6dd7e0336a0ab8", "url": "https://github.com/zrr1999/rill/blob/6e56a4b73bca6b1779195ebeea6dd7e0336a0ab8/AGENTS.md", "key": "zrr1999/rill/AGENTS.md" } }, "instructions": "# Working on Rill\n\nUse [CONTRIBUTING.md](CONTRIBUTING.md) for development commands, generated\nfiles, validation, and Git delivery conventions. Check the current implementation\nbefore relying on older plans or acceptance notes.\n\nWorking notes (research, plans, acceptance records) live in `.agents/notes/`,\nindexed by `.agents/notes/README.md`; read them on demand and never treat them as\ncurrent truth. Formal docs (`docs/`, README, CONTRIBUTING, site pages) must not\nreference notes; only AGENTS.md, skills, and the notes index may point to them.\n\nKeep notes sparse and brief. Update an existing not", "cost": { "context_tokens": 795 } }

rill

About

Working on Rill

Repository layout

Delivery and reporting

Pull requests

Repository skills

Project contracts

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