# Recoup Release Track Drop

> Confirm a release actually dropped and build a launch-day alert — checks whether the single/album went live and surfaces the first-day signals. Use for "did [artist]'s single drop", "launch alert", or "watch for the drop". Idempotent and dated; saves to the release workspace. For ongoing weekly streaming-spike watching use recoup-research-weekly-brief.

- Skill: `recoupable-skills/recoup-release-track-drop` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add recoupable-skills/recoup-release-track-drop`
- Raw SKILL.md: https://api.skillmd.com/api/skills/recoupable-skills/recoup-release-track-drop/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: recoupable (https://skillmd.com/u/recoupable-skills)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/recoupable-skills/recoup-release-track-drop

---


# Recoup Release — Track Drop

Confirm the release dropped and build a launch-day alert from the research API.
Idempotent + dated; save to `releases/{artist-slug}/{release-slug}/tracking/`.

## Procedure

Check whether the release is live (search + `/research/albums`/`/tracks` for the
title), then pull launch-day signals (Spotify metrics, playlists, milestones).
Classify the launch (live yet? on any playlists? early streaming?) and write a dated
tracking file + a short chat summary. If it isn't live yet, say so — don't fabricate.

For ongoing streaming-spike watching across the catalog, use
recoup-research-weekly-brief (streaming scope).

## Guardrails

- **Idempotent + dated** — re-runs surface the existing file rather than duplicate.
- **Never fabricate** a drop, placement, or number.

## References

- `references/response-shapes.md` — research API shapes.