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.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

review-team-deliverables - Skill - OpenSmartRoute

Skillv1.0.0

review-team-deliverables

Name: review-team-deliverables
Author: ruvnet

Checks an AI team run against its acceptance criteria using the evidence bundle. Use when the user asks whether the work is done or correct, or before completing a run.

by ruvnet(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from ruvnet/ruflo (plugins/ruflo-ai-team/directory/skills/review-team-deliverables/SKILL.md). Install upstream with npx skills add ruvnet/ruflo --skill review-team-deliverables. Copyright stays with the author.

Review Team Deliverables

Uses the RuFlo AI Team connector (server name ruflo-ai-team): the tools team_get, task_list, memory_search and evidence_export.

Retrieve the evidence bundle and compare each acceptance criterion with a concrete task result or artifact reference. Separate verified facts, agent assertions, uncertainty, and missing work. Report the recorded budget without presenting it as enforced or billed. Recommend completion only when every required criterion has evidence; the user decides whether to complete the run.

Next: if every criterion has evidence and the user agrees, use the manage-team-lifecycle skill to complete the run; if not, use the coordinate-team-work skill to add tasks for the gaps.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

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

Installed into a catalogue, chosen by a router

Install review-team-deliverables 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.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

ruvnet-ruflo-review-team-deliverables.ocm.jsonjson

{
  "ocm": "1",
  "id": "ruvnet-ruflo-review-team-deliverables",
  "kind": "skill",
  "name": "review-team-deliverables",
  "description": "Checks an AI team run against its acceptance criteria using the evidence bundle. Use when the user asks whether the work is done or correct, or before completing a run. Separates verified evidence from agent claims.",
  "publisher": "ruvnet",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "finance"
    ],
    "tags": [
      "skill-md",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Checks an AI team run against its acceptance criteria using the evidence bundle. Use when the user asks whether the work is done or correct, or before completing a run. Separates verified evidence from agent claims."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/ruvnet/ruflo",
      "path": "plugins/ruflo-ai-team/directory/skills/review-team-deliverables/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/ruvnet/ruflo/blob/HEAD/plugins/ruflo-ai-team/directory/skills/review-team-deliverables/SKILL.md",
      "key": "ruvnet/ruflo/plugins/ruflo-ai-team/directory/skills/review-team-deliverables/SKILL.md"
    },
    "allowed_tools": [
      "Read"
    ]
  },
  "instructions": "# Review Team Deliverables\n\nUses the RuFlo AI Team connector (server name ruflo-ai-team): the tools team_get, task_list, memory_search and evidence_export.\n\nRetrieve the evidence bundle and compare each acceptance criterion with a concrete task result or artifact reference. Separate verified facts, agent assertions, uncertainty, and missing work. Report the recorded budget without presenting it as enforced or billed. Recommend completion only when every required criterion has evidence; the user decides whether to complete the run.\n\nNext: if every criterion has evidence and the user agrees, use",
  "cost": {
    "context_tokens": 180
  }
}

Fetch it by URL: GET /api/v1/registry/ruvnet-ruflo-review-team-deliverables/manifest?version=1.0.0

About

Review Team Deliverables

Use it

Install review-team-deliverables 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