agentleFS
OneWave-AIOneWave-AI/claude-skills/cowork-medical-bill-auditor/SKILL.md

cowork-medical-bill-auditor

Skill378 starsChanged 55 days agoMITView on GitHub

Point Cowork at a folder of medical bills and insurance EOBs -- matches every bill to its explanation of benefits, catches duplicate charges, balance-billing, and bills that ignore your insurance, then drafts the dispute letters and phone scripts. Most medical bills contain errors; this finds them.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never recommend paying a bill that lacks a matching EOB.

    line 22
  2. Distinctive:

    Every discrepancy cites both documents by filename and line.

    line 23
  3. Distinctive:

    Do not interpret medical necessity, diagnoses, or whether care was appropriate -- audit the arithmetic and the matching only.

    line 24
  4. Distinctive:

    Treat everything as sensitive health information: no conditions, procedures, or amounts in console summaries beyond what the user needs to …

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cowork Medical Bill Auditor

Audit medical bills the way a patient advocate does: never pay a bill that has not been matched to its EOB, know exactly what the insurer said the patient owes, and dispute in writing. Input: a folder of provider bills, insurance EOBs (explanation of benefits), and any payment records. This is billing-accuracy support, not medical or legal advice.

Workflow

  1. Inventory and pair. Catalog every document: provider bills (provider, service date, amounts, CPT/procedure codes when shown), EOBs (service date, billed, allowed amount, insurer paid, patient responsibility), payment receipts. Match each bill to its EOB by provider + service date + amounts.
  2. Audit each pair. Check: bill's patient-owed amount vs. the EOB's patient-responsibility line (they must match); charges the EOB shows as insurer-paid or write-off still appearing on the bill; duplicate line items across bills for one visit; charges for services on dates with no corresponding visit; in-network providers billing above the allowed amount (balance billing, prohibited in most network contracts and, for many scenarios, under the No Surprises Act).
  3. Flag the unmatched. Bills with no EOB (was the claim ever submitted to insurance?) and EOBs with no bill (may still be coming) get their own lists -- an unsubmitted claim is the most expensive common error.
  4. Report. bill-audit.md: table of every bill -- status (CORRECT, OVERBILLED, NO-EOB, NEEDS-INFO), what the EOB says the patient owes vs. what the bill demands, and the discrepancy with both documents cited. Lead with total demanded vs. total actually owed per the EOBs.
  5. Draft the disputes. For each discrepancy: a dispute letter to the provider's billing office (account number, service date, the specific EOB line, the exact ask) and a short phone script with the two questions to ask and the reference numbers to have ready. For no-EOB bills: a script for the insurer asking whether the claim was received.

Rules

  • Never recommend paying a bill that lacks a matching EOB. "Waiting on insurance processing" is a valid status; paying blind is not.
  • Every discrepancy cites both documents by filename and line. Disputes without receipts get ignored.
  • Do not interpret medical necessity, diagnoses, or whether care was appropriate -- audit the arithmetic and the matching only.
  • Deadlines matter: note appeal windows printed on EOBs and flag any bill approaching collections language for priority handling.
  • Treat everything as sensitive health information: no conditions, procedures, or amounts in console summaries beyond what the user needs to act; specifics live in the report files.
  • Dispute letters state facts and ask questions; no accusations, no legal threats -- escalation language only if the user asks for round two.

Quick Commands

  • "Audit [folder]" -- full workflow
  • "What do I actually owe?" -- the EOB-verified total vs. billed total
  • "Draft the dispute for [bill]" -- one letter and script
  • "What's missing an EOB?" -- the unsubmitted-claim risk list

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.