/subscription-recovery · Consumer recovery; the negotiation lane, generalized beyond Amazon
You're still paying for something. Find it.
The App Store, Google Play, and PayPal each keep one page listing every merchant with standing permission to bill you. The skill builds the inventory from those three pages, your bank and card statements, and one direct ask: what you pay, what you use, and what you forgot. You name each service before it cancels or disputes anything, and it never touches payment credentials.
"what am I still paying for"->/subscription-recoveryAsk in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.
claude code · sample session
$ /subscription-recovery what am I paying forApp Store + Google Play + PayPal hubs scanned3 forgotten subscriptions surfaced · owner confirmedCANCELED · REFUNDS REQUESTED
Phase 1a discovery is read-only: checks the App Store, Google Play, and PayPal subscription hubs first, since each lists every merchant with standing billing authorization on one page; the highest-leverage single sources.
Phase 1b scans a bank or card statement the user shares for recurring merchant charges those hubs miss (direct-bill services like Netflix, Hulu, a gym).
Phase 1c asks the user directly for anything else they know they're paying for; people typically remember 60-70% unprompted and the rest only when asked.
Phase 1d hands off Amazon-billed subscriptions (Prime Video Channels, Audible, Kindle Unlimited) to amazon-returns-recovery instead of duplicating that flow.
Phase 2 stops and reports: service, price, billing cadence, next charge date, and usage signal; the account owner picks which to pursue and what outcome they want per service.
Phase 3 executes: straight cancellations go through the platform hub or the service's own settings page directly, no negotiation needed. Refund/goodwill asks for genuinely forgotten charges use the same ground rules as amazon-returns-recovery; state only true facts, one polite counter, confirm the outcome in writing.
A growing references/service-playbook.md records each service's validated click-path once confirmed live, so later runs don't rediscover it from scratch.
Phase 4 reports per service: canceled, refunded, or disputed and declined; with one-time dollars kept separate from ongoing monthly/annual savings.
When to use it
The user wants to audit recurring charges generally, or asks "what am I still paying for."
The user names a specific non-Amazon subscription: Netflix, Spotify, a gym, a SaaS tool, a news site, an App Store or Google Play subscription.
Finding and canceling subscriptions that look forgotten or unused, or disputing a charge (billed twice, charged after a cancellation attempt).
Requires the Claude in Chrome browser extension for anything checked or acted on in-browser; some services may need the user to share a statement or app screen directly.
Not for: Amazon-billed subscriptions or Amazon returns/restocking fees (use amazon-returns-recovery instead), automated statement parsing without the user directly sharing it, or entering payment credentials on the user's behalf.
Best prompt
Use $subscription-recovery to audit my recurring subscriptions across App Store, Google Play, PayPal, and anything else I'm paying for, report what you find, and after I confirm which ones to pursue, cancel them directly or negotiate a refund through that service's support.
Related skills
Pairs with amazon-returns-recovery, which stays scoped to Amazon: returns, restocking fees, and Amazon-billed subscriptions like Prime Video Channels and Audible. Together they're the pack's negotiation lane run against real accounts instead of a repo or a brief; the same discipline the code and copy lanes apply elsewhere in the pack.
Install this skill
It ships inside the Suede Creator Skills pack, so one install brings the whole pack and this skill with it. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.