Analyze bank transaction CSVs to find recurring charges, categorize subscriptions, and cancel what you don't need. Use when user says "cancel subscriptions", "audit subscriptions", "find recurring charges", or "what am I paying for". Supports Apple Card, Chase, Mint, and generic CSV formats. Outputs interactive HTML audit with copy-to-cancel workflow.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: just-fucking-cancel description: Analyze bank transaction CSVs to find recurring charges, categorize subscriptions, and cancel what you don't need. Use when user says "cancel subscriptions", "audit subscriptions", "find recurring charges", or "what am I paying for". Supports Apple Card, Chase, Mint, and generic CSV formats. Outputs interactive HTML audit with copy-to-cancel workflow.
just-fucking-cancel
Analyze transactions, categorize subscriptions, generate HTML audit, help cancel.
Workflow
1. Get Transaction CSV
Ask user for bank/card CSV export. Common sources:
- Apple Card: Wallet → Card Balance → Export
- Chase: Accounts → Download activity → CSV
- Mint: 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 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:
- Check common-services.md for cancel URL
- Use browser automation to navigate and cancel
- 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:
- 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.
More by rohunvora
View allGenerate minimal HTML pages to review Claude Code output in a browser. Use when terminal output is hard to read, when reviewing lists/tables/drafts, or when user says "show me", "make this reviewable", "quick view", or "open as webpage". Produces unstyled semantic HTML only. For granular feedback with inline comments, see the comment-mode skill.
Designs optimal filtering UX for data tables. Use when building a table that needs filters - analyzes the data columns and determines the best filter type for each. Outputs a unified filter field with inline header filters.
Primary Telegram interface. Full-featured CLI for message export, DM management, group sync, contact scoring, and thread state. Use when user mentions "telegram", "tg", "@username", or telegram-specific terms. Triggers: "telegram messages", "export telegram", "telegram DMs", "telegram groups", "sync telegram", "@username messages", "telegram contacts". This is STANDALONE - do not defer to unified-messages for telegram operations.
Granular feedback on drafts without rewriting. Generates highlighted HTML with click-to-reveal inline comments. Use when user says "comment on this", "leave comments on", "give feedback on", or asks for feedback on a draft. Supports multiple lenses—editor feedback, POV simulation ("as brian would react"), or focused angles ("word choice only", "weak arguments"). A granular alternative to rewrites that lets users review feedback incrementally without losing their voice.