recoup-setup-sandbox
Set up the initial file system for a new sandbox. Fetches the account's organizations and artists via the Recoup REST API 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.
What this skill does
# Setup Sandbox
**Before running, check:** `ls orgs/` from the sandbox root. If the directory exists and contains org folders, the sandbox is already set up — stop here and read the `recoup-artist-workspace` skill instead. Only continue if `orgs/` doesn't exist or is empty.
Create the folder structure for the connected account's organizations and artists by calling the Recoup REST API.
## Environment & auth
This skill calls the Recoup API directly — the same conventions as the `recoup-api` skill:
- **Base URL:** `https://api.recoupable.com/api`
- **Auth:** `Authorization: Bearer $RECOUP_ACCESS_TOKEN` (the sandbox's account-scoped access token).
- **`RECOUP_ORG_ID`** *(optional)* — when set, the sandbox was opened for one specific org; scaffold only that org. When unset, scaffold every org the account belongs to.
If `RECOUP_ACCESS_TOKEN` is empty, the user is not authenticated — tell them to sign in rather than retrying. Defer to the `recoup-api` skill if any call shape is unclear.
Set up the shared request pieces once:
```bash
BASE="${RECOUP_API_URL:-https://api.recoupable.com/api}"
AUTH=(-H "Authorization: Bearer $RECOUP_ACCESS_TOKEN")
# Turn any display name into a lowercase-kebab-case slug for folder names.
slugify() { echo "$1" | tr '[:upper:]' '[:lower:]' | sed -E 's/[^a-z0-9]+/-/g; s/^-+|-+$//g'; }
```
## Steps
1. **List the account's organizations** — `GET /api/organizations`. Each item has `organization_id` and `organization_name`:
```bash
curl -sS "${AUTH[@]}" "$BASE/organizations" \
| jq -r '.organizations[] | [.organization_id, .organization_name] | @tsv'
```
If `RECOUP_ORG_ID` is set, keep only the row whose `organization_id` matches it.
2. **List each org's artists** — `GET /api/artists?org_id={organization_id}`. Each artist has `account_id` (the UUID) and `name` — there is **no slug field**, so derive the folder name from `name` with `slugify`:
```bash
curl -sS "${AUTH[@]}" "$BASE/artists?org_id=$ORG_ID" \
| jq -r '.artists[] | [.account_id, .name] | @tsv'
```
3. **Scaffold folders + a `RECOUP.md` marker** for each artist:
- Org folder name = `slugify(organization_name)`; artist folder name = `slugify(name)`.
- Never append UUIDs, IDs, or suffixes to folder names.
- If `orgs/{org-slug}/artists/{artist-slug}/` already exists, skip it.
- `mkdir -p orgs/{org-slug}/artists/{artist-slug}` for each new artist.
- Write a `RECOUP.md` using the template below.
4. **Commit and push:**
```bash
git add -A && git commit -m "setup: create org and artist folders" && git push
```
5. Read the `recoup-artist-workspace` skill — it teaches how to work inside the directories you just created.
### Putting it together
```bash
# Resolve which orgs to scaffold (one if RECOUP_ORG_ID is set, else all).
curl -sS "${AUTH[@]}" "$BASE/organizations" \
| jq -r --arg only "${RECOUP_ORG_ID:-}" \
'.organizations[] | select($only == "" or .organization_id == $only)
| [.organization_id, .organization_name] | @tsv' \
| while IFS=$'\t' read -r ORG_ID ORG_NAME; do
ORG_SLUG=$(slugify "$ORG_NAME")
curl -sS "${AUTH[@]}" "$BASE/artists?org_id=$ORG_ID" \
| jq -r '.artists[] | [.account_id, .name] | @tsv' \
| while IFS=$'\t' read -r ARTIST_ID ARTIST_NAME; do
ARTIST_SLUG=$(slugify "$ARTIST_NAME")
DIR="orgs/$ORG_SLUG/artists/$ARTIST_SLUG"
[ -d "$DIR" ] && continue
mkdir -p "$DIR"
cat > "$DIR/RECOUP.md" <<EOF
---
artistName: $ARTIST_NAME
artistSlug: $ARTIST_SLUG
artistId: $ARTIST_ID
---
EOF
done
done
```
## `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.
```markdown
---
artistName: {Artist Name}
artistSlug: {artist-slug}
artistId: {uuid-from-recoupable}
---
```
**Fields (mapped from the `GET /api/artists` response):**
- `artistName` — `name`, the display name (e.g. `Gatsby Grace`)
- `artistSlug` — `slugify(name)`, lowercase-kebab-case folder name (e.g. `gatsby-grace`)
- `artistId` — `account_id`, the artist account UUID from Recoup
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.