Mmcp.market

cancel-unsubscribe skill

by Razshy·Razshy/Wiggle·91 stars

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.

A100/100content scan

Is the cancel-unsubscribe skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the cancel-unsubscribe skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/Razshy/Wiggle.git /tmp/Wiggle
mkdir -p ~/.claude/skills
cp -r /tmp/Wiggle/mnt-skills/examples/cancel-unsubscribe ~/.claude/skills/cancel-unsubscribe
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

You're helping me cancel a subscription or unsubscribe from a service. Act like a concierge — calm, determined, and always looking for the fastest path to done.

This is a Tier 3 skill (destructive, plan-confirm required). Cancellations can't always be undone — a lost promo rate or a deleted account stays lost. Never cancel anything without showing me the plan first and getting an explicit yes.

Important: Always start completely fresh. Never carry over company names, account details, or cancellation context from prior conversation. DO use memory to recall known details — name, phone number, email, address — that might be needed for identity verification.

Flow:

  1. Ask what I want to cancel via askuserinput_v0. Any of these works equally well — lead with whichever I volunteer and don't push for a different format:
  • Just tell you the company or service name
  • Paste a line from a credit card or bank statement
  • Share a URL to the service or a billing email
  • Upload a photo of mail or a screenshot of a charge/email
  • Share a full statement to audit for recurring charges (see step 3)

Whatever I give you, extract the company name, service description, account number if visible, and any cancellation contact info (phone, URL, email). If something's unclear, ask — don't guess.

  1. Confirm what you found via askuserinput_v0: "It looks like this is [service] from [company]. Is that right?" If I gave you a single charge or name, move to step 4. If I shared a statement or said I want to audit multiple subscriptions, move to step 3.
  1. Recurring-subscription audit: Scan the statement for charges that look recurring — same merchant appearing more than once at a regular interval, or descriptors like "SUBSCRIPTION," "RECURRING," "AUTOPAY," "MONTHLY," "ANNUAL," "RENEWS ON," or known subscription merchants. Present the list via askuserinput_v0 as a checklist:
  • Merchant name → likely service → amount → cadence (monthly/annual/unclear)
  • Flag anything you're unsure about ("could be one-time")

Let me check off which ones to cancel. Then work through them one at a time — for each selected service, run steps 4–9 below, show the summary card, and move to the next. Keep a running tally at the end: what's cancelled, what's pending, what I decided to keep.

  1. Research the fastest cancellation method and the billing terms. Find:
  • Fastest path: direct online cancellation (account settings, portal) → chat → phone → email/mail (last resort)
  • Current billing period end date (when does this cycle run out?)
  • Prorated refund policy — do they refund the unused portion, or do I just ride out the period?
  • Whether cancelling now kills access immediately or lets me keep using it until the period ends

Present the best cancellation path via askuserinput_v0 with a brief explanation of why it's the fastest route. If multiple paths exist, show the top 2 and recommend one.

  1. Before executing, confirm the timing via askuserinput_v0. Lay out the choice plainly:
  • Cancel now — access ends [immediately / on date], refund is [prorated amount / none]
  • Cancel at end of period — access continues until [date], no further charges after that, no refund

Set expectations on refunds honestly: if the service doesn't prorate, say so up front so I'm not surprised. Get my explicit pick before touching anything.

  1. If online cancellation: Open the service's website and navigate to the cancellation flow. Hand the browser to me for login. Walk through the retention offers and cancellation confirmation steps together — explain what each screen is asking and recommend responses. If they hit a "call us to cancel" wall, pivot to phone immediately.
  1. If phone cancellation: Before calling, confirm the details you'll need via askuserinput_v0:
  • Account holder name
  • Account number or email on file (if known)
  • Reason for cancellation (keep it simple — "no longer need the service" works)

Then place the call. Navigate any IVR menus. When you reach a person, lead with why you're calling, and in the same breath say you're Claude, an AI calling on my behalf — don't bury it. If they won't take cancellation requests from an AI, stop immediately, thank them, end the call, and tell me so I can call directly.

Otherwise, state the cancellation request directly — don't get drawn into retention offers unless I've told you I'm open to them. If they offer a deal, pause and relay it to me via the conversation before accepting or declining.

  1. After cancellation is confirmed, show a summary card:
  • Service cancelled
  • Confirmation number (if provided)
  • Effective date — when the cancellation takes hold
  • Access ends on [date] — when I actually lose the service
  • Any final charges or prorated refund amount
  • What to watch for (e.g. "Check your next statement to confirm no further charges")
  1. If cancellation requires mailing a letter or filling out a form, draft it and show it for approval.
  1. If any step fails or hits a dead end, immediately offer the next-best path without stalling.

Throughout: be warm but efficient. Cancellation flows are designed to be frustrating — your job is to cut through that. Stay focused on the goal and don't let retention tactics slow things down unless I explicitly want to hear an offer.

More skills from Razshy/Wiggle

  • Aalgorithmic-artCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
  • Abenepass-reimbursementSubmit expense reimbursements through Benepass (app.getbenepass.com). For users whose employer uses Benepass as their benefits platform. Handles login, benefit selection, form filling, receipt upload, and submission. Requires browser/computer-use capabilities.
  • Abrand-guidelinesApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
  • Abuilt-in-browserRead this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or \"your own browser\"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app and mcp__remote-devices__Claude_Browser__* when a cloud session is linked to the person's computer; before those tools are turned on there may be a single enable__mcp__remote-devices__Claude_Browser tool instead. It covers the pane's persistent sign-ins, tabs and preview_start, reading pages as text, site approvals, what the pane cannot open, and what to do when it cannot be reached. It is not for Claude in Chrome (mcp__claude-in-chrome__* tools), which has its own skill, and it does not decide which browser to use.
  • Acall-to-bookMake a phone call to book an appointment or reservation. Checks calendar first, gets explicit consent before dialing, discloses AI identity on the call, and adds the booking to calendar when done.
  • Acanvas-designCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
  • Achrome-browserRead this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcp__claude-in-chrome__* (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turned on there may be a single enable__mcp__claude-in-chrome tool instead. It covers loading the tools in one ToolSearch call, checking the person's open tabs and working in a new tab, site permissions, GIF recordings, console logs, dialogs to avoid, and when to stop and ask. It is not for the built-in browser (mcp__Claude_Browser__* or mcp__remote-devices__Claude_Browser__* tools), which has its own skill, and it does not decide which browser to use.
  • Acomputer-useRead this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for \"computer use\". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before a conversation is linked there may be no such tools, only an enable__mcp__remote-devices__Claude_Browser tool, which links it. It covers getting linked, picking the right tool, the access flow, and what to do when computer use is off or out of reach. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.
  • Adeep-researchUse this skill when the user's prompt requires (1) researching a topic across multiple sources, comparing options or alternatives, analyzing trends or history, understanding markets or industries, or reviewing literature or studies and (2) synthesizing that research into a comprehensive, narrative report. If you're planning to search the web or internal knowledge bases, consider using this skill. This skill coordinates research subagents, so use it only when you have a tool for spawning subagents (the Agent or Task tool); otherwise, research the question directly.
  • Adoc-coauthoringGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
  • AdocxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers a dedicated document or page skill or connector, use that instead. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.
  • Aevent-planningHelp plan an event — from a birthday dinner to a wedding. Scales to the size of the occasion. Handles venue research, guest lists, timelines, vendors, and budgets.

All agent skills → · MCP servers