recoup-platform-build-os — Claude Code skill: build a music company OS
Scaffolds a working OS for a music business inside your repo: folder structure, a self-managing CLAUDE.md, a plugin with skills and health checks.
npx skills add recoupable/skills --skill recoup-platform-build-os -a claude-codeWhat recoup-platform-build-os does
The skill walks the agent through phases and turns a kickoff input into a living workspace: a folder and file tree, a CLAUDE.md mirrored to AGENTS.md, a plugin/ directory holding an in-place installable plugin with skills inside, plus a janitor skill backed by a read-only {domain}-doctor check. The plugin is named {DOMAIN_SLUG}-os by default and ships manifests and adapters for Claude, Cursor and Codex.
The domain follows the actual work rather than a template. Artist and release operations use artists/ with releases under each artist; publishing uses compositions/ and parties/; audit, royalty reconciliation and acquisitions use cases/ with scope, evidence and stage records. An empty roster is fine, and there is no reason to invent an artist account for composition work. Verified artists are mirrored into artists/{artist-slug}/RECOUP.md with artistName, artistSlug and the real artistId — IDs are never made up.
Secrets stay out of versioned material: when REST access is needed, the skill seeds an .env.example listing variable names and a .gitignore that excludes real credentials. MCP OAuth credentials are not copied into files. A business without artists, catalog valuation or a recurring task still gets its doctor and dashboard templates filled in for the chosen spine, because otherwise health checks fail for no good reason.
What it helps with
- scaffold a folder and file structure for a label or publisher
- set up a
CLAUDE.mdthat keeps its own state current - get an installable plugin with skills living in the repo
- run read-only health checks on the workspace
- mirror a verified roster into artist folders with real IDs
Example prompts for the agent
- Set up our label OS in this repository
- Build our publishing workspace with compositions and parties
- Mirror my roster into
artists/{artist-slug}folders
How to install recoup-platform-build-os
1Skills CLI (Vercel)
npx skills add recoupable/skills --skill recoup-platform-build-os -a claude-code2Manually: put the files in place
~/.claude/skills/recoup-platform-build-os/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/recoup-platform-build-os/
1Skills CLI (Vercel)
npx skills add recoupable/skills --skill recoup-platform-build-os -a codex2Manually: put the files in place
.agents/skills/recoup-platform-build-os/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add recoupable/skills --skill recoup-platform-build-os -a cursor2Manually: put the files in place
.cursor/skills/recoup-platform-build-os/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install recoupable/skills recoup-platform-build-os2Manually: put the files in place
.github/skills/recoup-platform-build-os/SKILL.md1Skills CLI (Vercel)
npx skills add recoupable/skills --skill recoup-platform-build-os -a gemini-cli2Platform CLI
gemini skills install https://github.com/recoupable/skills --path skills/recoup-platform-build-osManually: put the files in place
.devin/skills/recoup-platform-build-os/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add recoupable/skills --skill recoup-platform-build-os -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about recoup-platform-build-os
How do I install recoup-platform-build-os in Claude Code?
Run npx skills add recoupable/skills --skill recoup-platform-build-os -a claude-code; the skill lands at ~/.claude/skills/recoup-platform-build-os/SKILL.md.
What does recoup-platform-build-os do?
It builds a music company's working OS from a kickoff input: folder structure, a self-managing CLAUDE.md, a plugin with skills, a janitor with health checks and a learning loop.
Do I need an artist roster for the skill to work?
No. An empty roster is legitimate, and the workspace is shaped around the real objects: releases, compositions with parties, or audit cases.
