
Setup Artist
Scaffold a complete music-artist workspace (directories, context, memory, config) inside a Recoup sandbox after org setup.
Overview
Setup Artist is an agent skill for the Build phase that scaffolds a complete Recoup artist workspace with context, memory, config, and per-directory READMEs inside an existing sandbox.
Install
npx skills add https://github.com/recoupable/setup-artist --skill setup-artistWhat is this skill?
- Creates full artist directory tree with README in every folder
- Populates context templates (identity, audience, era, tasks, images)
- Sets up scope-aware memory (MEMORY.md + README)
- Lean SERVICES.md and .env templates without pre-filled JSON
- Requires setup-sandbox skill first for org/artist folders
- README files for every directory
- reference templates for context, memory, services, and env
Adoption & trust: 1.1k installs on skills.sh; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have org/artist folders from setup-sandbox but no standardized artist workspace, context files, or agent instructions for where creative assets live.
Who is it for?
Recoup users onboarding a new artist in a sandbox who want agent-safe folder conventions before writing songs, releases, or automation.
Skip if: Teams not using Recoup sandboxes, or cases where setup-sandbox has not been run yet.
When should I use this skill?
User asks to set up, create, or initialize an artist workspace or directory for a named artist after sandbox exists.
What do I get? / Deliverables
You get a fully templated artist tree ready for agents to fill in data or placeholders, with memory scope rules and a lean services guide to extend as integrations are added.
- Full artist directory tree
- context/ and memory/ templates
- config/SERVICES.md and .env stubs
Recommended Skills
Journey fit
Workspace scaffolding is canonical on the Build shelf because it materializes agent-ready project structure and context files before day-to-day creative ops. agent-tooling fits because the skill defines where agents read/write identity, audience, era, songs, and services—not application runtime code.
How it compares
Use as structured workspace scaffolding—not a generic monorepo generator or music distribution MCP.
Common Questions / FAQ
Who is setup-artist for?
Solo builders and small teams using Recoup sandboxes who need a repeatable artist workspace layout for AI agents and human collaborators.
When should I use setup-artist?
During Build agent-tooling after setup-sandbox, when prompts like “Set up the workspace for [Artist Name]” or “Initialize [Artist Name]'s artist workspace” apply.
Is setup-artist safe to install?
It scaffolds files and templates locally in your sandbox; review the Security Audits panel on this page before trusting third-party skill sources.
Workflow Chain
Requires first: setup sandbox
SKILL.md
READMESKILL.md - Setup Artist
# Recoup Setup Artist Skill An LLM skill for scaffolding a complete artist workspace inside a sandbox environment. ## What It Does - Creates the full directory structure for an artist workspace - Populates context files (identity, audience, era) - Sets up the memory system with scope-aware instructions (MEMORY.md + README) - Creates a lean services guide (no pre-filled JSON) and environment files - Creates README files for every directory so agents know what goes where - Fills in artist data when available, uses placeholders when not ## Prerequisites Run the `setup-sandbox` skill first to create the org/artist folder structure. ## Usage > "Set up the workspace for [Artist Name]" > "Create artist directory for [Artist Name]" > "Initialize [Artist Name]'s artist workspace" ## Files | File | Purpose | |------|---------| | `SKILL.md` | Core skill instructions | | `references/context-files.md` | Templates for `context/` files (artist, audience, era, tasks, images) | | `references/memory-system.md` | Templates for the `memory/` directory (includes scope system) | | `references/services-guide.md` | Template for `config/SERVICES.md` — lean, add-as-you-go approach | | `references/env-template.md` | Templates for `.env.example` and `.env` files | | `references/directory-readmes.md` | Templates for `songs/`, `releases/`, `config/`, `library/`, `apps/` READMEs | | `references/root-readme.md` | Template for the root `README.md` | --- name: setup-artist description: Set up the workspace for a new artist inside a sandbox. Creates the directory structure, context files, memory system, and placeholder content so agents can immediately start working. Use after setup-sandbox has created the org/artist folders, when RECOUP.md has status not-setup. Triggers on "set up artist", "create artist workspace", "initialize artist", or "onboard new artist". --- # Setup Artist Scaffold a complete artist workspace so agents can start working immediately. ## Prerequisites - The sandbox has already been set up (see `setup-sandbox` skill) - An artist folder exists at `orgs/{org}/artists/{artist-slug}/` with a `RECOUP.md` marker file - The `RECOUP.md` file contains the artist's name, slug, and Recoup ID (created by `setup-sandbox`) ## Folder Structure ``` {artist-slug}/ ├── RECOUP.md ├── README.md ├── .env.example ├── .env ├── context/ │ ├── artist.md │ ├── audience.md │ ├── era.json │ ├── tasks.md │ └── images/ │ └── README.md ├── memory/ │ ├── README.md │ └── MEMORY.md ├── songs/ │ └── README.md ├── releases/ │ └── README.md ├── content/ │ ├── README.md │ ├── images/ │ └── videos/ ├── config/ │ ├── README.md │ └── SERVICES.md ├── library/ │ └── README.md └── apps/ └── README.md ``` ## Steps ### Step 1: Read `RECOUP.md` and create the directory structure 1. Navigate to the artist folder and read `RECOUP.md` to get the artist's name, slug, and ID: ```bash cd orgs/{org}/artists/{artist-slug} cat RECOUP.md ``` 2. Create the directory structure: ```bash mkdir -p {context/images,memory,songs,releases,content/images,content/videos,config,library,apps} ``` ### Step 2: Update `RECOUP.md` Update the `status` field from `not-setup` to `active` and replace the body with a brief description: ```markdown --- artistName: {Artist Name} artistSlug: {artist-slug} artistId: {uuid-from-recoupable} status: active --- # {Artist Name} Connects this workspace to the Recoupable platform. See `README.md` for the full directory guide and setup checklist. ``` ### Step 3: Create context files Create each file from the templates in `references/context-files.md`. The essential files: | File | What to do | |------|-----------| | `context/artist.md` | Fill with artist identity, brand, visual world, voice, tone. Ask the user for details or research the artist. | | `context/audience.md` | Fill with audience insights. Focus on WHY they listen, what they relate to, how they talk. | | `context/era.json` | Set the current rele