setup-sandbox▌
recoupable/setup-sandbox · updated Apr 8, 2026
Initial file system scaffolding for Recoup sandbox accounts with organizations and artists.
- ›Fetches organizations and artists from the connected Recoup account via CLI, then creates an opinionated folder structure under orgs/{org}/artists/{artist-slug}
- ›Generates a RECOUP.md identity file in each artist directory to track setup status and connect the workspace to the Recoupable platform
- ›Requires RECOUP_ACCOUNT_ID environment variable only when using an Org API Key; omit it for Persona
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
- Check if
RECOUP_ACCOUNT_IDis set. If set, use--account $RECOUP_ACCOUNT_IDon all CLI commands below. If not set, omit the--accountflag. - Run
recoup orgs list --json [--account $RECOUP_ACCOUNT_ID]to get all organizations - For each organization, run
recoup artists list --org {organization_id} --json [--account $RECOUP_ACCOUNT_ID]to get its artists - Create the folder structure and a
RECOUP.mdmarker 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
- Use
- 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
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
setup-sandbox is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Sep 9, 2024
Keeps context tight: setup-sandbox is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Registry listing for setup-sandbox matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakshi Patil· Jul 7, 2024
setup-sandbox reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend setup-sandbox for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· May 5, 2024
Useful defaults in setup-sandbox — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Dhruvi Jain· Apr 4, 2024
setup-sandbox has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Rahul Santra· Mar 3, 2024
Solid pick for teams standardizing on skills: setup-sandbox is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Feb 2, 2024
We added setup-sandbox from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Jan 1, 2024
setup-sandbox fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.