recoup-roster-add-artist — Claude Code skill: onboard an artist

What recoup-roster-add-artist does

The skill walks an artist through an eight-step chain and keeps state in RECOUP.md. Identity comes first: a Spotify URL or ID is verified and the exact 22-character, case-sensitive spotify_artist_id is captured. Ambiguous matches stop for selection. Then POST /api/artists goes out with the name, Spotify ID and organization_id — 200 means an existing canonical profile was reused, 201 means a new one was created. Status and returned ID are saved right away.

Enrichment follows: GET /api/research/lookup returns a research ID, profile, career and playlists are read, the Spotify catalog lands in releases/{slug}/RELEASE.md and releases/top-tracks.md, socials are found and written back with PATCH /api/artists/{id}, and a knowledge base section closes the run. Calls go through recoup-platform-api-access.

Manual onboarding is a separate path: only {name, organization_id} with mode manual. It does not link artists by matching name and does not create a professional-roster record, and it must not be used after a failed canonical request. One more thing worth knowing: a mutation is never retried automatically on a network failure or 5xx, because it may have committed — reconcile the roster first. The examples in scripts/onboarding_examples.sh need Bash, jq and a configured RECOUP_API_KEY or RECOUP_ACCESS_TOKEN.