Bill Fighter
Challenge overcharges and denied claims with evidence-backed letters
Turns your AI into a bill dispute assistant — builds your evidence pack, finds the leverage (clauses, competitor prices, your history), drafts firm factual dispute letters, and runs the follow-up clock until it's resolved.
Install it in 3 steps
No sign-up. No CLI tools. Pick your AI, copy one line, paste it over.
Prefer doing it yourself? Download the ZIP, unzip it into the directory shown above, restart your AI session — same result.
Real-world proof
Real people did this exact job with AI agents.
What’s inside
One SKILL.md (the playbook) + one starter template. A preview:
Bill Fighter
When to use
- Your internet/cable bill crept up $30 and the "promotional rate expired" with no warning
- An insurance claim was denied and the denial letter reads like it was designed to make you give up
- You found the same service cheaper elsewhere and want your provider to match it or lose you
- A medical bill looks wrong but decoding it would take an afternoon you don't have
- A subscription you cancelled keeps charging and support keeps "escalating" it into the void
Workflow
Gather everything first: the bill or denial letter, the last 3–6 months of statements showing what you used to pay, the policy or contract clauses that apply, and any competitor prices you've seen. Photograph paper bills; the skill reads them. One dispute = one case file. No evidence pack, no letter — the letter is only as strong as what's behind it.
- Build the case file (input: your bills and letters → output: organized evidence pack)
Figure out what actually gives you power here, in this order: ① contract/policy language in your favor (quote the clause number) ② competitor prices for the same service ③ your tenure and payment history ("3 years, never late") ④ regulatory hooks (FCC complaints for telecom, state insurance commissioners, CFPB for financial products). Write the leverage memo before the letter — it decides the letter's entire strategy.
- Find the leverage (input: evidence pack → output: leverage memo)
Structure: what happened (dates, amounts, one paragraph), what's wrong (cite the clause or the competitor price), what you want (specific number: "restore the $49 rate" not "lower my bill"), and the consequence ("I'll file with the FCC on Friday" — only if you mean it). Firm, factual, boring. Anger is noise; numbers are signal. Keep it under 300 words — the person reading it processes 200 of these a day.
- Draft the letter (input: leverage memo → output: dispute letter draft)
You read every letter before it sends — non-negotiable. Check: are the numbers right, is the clause quoted accurately, is the ask specific, is the tone firm-not-abusive. Then send it through the channel that creates a paper trail: email, provider chat with transcript saved, or certified mail for the serious ones. Log the date sent.
- Review and send (input: draft → output: sent dispute)
Disputes die in silence — that's the business model. Set the follow-up schedule when you send: nudge at 7 days, escalate at 14 (supervisor / executive relations / regulator complaint drafted but unsent), final decision at 30. Every reply gets logged against the case file. When they counter, you decide: accept, push once more with new leverage, or walk away and switch prov
- Run the follow-up clock (input: sent dispute → output: resolution)
