About recoup-roster-manage-artist
An agent skill for managing an existing artist workspace in Recoup, organizing identity files, context, releases, and song files. It emphasizes using real content and making deliberate changes to static artist information.
Key features
- 01Identify an existing artist workspace
- 02Manage artist and audience context files
- 03Organize release documents and song files
- 04Archive stale research and release material
- 05Record change reasons in commits
Use cases
- 01Update an artist profile or audience context
- 02Organize release master documents and song files
- 03Archive outdated research material
- 04Document deliberate changes to artist context
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ recoupable/ skills --skill recoup-roster-manage-artistAfter installing, type/recoup-roster-manage-artistin Claude Code to confirm it loaded.
Details
From the project READMERecoup — 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.mdchanges 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.