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.

recoup-roster-manage-artist - Skill

Name: recoup-roster-manage-artist
Author: recoupable

Imported from recoupable/skills (skills/recoup-roster-manage-artist/SKILL.md) via skills.sh. Install upstream with npx skills add recoupable/skills --skill recoup-roster-manage-artist. Copyright stays with the author.

Recoup — Manage Artist

Operate inside an existing artist's workspace at artists/{artist-slug}/. RECOUP.md (frontmatter artistName/artistSlug/artistId) is the identity file.

Layout

context/artist.md (who they are — static), context/audience.md (static), context/images/face-guide.png, releases/{slug}/RELEASE.md (the release master doc), songs/{slug}/{slug}.mp3. Nothing is pre-created — add files when real content arrives; never write placeholder tokens.

Static vs dynamic context

Update artist.md/audience.md deliberately (they're the source of truth other skills read); treat research/release docs as time-bound — archive when stale. Commit {what}: {why}; the git log is the per-artist progress log.

Guardrails

No placeholder data in artist files — real content or leave the section out.
Don't overwrite static context casually — artist.md changes are deliberate evolutions; note the why in the commit.
Never invent a roster/artist — empty filesystem ≠ empty roster; confirm via recoup-platform-api-access first.

# 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 recoup-roster-manage-artist 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": "recoupable-skills-recoup-roster-manage-artist", "kind": "skill", "name": "recoup-roster-manage-artist", "description": "Work inside one artist's folder — read and update their context, brand, songs, and releases. Use for \"organize [artist]'s files\", \"update [artist]'s brand/context\", \"what's in [artist]'s workspace\", or any task about a named artist's files. To list your whole roster use recoup-roster-list-artists; for research/metrics on an artist use recoup-research-artist-overview.", "publisher": "recoupable", "version": "1.0.0", "capabilities": { "domains": [ "coding", "marketing" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Work inside one artist's folder — read and update their context, brand, songs, and releases. Use for \"organize [artist]'s files\", \"update [artist]'s brand/context\", \"what's in [artist]'s workspace\", or any task about a named artist's files. To list your whole roster use recoup-roster-list-artists; for research/metrics on an artist use recoup-research-artist-overview." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/recoupable/skills", "path": "skills/recoup-roster-manage-artist/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/recoupable/skills/recoup-roster-manage-artist", "key": "recoupable/skills/skills/recoup-roster-manage-artist/SKILL.md" } }, "instructions": "# Recoup — Manage Artist\n\nOperate inside an existing artist's workspace at `artists/{artist-slug}/`.\n`RECOUP.md` (frontmatter `artistName`/`artistSlug`/`artistId`) is the identity file.\n\n## Layout\n\n`context/artist.md` (who they are — static), `context/audience.md` (static),\n`context/images/face-guide.png`, `releases/{slug}/RELEASE.md` (the release master\ndoc), `songs/{slug}/{slug}.mp3`. Nothing is pre-created — add files when real\ncontent arrives; never write placeholder tokens.\n\n## Static vs dynamic context\n\nUpdate `artist.md`/`audience.md` deliberately (they're the source of truth other\nskil", "cost": { "context_tokens": 270 } }

recoup-roster-manage-artist

About

Recoup — Manage Artist

Layout

Static vs dynamic context

Guardrails

Use it

Install recoup-roster-manage-artist 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