subscription-recovery

Featured

Suede-owned recovery discipline for recurring charges billed outside Amazon: App Store, Google Play, PayPal, direct-bill streaming, gyms, news, and SaaS. Use when the user wants to find, audit, cancel, or dispute a subscription they may have forgotten, is being charged for twice, or no longer uses. Every cancellation and dispute requires the user to name the service first. Never enters payment credentials and never promises a refund. 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-returns-recovery); merchant-side dunning and cancel-flow design (use suede-churn-prevention).

AI & Automation 135 stars 10 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Subscription Recovery ``` IRON LAW: Never cancel, dispute, or contact a merchant about a service until the user has named that specific service and the specific outcome they want for it. A subscription appearing in a discovery list is not authorization to act on it. ``` ## Prerequisites - Claude in Chrome browser extension connected, for any service checked or acted on in-browser. If `mcp__claude-in-chrome__*` tools aren't loaded yet, fetch them via ToolSearch first. - Unlike amazon-returns-recovery, there is no single account to sweep — discovery depends on what the user can provide (a bank/card statement, app access, or just naming what they remember paying for) and what platform-level subscription hubs are available (App Store, Google Play, PayPal). - **Unvalidated click-paths.** Only the App Store, Google Play, and PayPal hub pages in Phase 1a are close to a fixed, checkable URL. Every individual service's own billing/cancellation page (Netflix, Spotify, a gym's member portal, etc.) has to be discovered live and should be recorded in [references/service-playbook.md](references/service-playbook.md) once confirmed, so the next run doesn't rediscover it from scratch. ## Phase 1a — Platform subscription hubs (read-only, no side effects) These three cover a large share of subscriptions in one page each, because the platform (not the individual service) is the merchant of record: 1. **Apple App Store** (iOS/iPadOS/Mac subscriptions bought through App...

Details

Author
JasonColapietro
Repository
JasonColapietro/suede-creator-skills
Created
3 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

amazon-returns-recovery

Suede-affiliated Amazon money-recovery audit for restocking fees, short or denied refunds, and Amazon-billed subscriptions. Use when the user mentions a restocking fee, a short or denied Amazon refund, or a forgotten Prime Video Channel, Audible, Kindle Unlimited, or Prime charge, or asks whether Amazon still owes or bills them. Read-only discovery; no chat, cancellation, or dispute without the account owner's per-item confirmation, and never a promise of recovery. Requires an authenticated Claude in Chrome session. NOT FOR: bank chargebacks, marketplace A-to-z seller claims, price-protection claims, or subscriptions billed outside Amazon (use subscription-recovery).

135 Updated today
JasonColapietro
AI & Automation Listed

cancel-unsubscribe

Cancel a subscription or unsubscribe from a service. Works from a description, a pasted charge line, a URL, or a photo/screenshot. Can also audit a full statement for recurring charges and cancel several at once. Finds the right contact method and handles the cancellation — including phone calls.

78 Updated 6 days ago
Razshy
AI & Automation Featured

suede-churn-prevention

Suede-owned retention discipline for voluntary and involuntary churn: cancel flows, pause paths, evidence-based save offers, failed-payment recovery, proactive signals, and win-back design. Use when diagnosing subscriber loss or designing a bounded retention intervention. NOT FOR: lifecycle-email production (use suede-emails), pricing architecture (use suede-pricing), paywall design (use suede-paywalls), or event instrumentation (use suede-analytics).

135 Updated today
JasonColapietro