Agent skill

Subscription Recovery

by JasonColapietro in JasonColapietro/suede-creator-skills

Suede-owned recovery discipline for recurring charges billed outside Amazon: App Store, Google Play, PayPal, direct-bill streaming, gyms, news, and SaaS.

MITAuto-check passedMobile

Install Subscription Recovery

skills CLI
$ npx skills add JasonColapietro/suede-creator-skills --skill subscription-recovery -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JasonColapietro/suede-creator-skills subscription-recovery --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/subscription-recovery .claude/skills/subscription-recovery && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
subscription-recovery
GitHub stars
127
Token cost
~2.2k tokens
SKILL.md length
1,085 words
Files
4 (incl. references)
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Suede-owned recovery discipline for recurring charges billed outside Amazon: App Store, Google Play, PayPal, direct-bill streaming, gyms, news, and SaaS.

  • Works in 3 steps: Confirm with the user → Execute (one service at a time, only… → Report
  • The user wants to find
  • SKILL.md covers Prerequisites, Phase 1a: Platform…, Phase 1b: Bank/card statement… and Phase 1c: Ask directly, plus 6 more sections
  • Reaches apps.apple.com and play.google.com

What it does

Subscription Recovery is an agent skill from JasonColapietro/suede-creator-skills. 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…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `references/service-playbook.md`).

It sits in Mobile, covering App store release and Referral and retention marketing. It works with PayPal. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.

When your agent uses it

  • The user wants to find
  • Dispute a subscription they may have forgotten
  • Is being charged for twice

Example prompts

  • “/subscription-recovery”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Confirm with the user
  2. Execute (one service at a time, only after confirmation)
  3. Report

What it can do on your machine

Read from SKILL.md and the folder at commit e5f94d7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • apps.apple.com
    • play.google.com
    • paypal.com
    • reportaproblem.apple.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Subscription Recovery loads about 2.2k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 182 tokens; SKILL.md has 1,085 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~182
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JasonColapietro/suede-creator-skills at commit e5f94d7, republished under its MIT licence (© JasonColapietro). 1,085 words, ~2,156 tokens.

Download SKILL.mdSave it as .claude/skills/subscription-recovery/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
subscription-recovery
description
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).
metadata.version
1.0.0

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 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 Apple's in-app-purchase flow, many streaming apps route here instead of billing directly): https://apps.apple.com/account/subscriptions (requires Apple ID sign-in) or on-device: Settings → [Apple ID] → Subscriptions.
  2. Google Play: https://play.google.com/store/account/subscriptions, same idea for Android-purchased subscriptions.
  3. PayPal recurring payments: https://www.paypal.com/myaccount/autopay/: lists every merchant with standing authorization to charge the account, including ones that don't show up anywhere else (a common blind spot: an old free trial that converted, billed via PayPal, with no reminder email ever opened).

Each of these lists service name, price, billing cadence, and next charge date, and each has a direct cancel button on the same page: no negotiation needed for a straight cancellation found here.

Phase 1b: Bank/card statement scan (read-only, no side effects)

If the user can share a recent statement (PDF, CSV export, or even a screenshot of the transaction list), scan for recurring merchant names and amounts: the same charge appearing monthly/annually from the same merchant is the signal. This catches services that bill directly (Netflix, Hulu, Disney+, HBO Max, a gym, a SaaS tool) and aren't visible through the Phase 1a hubs. Ask for the statement rather than guessing; don't assume access to financial accounts.

Phase 1c: Ask directly

Ask the user what else they know they're paying for that Phase 1a/1b didn't surface: people usually remember 60-70% of their subscriptions when prompted but forget the rest until specifically asked. This is often faster than a statement scan for a first pass, and worth doing even after one.

Phase 1d: Amazon carve-out

If a subscription turns out to be Amazon-billed (Prime Video Channels, Audible, Kindle Unlimited, Prime itself), don't handle it here, hand off to amazon-returns-recovery's Phase 1b, which already documents those pages.

Phase 2: Confirm with the user

HALT. Discovery is over and nothing has been canceled, disputed, or contacted. Present the findings, then wait for the user. No service is acted on unless the user names it, silence, "sounds good," or a general go-ahead is not a naming.

