Back to Skills

setup-sandbox

Set up the initial file system for a new sandbox. Fetches the account's organizations and artists via the Recoup CLI and scaffolds the folder structure. Use when a sandbox has just been created and has no existing file system. Before running, check if the sandbox already has an orgs/ directory — if it does, this skill is not needed.

Updated 8/5/2026

Security Assessment

Safe(91/100)
Security Score91/100

About setup-sandbox

setup-sandbox scaffolds the initial file system for a newly created Recoup sandbox workspace. It solves a first-run bootstrapping problem: a fresh sandbox has no folder structure, and this skill fetches the connected account's organizations and artists via the Recoup CLI and lays out the corresponding directory tree. It is intended to run only once, and the documentation instructs checking for an existing orgs/ directory first — if it exists, the skill is not needed.

The workflow is a short, deterministic sequence: optionally read a RECOUP_ACCOUNT_ID environment variable (used only with an Org API Key; a Personal API Key lets the CLI infer the account), run `recoup orgs list --json` to enumerate organizations, then `recoup artists list --org {id} --json` per organization, and create an `orgs/{org}/artists/{artist-slug}/` folder for each artist using the exact artistSlug from the CLI response. In each artist folder it writes a RECOUP.md identity file containing artistName, artistSlug, and artistId from the CLI, then commits and pushes the new folders to the main branch. The RECOUP.md marker connects the workspace to the Recoupable platform and signals that the workspace is active.

The target users are Recoupable platform users and agents provisioning a new artist/organization workspace. Credentials are supplied through standard API-key mechanisms and used only to read the account's own org and artist data; the skill performs local filesystem scaffolding and a routine git commit and push, with no destructive or exfiltration behavior.

FAQ

When should this skill run?

Only once, right after a sandbox is created and has no file system. If an orgs/ directory already exists, the skill is not needed.

How does it authenticate?

Via the Recoup CLI. With an Org API Key you pass --account $RECOUP_ACCOUNT_ID; with a Personal API Key you omit the flag and the CLI uses the authenticated account automatically.

What does it create?

An orgs/{org}/artists/{artist-slug}/ folder for each artist, each containing a RECOUP.md identity file with artistName, artistSlug, and artistId, then it commits and pushes to main.

Does it overwrite existing folders?

No. It skips any artist folder that already exists and uses the exact artistSlug as the directory name without appending IDs or suffixes.

Install setup-sandbox

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill