recoup-playlist-intelligence
Playlist pitching intelligence, gap analysis, and catalog optimization via the Recoup research API. Use when asked about playlist placements, pitch targets, playlist gaps, which playlists an artist should be on, editorial vs algorithmic coverage, track-level playlist analysis, or catalog optimization ("which songs should we push"). Triggers on "playlist pitch", "playlist targets", "which playlists", "playlist gap", "editorial placements", "catalog optimization", "which songs should we push".
What this skill does
# Playlist Intelligence
Playlist pitching targets, gap analysis, and catalog optimization through the
Recoup research API. Turns raw playlist data into actionable pitch lists and
catalog strategy. The API is backed by **Songstats** — IDs are short
alphanumeric strings, not numeric Chartmetric IDs.
```bash
export RECOUP_API_KEY="recoup_sk_..."
export RECOUP_API="https://api.recoupable.com/api"
```
## Decision tree
- **"Which playlists should we pitch?"** → Playlist Pitching Intelligence workflow
- **"Where are we playlisted?"** → `/research/playlists?artist={ARTIST}&status=current` → synthesize
- **"Playlist gap analysis"** → compare vs similar artists' placements
- **"Which songs should we push?"** → Catalog Optimization workflow
- **"Track-level / editorial playlist coverage"** → resolve track ID → `/research/track/playlists`
- **"Re-pitch opportunities"** → `/research/playlists?artist={ARTIST}&status=past`
## Playlist Pitching Intelligence
Find the playlists your similar artists are on that you aren't.
```bash
# 1. Find similar artists (benchmarks slightly bigger than you)
curl -s "$RECOUP_API/research/similar?artist={ARTIST}&audience=high&genre=high&limit=50" \
-H "x-api-key: $RECOUP_API_KEY"
# 2. For each similar artist, get their current playlist placements
curl -s "$RECOUP_API/research/playlists?artist={similar_artist}&platform=spotify&status=current" \
-H "x-api-key: $RECOUP_API_KEY"
# 3. Look for overlap — playlists hosting multiple similar artists
# 4. For per-track editorial detail, resolve a track id, then page the track-level endpoint
curl -s "$RECOUP_API/research?q={TRACK_NAME}&type=tracks" \
-H "x-api-key: $RECOUP_API_KEY" # get track id
curl -s "$RECOUP_API/research/track/playlists?id={track_id}&editorial=true&indie=true&majorCurator=true&popularIndie=true" \
-H "x-api-key: $RECOUP_API_KEY"
# 5. Check if the target artist was ever on these playlists before
curl -s "$RECOUP_API/research/playlists?artist={ARTIST}&status=past" \
-H "x-api-key: $RECOUP_API_KEY"
```
**Synthesize:** Playlists that already host similar artists but haven't added
yours yet. Prioritize playlists hosting 2+ similar artists — they're the warmest
targets.
## Catalog Optimization
Which songs should we push, and where?
```bash
# 1. All tracks
curl -s "$RECOUP_API/research/tracks?artist={ARTIST}" -H "x-api-key: $RECOUP_API_KEY"
# 2. Current placements
curl -s "$RECOUP_API/research/playlists?artist={ARTIST}&status=current" -H "x-api-key: $RECOUP_API_KEY"
# 3. Per-track playlist coverage (resolve track ID first; 5 credits)
curl -s "$RECOUP_API/research?q={TRACK_NAME}&type=tracks" -H "x-api-key: $RECOUP_API_KEY"
curl -s "$RECOUP_API/research/track/playlists?id={track_id}&editorial=true&indie=true&majorCurator=true&popularIndie=true" -H "x-api-key: $RECOUP_API_KEY"
# 4. Albums (needs the provider artist ID — resolve via search)
curl -s "$RECOUP_API/research?q={ARTIST}&type=artists" -H "x-api-key: $RECOUP_API_KEY" # get id
curl -s "$RECOUP_API/research/albums?artist_id={artist_id}" -H "x-api-key: $RECOUP_API_KEY"
# 5. Track detail (genres, audio analysis) for sound fit + metrics for trend context
curl -s "$RECOUP_API/research/track?id={track_id}" -H "x-api-key: $RECOUP_API_KEY"
curl -s "$RECOUP_API/research/metrics?artist={ARTIST}&source=spotify" -H "x-api-key: $RECOUP_API_KEY"
```
**Synthesize:** Track-by-track analysis:
- Tracks on many playlists but not converting to streams = discovery issue
- Tracks with strong audio-analysis fit for a target playlist = pitch candidates
- Old songs suddenly getting playlisted (from `/milestones`) = catalog momentum
## Critical gotchas — Playlists
- **Two different playlist endpoints.** `/research/playlists` is **artist-level**
(`status` + `platform` + `limit` only — no editorial/indie filter flags).
`/research/track/playlists` is **track-level** and is the one with filter flags.
- **Track-level filter flags are exclusive when set.** On `/research/track/playlists`,
`?editorial=true` alone returns ONLY editorials. To get editorial *plus* the
defaults, pass all four:
`&editorial=true&indie=true&majorCurator=true&popularIndie=true`. With no flags
it defaults to `editorial + indie + majorCurator + popularIndie`.
- **`placements[].followers_total` is a formatted string** (`"34.3M"`) on
artist-level placements, not an integer. Parse it if you need to sort numerically.
There is no `peak_position` or nested `playlist`/`track` wrapper anymore.
- **For editorial magnitude, read `playlists_editorial_current` from
`/research/metrics?source=spotify`** — that's the aggregate count.
- **No `/research/playlist` (singular) or `/research/curator` detail endpoint.**
Use the `external_url` on each placement to open the playlist directly.
- **Past placements (`status=past`) that dropped off = re-pitch opportunities.**
## Interpretation rules
- Low `playlists_editorial_current` (from /metrics) for an artist with millions of listeners = severely under-playlisted (pitch immediately)
- Past placements that dropped off = re-pitch candidates
- Playlists hosting multiple peers = warmest pitch targets
- `playlist_reach_current` from `/metrics` gives the magnitude; `/playlists` gives the sampled list
## Output format
Produce a ranked pitch list:
| Playlist | Followers | Peers On It | Artist Status | Priority |
|----------|-----------|-------------|---------------|----------|
| RapCaviar | 15.7M | 5/10 peers | Never on | 🔴 High |
| Chill Vibes | 200K | 3/10 peers | Past (dropped 3mo ago) | 🟡 Re-pitch |
(Curator names aren't returned by the API anymore — link the playlist via its
`external_url` instead.)
## References
- **`references/endpoints.md`** — full playlist filter/pagination semantics
- **`references/response-shapes.md`** — placement JSON structure
- **`references/workflows.md`** — Workflow 1 (Playlist Pitching) and Workflow 5 (Catalog Optimization)
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.