Report every subscription found as a plain list: service, price, billing cadence, next charge date, and usage signal if known (last opened, last watched, last attended). Ask which ones to pursue and what outcome they want per service: cancel only, cancel and ask for the last charge back, or dispute a specific charge without canceling (e.g. billed twice in one month). Some subscriptions may turn out to still be wanted: don't assume every finding is a mistake, and say so if one looks intentional.

Show full SKILL.md (507 more words)Show less

Phase 3: Execute (one service at a time, only after confirmation)

Straight cancellation, no negotiation needed:

  • If found via Phase 1a (App Store, Google Play, or PayPal), cancel directly on that same hub page, fastest path, no chat required.
  • Otherwise navigate to the service's own account/billing settings and look for a direct cancel option before resorting to chat or a phone call.

Refund/goodwill ask (forgot to cancel, charged after a cancellation attempt, billed twice, or genuinely unused for months):

  • Use the same ground rules as amazon-returns-recovery: state only true facts (service name, price, charge date, and the real reason), don't invent a prior contact attempt or cancellation date that didn't happen, ask plainly for the specific outcome wanted, and accept one polite counteroffer round at most before reporting back rather than escalating with anything untrue.
  • Apple and Google have their own self-service refund-request flows separate from the subscription hub itself, Apple: https://reportaproblem.apple.com; Google Play: order history → "Report a problem" (or support.google.com refund request). These are usually faster than chat for App Store/Play Store charges and worth trying first.
  • For direct-bill services, most have either a support chat or a cancellation retention flow (which sometimes offers a discount or partial refund unprompted when the user tries to cancel), take the retention offer only if the user actually wants to keep the service at the lower price; otherwise decline and proceed with cancellation.

Record the working path. Once a service's actual cancellation/dispute flow is confirmed live, add it to references/service-playbook.md with the exact URL and click-path, the same way amazon-returns-recovery documents its own chat flow: this is what turns "unvalidated" into "validated" over time.

Phase 4: Report

After each cancellation or dispute resolves, report per service: what happened (canceled, refunded, disputed and declined), the confirmation identifier or confirmation email, the effective end date, and the refund amount and method. An outcome with no confirmation identifier or email is reported as unconfirmed, never as done. For anything unresolved, name the exact next contact and date.

If several services were pursued in one session, summarize as a running total: keep one-time dollars recovered separate from ongoing monthly/annual savings from cancellations, since they're not the same kind of money.

Boundaries

  • Keep billing records, customer identifiers, personal reasons, and support transcripts in the user's private session. Public playbook updates may contain generic navigation only.

  • Never enter, store, or transcribe payment credentials, card numbers, or bank logins, and never connect a financial account.

  • Never promise a refund amount, a refund timeline, or that a dispute will succeed.

  • Never act on a service the user has not named, and never batch several services under one approval.

  • Never dispute or cancel a charge the user recognizes as intentional.

  • Never escalate with a fact the user did not supply: no invented prior contact, cancellation date, or usage claim.

Routing

  • Amazon-billed subscriptions, returns, and restocking fees -> use amazon-returns-recovery.
  • Designing the cancel flow, dunning, retention offers, or save offers for a product the user sells -> use suede-churn-prevention. That skill is the merchant side; this one is the subscriber side.

© JasonColapietro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/subscription-recovery of JasonColapietro/suede-creator-skills.

  • SKILL.md
  • CARD.md
  • agents/openai.yaml
  • references/service-playbook.md

Open the folder on GitHubat commit e5f94d7

Compare with similar skills

Subscription Recovery next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Subscription Recovery compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Subscription Recovery this skillJasonColapietro/suede-creator-skills127—~2.2kAutomated safety check: PassMIT
Asocoreyhaines31/marketingskills54k1 repos~4kAutomated safety check: PassMIT
App Store Optimizationmanojbajaj95/claude-gtm-plugin105—~4.2kAutomated safety check: PassMIT
App Store Featuredappeeky/aso-skills2.2k—~1.9kAutomated safety check: PassMIT
Aso Auditappeeky/aso-skills2.2k—~1.6kAutomated safety check: PassMIT
Apple Appstore Reviewergithub/awesome-copilot40k2 repos~2.9kAutomated safety check: PassMIT

