Draft email
Turn your AI agent into a medical-bill negotiation advocate — an open-source playbook of skills, letters, and verified patient rights. Pay what's fair, nothing more.
npx -y skills add nathan8823/fairbill --skill draft-emailAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Draft and (with approval) send negotiation emails through the user's email account. Use for itemized-bill requests, dispute follow-ups, call recaps, and settlement correspondence.
SKILL.md
2.2 KB, as published. Nobody here has run it
Draft email
Capability check (once per session)
Use whatever email tooling exists — Gmail/Outlook MCP connector, himalaya,
Apple Mail via computer use, anything the user has wired up. Preferred
mode: create a draft in their account and have them hit send. If no email
tool exists: write the draft to cases/<case>/letters/ as
email-yyyy-mm-dd-<topic>.md with To/Subject/Body clearly marked for
copy-paste, and offer to help set up the Gmail MCP connector for next time.
Non-negotiables
- Never send without the user seeing the exact final text, recipient, and subject, and approving. One approval = one email. "Send it" in a prior session is not approval for this one.
- Find the right address first: billing-department email from the bill or provider site. Avoid generic contact forms when a real mailbox exists — forms don't leave the user a copy.
- Subject line formula:
Account #<number> — WRITTEN DISPUTE: <topic>(or REQUEST). The account number makes it land in the right queue; the word "dispute" starts the paper trail.
Structure that works
- One line of who/what: patient name, account number, date of service.
- The ask, stated in the first three lines. Not the story — the ask.
- Numbered facts, each anchored to a document ("your itemized statement dated…", "your published standard-charges file lists…", "per our call with Maria on 7/2, ref #48119…").
- The specific action requested + a response deadline (10–15 business days), and "please respond in writing."
- "This account is in dispute" when applicable — and a line noting the dispute should be recorded on the account.
Tone per AGENTS.md: firm, factual, boring. No emotion in the email; keep
that for the user. Templates in templates/emails/; personalize fully — a
placeholder left in ruins credibility.
After sending
Log to case.md (date, recipient, subject, deadline set). Calendar the
follow-up: no reply by deadline → one follow-up citing the first, then up
the escalation ladder.