PluginBench
Skill
Review
Audit score 70

setup-sandbox

recoupable/setup-sandbox

Initialize sandbox folder structure for Recoup organizations and artists.

What is setup-sandbox?

Set up the initial file system for a new sandbox by fetching organizations and artists from your Recoup account via CLI and scaffolding the required folder structure. Use this immediately after creating a sandbox, before any file system exists.

  • Fetches all organizations from the connected Recoup account
  • Retrieves artists for each organization
  • Creates org/artist folder hierarchy with correct naming
  • Generates RECOUP.md identity files in each artist directory
  • Commits and pushes the scaffolded structure to git

How to install setup-sandbox

npx skills add https://github.com/recoupable/setup-sandbox --skill setup-sandbox
Prerequisites
  • Recoup CLI installed and authenticated
  • RECOUP_ACCOUNT_ID environment variable set (for Org API Keys) or Personal API Key configured
  • Git repository initialized in the sandbox
Claude Code
Cursor
Windsurf
Cline

How to use setup-sandbox

  1. 1.Check if orgs/ directory already exists in the sandbox—if it does, skip this skill
  2. 2.Verify RECOUP_ACCOUNT_ID environment variable is set (required for Org API Keys, optional for Personal API Keys)
  3. 3.Run the skill to fetch organizations and artists from your Recoup account
  4. 4.Review the generated folder structure under orgs/{org}/artists/{artist-slug}/
  5. 5.Verify RECOUP.md files were created in each artist directory with correct metadata
  6. 6.The skill automatically commits and pushes changes to main branch

Use cases

Good for
  • Initialize a newly created sandbox with no existing file system
  • Set up folder structure for a fresh Recoup workspace
  • Establish the foundation for managing multiple organizations and artists
Who it's for
  • Recoup account administrators
  • Developers setting up new sandboxes
  • Teams managing multiple artist workspaces

setup-sandbox FAQ

When should I use this skill?

Use this skill immediately after creating a new sandbox that has no existing file system. If your sandbox already has an orgs/ directory, this skill is not needed.

What does RECOUP.md do?

RECOUP.md is the identity file that connects your workspace to the Recoupable platform. Its presence indicates the workspace is active. It contains artistName, artistSlug, and artistId metadata.

Do I need to set RECOUP_ACCOUNT_ID?

Only if you're using an Org API Key. If you're using a Personal API Key, omit the flag and the CLI will automatically use your authenticated account.

What naming convention is used for artist folders?

Artist folders use the artistSlug in lowercase-kebab-case format (e.g., gatsby-grace). Never append UUIDs or other suffixes to the directory name.

What happens if an artist folder already exists?

The skill skips creating folders that already exist and only creates new ones, preventing overwrites.

Full instructions (SKILL.md)

Source of truth, from recoupable/setup-sandbox.


name: setup-sandbox description: 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.

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 --account flag 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 artistSlug from 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.md using 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

More from recoupable/setup-sandbox and the wider catalog.

REredis-connections logo

redis-connections

Official
redis/agent-skills

Redis client and connection guidance covering connection pooling, multiplexing, pipelining, client-side caching with RESP3, avoiding slow commands (KEYS, SMEMBERS, HGETALL), and tuning socket timeouts. Use when configuring a Redis client (redis-py, Jedis, Lettuce, NRedisStack), batching commands for throughput, eliminating per-request connection creation, iterating large keyspaces with SCAN, enabling client-side caching for read-heavy workloads, or setting connect and read timeouts.

634 installsAudited
REredis-core logo

redis-core

Official
redis/agent-skills

Core Redis modeling guidance — choose the right data structure (String, Hash, List, Set, Sorted Set, JSON, Stream, Vector Set) and use consistent colon-separated key names. Use when designing a Redis data model, caching objects, deciding between Hash and JSON, building counters, leaderboards, membership sets, or session stores, or when reviewing/cleaning up Redis key naming.

837 installsAudited
REredis-development logo

redis-development

Official
redis/agent-skills

Redis performance optimization and best practices for data structures, query engines, vector search, and semantic caching.

3.2k installs
AGagent-ci logo

agent-ci

redwoodjs/agent-ci

Run GitHub Actions CI locally with Agent CI to validate changes before pushing. Use when testing, running checks, or validating code changes.

1.2k installs
RErefero-design logo

refero-design

referodesign/refero_skill

Research-first design skill for UI, product, web, and landing pages—grounded in real references, not generic AI taste.

3.9k installs
AIai-evals logo

ai-evals

refoundai/lenny-skills

Design and run systematic evaluations for AI products to measure model quality and output performance.

1.6k installs