mcpbeat Sign in

Cowork Medical Bill Auditor Skill for Claude

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.

875 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
235
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/OneWave-AI/claude-skills --skill cowork-medical-bill-auditor

The instruction itself

4 sections, as written by the author

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

  • 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.
  • 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).
  • 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.
  • 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.
  • 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

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide 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.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take onewave-ai/cowork-medical-bill-auditor from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.