How do I install the Recoup Research Weekly Brief skill?

Run npx skillmds add recoupable-skills/recoup-research-weekly-brief in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Recoup Research Weekly Brief safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Recoup Research Weekly Brief?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Recoup Research Weekly Brief free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Recoup Research Weekly Brief?

recoupable (@recoupable-skills) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Recoup Research Weekly Brief by recoupable-skills

Name: Recoup Research Weekly Brief
Rating: 4.5 (4 reviews)
Author: recoupable

Recoup Research Weekly Brief

The recurring "what changed this week" update for an artist — streaming/social deltas vs the last run, milestones, and a spike/drop check. Use for "weekly brief", "what's new this week", "what changed for [artist]", or "are streams spiking or dropping". Recurring and dated; diffs against your own prior file. For a one-time full sweep use recoup-research-artist-overview.

recoupable df503d5 2 files · 30.7 KB Updated Sep 9, 2026

File contents

Recoup Research — Weekly Brief

The recurring artifact a customer opens. Snapshots, not time series — the delta is vs your last file.

export RECOUP_API="https://api.recoupable.dev/api"   # auth header: x-api-key: $RECOUP_API_KEY

Procedure (idempotent, dated, diffed)

Idempotency: if today's file already exists at artists/{slug}/research/brief-$(date +%F).md, stop and surface it. Read the prior brief for the baseline, then fan out in parallel:

curl -s "$RECOUP_API/research/metrics?artist={ARTIST}&source=spotify"   -H "x-api-key: $RECOUP_API_KEY" &
curl -s "$RECOUP_API/research/metrics?artist={ARTIST}&source=tiktok"    -H "x-api-key: $RECOUP_API_KEY" &
curl -s "$RECOUP_API/research/metrics?artist={ARTIST}&source=instagram" -H "x-api-key: $RECOUP_API_KEY" &
curl -s "$RECOUP_API/research/milestones?artist={ARTIST}" -H "x-api-key: $RECOUP_API_KEY" &
curl -s "$RECOUP_API/research/insights?artist={ARTIST}"   -H "x-api-key: $RECOUP_API_KEY" &
wait

Compute deltas vs the prior brief. Streaming spot-check sub-mode ("are streams spiking?"): pull Spotify metrics + playlists + milestones, classify SPIKE/DROP/FLAT (≥15% or a large absolute move), and name the likely cause only if it appears in the feed. Write a dated file + a short chat summary. First reading shows current values with "first reading" in the Δ column.

Guardrails

Snapshots, not history — deltas come from diffing your own prior file.
No invented numbers / no causation without evidence.
Credits: surface checkoutUrl on insufficient_credits.

References

references/workflows.md — metrics interpretation + TikTok-to-Spotify pipeline.

---name: recoup-research-weekly-briefdescription: The recurring "what changed this week" update for an artist — streaming/social deltas vs the last run, milestones, and a spike/drop check. Use for "weekly brief", "what's new this week", "what changed for [artist]", or "are streams spiking or dropping". Recurring and dated; diffs against your own prior file. For a one-time full sweep use recoup-research-artist-overview.--- # Recoup Research — Weekly Brief The recurring artifact a customer opens. Snapshots, not time series — the delta is vs your last file. ```bash export RECOUP_API="https://api.recoupable.dev/api" # auth header: x-api-key: $RECOUP_API_KEY ``` ## Procedure (idempotent, dated, diffed) **Idempotency:** if today's file already exists at `artists/{slug}/research/brief-$(date +%F).md`, stop and surface it. Read the prior brief for the baseline, then fan out in parallel: ```bash curl -s "$RECOUP_API/research/metrics?artist={ARTIST}&source=spotify" -H "x-api-key: $RECOUP_API_KEY" & curl -s "$RECOUP_API/research/metrics?artist={ARTIST}&source=tiktok" -H "x-api-key: $RECOUP_API_KEY" & curl -s "$RECOUP_API/research/metrics?artist={ARTIST}&source=instagram" -H "x-api-key: $RECOUP_API_KEY" & curl -s "$RECOUP_API/research/milestones?artist={ARTIST}" -H "x-api-key: $RECOUP_API_KEY" & curl -s "$RECOUP_API/research/insights?artist={ARTIST}" -H "x-api-key: $RECOUP_API_KEY" & wait ``` Compute deltas vs the prior brief. **Streaming spot-check sub-mode** ("are streams spiking?"): pull Spotify metrics + playlists + milestones, classify SPIKE/DROP/FLAT (≥15% or a large absolute move), and name the likely cause only if it appears in the feed. Write a dated file + a short chat summary. First reading shows current values with "first reading" in the Δ column. ## Guardrails - **Snapshots, not history** — deltas come from diffing your own prior file. - **No invented numbers / no causation without evidence.** - **Credits:** surface `checkoutUrl` on `insufficient_credits`. ## References - `references/workflows.md` — metrics interpretation + TikTok-to-Spotify pipeline.

Frequently asked questions