setup-sandbox

Initial file system scaffolding for Recoup sandbox accounts with organizations and artists.

recoupable/setup-sandboxUpdated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/recoupable/setup-sandbox --skill setup-sandbox

0

installs

0

this week

stars

What it does

  • 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

Category

Productivity

Last updated

Apr 8, 2026

Installation Guide

How to use setup-sandbox on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add setup-sandbox
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/recoupable/setup-sandbox --skill setup-sandbox

Fetches setup-sandbox from recoupable/setup-sandbox and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/setup-sandbox

Restart Cursor to activate setup-sandbox. Access via /setup-sandbox in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

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

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.740 reviews
  • D
    Diya NasserDec 24, 2024

    setup-sandbox is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • V
    Valentina GonzalezDec 20, 2024

    Keeps context tight: setup-sandbox is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • H
    Harper ChoiDec 20, 2024

    I recommend setup-sandbox for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • A
    Aditi ChenNov 15, 2024

    setup-sandbox reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • M
    Mateo TorresNov 11, 2024

    Registry listing for setup-sandbox matched our evaluation — installs cleanly and behaves as described in the markdown.

  • A
    Amelia FarahOct 6, 2024

    Registry listing for setup-sandbox matched our evaluation — installs cleanly and behaves as described in the markdown.

  • V
    Valentina GhoshOct 2, 2024

    setup-sandbox reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Y
    Yusuf RobinsonSep 25, 2024

    Solid pick for teams standardizing on skills: setup-sandbox is focused, and the summary matches what you get after install.

  • A
    Aditi YangSep 25, 2024

    setup-sandbox fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • P
    Piyush GSep 21, 2024

    setup-sandbox has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 40

1 / 4

Discussion

Comments — not star reviews
  • No comments yet — start the thread.