Similar skills

  • Aso

    coreyhaines31/marketingskills

    When the user wants to audit or optimize an App Store or Google Play listing.

    54k GitHub starsUsed in 1 repo~4k tokens
    MobileAuto-check passed
  • App Store Optimization

    manojbajaj95/claude-gtm-plugin

    A skill your agent uses when optimizing app store listings, researching keywords, or tracking mobile app performance on Apple App Store and Google Play Store.

    105 GitHub stars~4.2k tokensUpdated 23 days ago
    MobileAuto-check passed
  • App Store Featured

    appeeky/aso-skills

    When the user wants to get featured on the App Store or understand the editorial process.

    2.2k GitHub stars~1.9k tokensUpdated 4 days ago
    MobileAuto-check passed
  • Aso Audit

    appeeky/aso-skills

    When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking.

    2.2k GitHub stars~1.6k tokensUpdated 4 days ago
    MobileAuto-check passed
  • Apple Appstore Reviewer

    github/awesome-copilot

    Official

    Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.

    40k GitHub starsUsed in 2 repos~2.9k tokens
    MobileAuto-check passed
  • Aso Router

    appeeky/aso-skills

    Single entry point that routes any ASO, App Store, Google Play, app marketing, paid UA, monetization, retention, reviews, ratings, market-intel, or app-analytics question to the correct specialist…

    2.2k GitHub stars~2.7k tokensUpdated 4 days ago
    MobileAuto-check passed

More from JasonColapietro/suede-creator-skills

All 78 skills in this repo
  • Suede Release Linter

    JasonColapietro/suede-creator-skills

    Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.

    127 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check: notes
  • Creator Rights Passport

    JasonColapietro/suede-creator-skills

    Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.

    127 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check: notes
  • Suede Clip to Guide

    JasonColapietro/suede-creator-skills

    Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.

    127 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed
  • Suede MCP Release QA

    JasonColapietro/suede-creator-skills

    Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.

    127 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Android App Factory

    JasonColapietro/suede-creator-skills

    Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.

    127 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed
  • Suede Ad Creative

    JasonColapietro/suede-creator-skills

    Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.

    127 GitHub stars~5k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Subscription Recovery

What does Subscription Recovery do?

Suede-owned recovery discipline for recurring charges billed outside Amazon: App Store, Google Play, PayPal, direct-bill streaming, gyms, news, and SaaS. Subscription Recovery is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned recovery discipline for recurring charges billed outside Amazon: App Store, Google Play, PayPal, direct-bill streaming, gyms, news, and SaaS.

When should I use Subscription Recovery?

Subscription Recovery fits situations like: the user wants to find; dispute a subscription they may have forgotten; is being charged for twice.

How do I install Subscription Recovery in Claude Code?

Run `npx skills add JasonColapietro/suede-creator-skills --skill subscription-recovery -a claude-code`. Or copy the skill folder (skills/subscription-recovery in JasonColapietro/suede-creator-skills) into .claude/skills/subscription-recovery in your project. Claude Code loads it when a task matches its description.

How do I install Subscription Recovery in Codex?

Run `npx skills add JasonColapietro/suede-creator-skills --skill subscription-recovery -a codex`. Or copy the skill folder (skills/subscription-recovery in JasonColapietro/suede-creator-skills) into .agents/skills/subscription-recovery in your project. Codex loads it when a task matches its description.

Can I use Subscription Recovery in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JasonColapietro/suede-creator-skills --skill subscription-recovery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/subscription-recovery, .gemini/skills/subscription-recovery, .github/skills/subscription-recovery and .opencode/skills/subscription-recovery in your project.

What does Subscription Recovery need to run?

SKILL.md names no scripts, command-line tools or credentials: Subscription Recovery is instructions for the agent only.

Does Subscription Recovery access the network?

SKILL.md names 4 domains. In commands or code: apps.apple.com, play.google.com, paypal.com and reportaproblem.apple.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Subscription Recovery safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Subscription Recovery use?

Subscription Recovery is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Subscription Recovery use?

About 2.2k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 423 tokens, read only when the agent opens those files.

What are the alternatives to Subscription Recovery?

Skills that share tags, products or a category with Subscription Recovery: Aso (coreyhaines31/marketingskills, 54k stars), App Store Optimization (manojbajaj95/claude-gtm-plugin, 105 stars), App Store Featured (appeeky/aso-skills, 2.2k stars) and Aso Audit (appeeky/aso-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Subscription Recovery?

JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.

Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.