How do I install the Recoup Roster Add Artist skill?

Run npx skillmds add om-scogo/recoup-roster-add-artist in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Recoup Roster Add Artist safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Recoup Roster Add Artist?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Recoup Roster Add Artist free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Recoup Roster Add Artist?

om-scogo (@om-scogo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Recoup Roster Add Artist by om-scogo

Name: Recoup Roster Add Artist
Rating: 4.5 (4 reviews)
Author: om-scogo

Recoup Roster Add Artist

Onboard a brand-new artist to your roster and enrich them — the 8-call chain (create → Spotify match → research → catalog → socials → knowledge base) that sets up the artist and their workspace folder. Use for "create/add/onboard an artist", "set up [artist]", "we just signed [artist]", or "new signing". To see your roster use recoup-roster-list-artists; to work inside an existing artist's files use recoup-roster-manage-artist.

om-scogo 0d42946 4 files · 7.1 KB Updated Sep 8, 2026 0 repo stars

File contents

Recoup — Add Artist

Bring a new artist into the box: create the account, enrich it, and scaffold their workspace. Driven by a checklist so the long chain is resumable.

The 8-call onboarding chain (drive from the RECOUP.md checklist)

Long chains run from prose drop steps, so drive from the RECOUP.md checklist: scaffold it first (frontmatter holds captured values; body holds the unchecked steps), tick + persist after each step — the file IS the workflow state, resumable from the first unchecked box. Don't run under an agent+ account (data gets orphaned). The 8 calls:

POST /api/artists {name, organization_id} → capture account_id.
GET /api/spotify/search → best match → id, external_urls.spotify, images[0].
PATCH /api/artists/{id} with image + profileUrls:{SPOTIFY} (UPPERCASE keys).
Structured research (retry transient misses): /research/lookup?spotifyId= → songstats_artist_id, then /research/profile|career|playlists + /research/web.
Spotify catalog (topTracks, albums, album) → write releases/{slug}/RELEASE.md per album + releases/top-tracks.md.
Web search for socials (ig/tiktok/twitter/youtube).
PATCH /api/artists/{id} with discovered profileUrls (only platforms found).
Synthesize a ## Knowledge base section into RECOUP.md.

Run in order; don't continue past a 4xx/5xx without recovery. Uses recoup-platform-api-access for the call shapes.

Guardrails

The file is the state — tick + persist each step or a fresh turn redoes/skips work.
No placeholder data in artist files — real content or leave the section out.
Never invent a roster/artist — confirm via recoup-platform-api-access first; an empty filesystem is not an empty roster.

---name: recoup-roster-add-artistdescription: Onboard a brand-new artist to your roster and enrich them — the 8-call chain (create → Spotify match → research → catalog → socials → knowledge base) that sets up the artist and their workspace folder. Use for "create/add/onboard an artist", "set up [artist]", "we just signed [artist]", or "new signing". To see your roster use recoup-roster-list-artists; to work inside an existing artist's files use recoup-roster-manage-artist.---# Recoup — Add ArtistBring a new artist into the box: create the account, enrich it, and scaffold theirworkspace. Driven by a checklist so the long chain is resumable.## The 8-call onboarding chain (drive from the RECOUP.md checklist)Long chains run from prose drop steps, so **drive from the `RECOUP.md` checklist**:scaffold it first (frontmatter holds captured values; body holds the uncheckedsteps), tick + persist after each step — the file IS the workflow state, resumablefrom the first unchecked box. Don't run under an `agent+` account (data getsorphaned). The 8 calls:1. `POST /api/artists {name, organization_id}` → capture `account_id`.2. `GET /api/spotify/search` → best match → `id`, `external_urls.spotify`, `images[0]`.3. `PATCH /api/artists/{id}` with image + `profileUrls:{SPOTIFY}` (UPPERCASE keys).4. Structured research (retry transient misses): `/research/lookup?spotifyId=` → `songstats_artist_id`, then `/research/profile|career|playlists` + `/research/web`.5. Spotify catalog (`topTracks`, `albums`, `album`) → write `releases/{slug}/RELEASE.md` per album + `releases/top-tracks.md`.6. Web search for socials (ig/tiktok/twitter/youtube).7. `PATCH /api/artists/{id}` with discovered `profileUrls` (only platforms found).8. Synthesize a `## Knowledge base` section into `RECOUP.md`.Run in order; don't continue past a 4xx/5xx without recovery. Usesrecoup-platform-api-access for the call shapes.## Guardrails- **The file is the state** — tick + persist each step or a fresh turn redoes/skips work.- **No placeholder data** in artist files — real content or leave the section out.- **Never invent a roster/artist** — confirm via recoup-platform-api-access first; an empty filesystem is not an empty roster.

Frequently asked questions