Agent skill · Security

subscription-recovery

Use when the user wants to find, audit, cancel, or dispute recurring charges billed outside Amazon, including App Store, Google Play, PayPal, direct-bill streaming, gyms, news, and SaaS. Discover charges from evidence the user directly provides or authenticated service pages, report findings first, and require confirmation before cancellation or refund contact. Never enter payment credentials or promise recovery. Requires Claude in Chrome for browser actions. NOT FOR: Amazon returns, restocking fees, or Amazon-billed Prime Video Channels, Audible, Kindle Unlimited, or Prime — use amazon-return

JasonColapietrogithub.com/JasonColapietroGitHub ↗
claude-codecodexMIT
Install
npx skills add JasonColapietro/suede-creator-skills --skill subscription-recovery --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/subscription-recovery/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 165
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Subscription Recovery ## Why this exists The [amazon-returns-recovery](../amazon-returns-recovery/SKILL.md) skill proved the underlying idea on Amazon: money doesn't announce itself when it's still being charged, only when someone goes and checks. Restocking fees and Amazon-billed subscriptions (Prime Video Channels routes Britbox, Starz, AMC+, and friends through one Amazon bill) are one slice of that. Most people's actual subscription sprawl is bigger and more scattered — a streaming service billed directly by its own app, a gym membership, a SaaS tool from a free trial that converted, a magazine, an App Store subscription bought once and forgotten. None of that goes through Amazon at all. This skill is the same negotiation discipline — build the case from real facts, confirm before acting, hold the line under a counteroffer, get the outcome confirmed in writing — pointed at *anything* recurring, not just an Amazon account. Treat this as a metal detector, not an autopilot: it surfaces what's being charged and drafts the case, but every cancellation and every dispute goes through the account owner before anything gets sent or clicked. **Scope split with amazon-returns-recovery**

What's inside
Steps it walks through
  1. Why this exists
  2. Prerequisites
  3. Phase 1a — Platform subscription hubs (read-only, no side effects)
  4. Phase 1b — Bank/card statement scan (read-only, no side effects)
  5. Phase 1c — Ask directly
  6. Phase 1d — Amazon carve-out
  7. Phase 2 — Confirm with the user
  8. Phase 3 — Execute (one service at a time, only after confirmation)
  9. Phase 4 — Report
  10. Stretch goal — not yet built
Ships with 2 files
  • agents/openai.yaml
  • references/service-playbook.md
More from suede-creator-skills
All skills →
About this skill
What does the subscription-recovery skill do?

Use when the user wants to find, audit, cancel, or dispute recurring charges billed outside Amazon, including App Store, Google Play, PayPal, direct-bill streaming, gyms, news, and SaaS. Discover charges from evidence the user directly provides or authenticated service pages, report findings first, and require confirmation before cancellation or refund contact. Never enter payment credentials or promise recovery. Requires Claude in Chrome for browser actions. NOT FOR: Amazon returns, restocking fees, or Amazon-billed Prime Video Channels, Audible, Kindle Unlimited, or Prime — use amazon-return

How do I install it?

Run `npx skills add JasonColapietro/suede-creator-skills --skill subscription-recovery --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going