
Setup Sandbox
- 1.4k installs
- Updated March 27, 2026
- recoupable/skill-setup-sandbox
This is a copy of setup-sandbox by recoupable - installs and ranking accrue to the original listing.
setup-sandbox is an agent skill that scaffolds the initial Recoup sandbox filesystem with organizations and artists folders for developers whose newly created sandbox has no existing orgs/ directory.
About
setup-sandbox in recoupable/skill-setup-sandbox initializes the file system for a new Recoup sandbox by fetching the connected account's organizations and artists through the Recoup CLI and creating the matching folder structure. The skill runs only when a sandbox has just been created and lacks an orgs/ directory—if orgs/ already exists, setup-sandbox is not needed. Environment variable RECOUP_ACCOUNT_ID supplies the account when using an Org API Key; Personal API Key auth omits the --account flag so the CLI uses the authenticated account automatically. Developers reach for setup-sandbox immediately after provisioning an isolated Recoup sandbox so agents inherit a predictable orgs-and-artists hierarchy with permissions and dependencies already wired. The workflow prevents duplicate scaffolding on sandboxes that already contain project files. Triggers include new sandbox creation, empty workspace initialization, and requests to pull Recoup organizations into the local filesystem before coding begins on music-industry or artist-management automations inside Recoup's agent environment.
- Creates a clean, isolated development sandbox in one command
- Automatically installs and configures agent-compatible tooling
- Sets correct filesystem permissions and security boundaries
- Prepares MCP server connections and API keys structure
- Eliminates hours of manual environment setup and debugging
Setup Sandbox by the numbers
- 1,385 all-time installs (skills.sh)
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/recoupable/skill-setup-sandbox --skill setup-sandboxAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| Security audit | 3 / 3 scanners passed |
| Last updated | March 27, 2026 |
| Repository | recoupable/skill-setup-sandbox ↗ |
How do you initialize a new Recoup sandbox filesystem?
Instantly create an isolated, pre-configured workspace with all necessary tools, dependencies, and agent permissions ready for a new project.
Who is it for?
Developers using Recoup sandboxes who need first-run folder scaffolding from CLI-fetched organizations and artists data.
Skip if: Sandboxes that already contain an orgs/ directory, or projects outside the Recoup platform ecosystem.
When should I use this skill?
A Recoup sandbox was just created with no orgs/ directory and the user needs initial organization and artist folder scaffolding.
What you get
orgs/ directory tree mirroring Recoup account organizations and artists fetched via Recoup CLI.
- orgs/ folder hierarchy
- organization directories
- artist subfolder structure
Files
Setup Sandbox
Create the folder structure for the connected account's organizations and artists.
Environment
RECOUP_ACCOUNT_ID— The account ID to fetch data for. Only needed when using an Org API Key. When using a Personal API Key, omit the--accountflag and the CLI will use the authenticated account automatically.
Steps
1. Check if RECOUP_ACCOUNT_ID is set. If set, use --account $RECOUP_ACCOUNT_ID on all CLI commands below. If not set, omit the --account flag. 2. Run recoup orgs list --json [--account $RECOUP_ACCOUNT_ID] to get all organizations 3. For each organization, run recoup artists list --org {organization_id} --json [--account $RECOUP_ACCOUNT_ID] to get its artists 4. Create the folder structure and a RECOUP.md marker in each artist folder:
- Use
artistSlugfrom the CLI response as the exact directory name — never append UUIDs, IDs, or suffixes - If
orgs/{org}/artists/{artist-slug}/already exists, skip it mkdir -p orgs/{org}/artists/{artist-slug}for each new artist- Write a
RECOUP.mdusing the template below
5. Commit and push:
git add -A && git commit -m "setup: create org and artist folders" && git push origin main
RECOUP.md
Every artist directory has a RECOUP.md at its root. This is the identity file — it connects the workspace to the Recoupable platform. The existence of this file means the workspace is active.
Fill it with data from the CLI response:
---
artistName: {Artist Name}
artistSlug: {artist-slug}
artistId: {uuid-from-recoupable}
---Fields:
artistName— display name from the CLI (e.g.Gatsby Grace)artistSlug— lowercase-kebab-case folder name (e.g.gatsby-grace)artistId— the UUID from Recoup
Related skills
How it compares
Pick setup-sandbox for first-run Recoup sandbox orgs/ scaffolding; pick generic devcontainer setup skills for non-Recoup isolated workspaces.
FAQ
When should setup-sandbox run?
setup-sandbox runs when a Recoup sandbox was just created and has no orgs/ directory; if orgs/ already exists, the skill is not needed and should be skipped to avoid duplicate scaffolding.
How does setup-sandbox authenticate to Recoup?
setup-sandbox uses the Recoup CLI with RECOUP_ACCOUNT_ID when an Org API Key is configured, or omits --account with a Personal API Key so the CLI uses the authenticated account automatically.
Is Setup Sandbox safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.