just-fucking-cancel
Find and cancel unwanted subscriptions by analyzing bank transactions. Detects recurring charges, calculates annual waste, and helps you cancel with direct URLs and browser automation. Use when: 'cancel subscriptions', 'audit subscriptions', 'find recurring charges', 'what am I paying for', 'save money', 'subscription cleanup', 'stop wasting money'. Supports CSV import (Apple Card, Chase, Amex, Citi, Bank of America, Capital One, Mint, Copilot) OR Plaid API for automatic transaction pull. Outputs interactive HTML audit with one-click cancel workflow. Pairs with Plaid integration for real-time transaction access without CSV exports.
What this skill does
# just-fucking-cancel Analyze transactions, categorize subscriptions, generate HTML audit, help cancel. ## Triggers - "cancel subscriptions", "audit subscriptions" - "find recurring charges", "what am I paying for" - "subscription audit", "clean up subscriptions" ## Workflow ### 1. Get Transactions **Option A: Plaid API (recommended — no CSV needed)** If the user has Plaid connected (check for Plaid integration/API access): 1. Pull last 6-12 months of transactions via Plaid Transactions API 2. All accounts are automatically included — no manual export needed 3. Skip straight to Step 2 **Option B: CSV Upload** Ask user for bank/card CSV export. Common sources: - Apple Card: Wallet → Card Balance → Export - Chase: Accounts → Download activity → CSV - Amex: Statements & Activity → Download → CSV - Citi: Account Details → Download Transactions - Bank of America: Activity → Download → CSV - Capital One: Transactions → Download - Mint / Copilot: Transactions → Export ### 2. Analyze Recurring Charges Read CSV, identify recurring patterns: - Same merchant, similar amounts, monthly/annual frequency - Flag subscription-like charges (streaming, SaaS, memberships) - Note charge frequency and total annual cost ### 3. Categorize with User For each subscription, ask user to categorize: - **Cancel** - Stop immediately - **Investigate** - Needs decision (unsure, trapped in contract) - **Keep** - Intentional, continue paying Ask in batches of 5-10 to avoid overwhelming. ### 4. Generate HTML Audit Copy [template.html](assets/template.html) and populate: - Update header summary: - Scope line: "found N subscriptions · N transactions" - Breakdown: "Cancelled N · Keeping N" - Savings: yearly amount big, monthly in parentheses - Timestamp: current date - Add rows to appropriate sections (cancelled/investigate/keep) - Include notes from user responses Row templates in the HTML comments show the structure. ### 5. Cancel Subscriptions When user checks items and copies from floating button, they'll paste: `Cancel these: Service1 ($XX), Service2 ($XX)...` For each service: 1. Check [common-services.md](references/common-services.md) for cancel URL 2. Use browser automation to navigate and cancel 3. Update HTML row to cancelled status with date ## HTML Structure Three sections, auto-hide when empty: - **Cancelled** (green badge, strikethrough) - Done items, the win - **Needs Decision** (orange badge) - Has checkboxes for cancel selection - **Keeping** (grey badge) - No checkboxes, just reference Features: - Floating copy button appears when items checked - Privacy toggle blurs service names - Collapsible sections via header click - Dark mode support ## Cancellation Tips For difficult services, see [common-services.md](references/common-services.md): - Direct cancel URLs for 50+ services - Dark pattern warnings (gym contracts, phone-only) - Retention script responses - Credit card dispute backup ## Privacy All data stays local. Transaction CSVs are analyzed in-session only.
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.