Skip to main content
ClaudeWave
Skill283 repo starsupdated 25d ago

cowork-medical-bill-auditor

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.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/OneWave-AI/claude-skills /tmp/cowork-medical-bill-auditor && cp -r /tmp/cowork-medical-bill-auditor/cowork-medical-bill-auditor ~/.claude/skills/cowork-medical-bill-auditor
Then start a new Claude Code session; the skill loads automatically.

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
accessibility-auditorSkill

Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.

agent-armySkill

Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.

agent-swarm-deployerSkill

Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.

agent-team-builderSkill

Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.

agent-to-agentSkill

Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.

ai-readiness-assessmentSkill

Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.

animateSkill

Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.

api-documentation-writerSkill

Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.