agentleFS
nathan8823nathan8823/fairbill/.claude/skills/intake/SKILL.md

intake

Skill1 starsChanged 4 months agoMITView on GitHub

Start a new medical-bill case. Use when the user mentions any new bill, collection notice, or billing problem — builds the case file that every other skill works from.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan, triage and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 4 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 3 projects that use this

  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    Also in 3 projects that use this

  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Get the documents: Ask the user to drop into the case folder (or share) whatever they have: the bill, any EOB, collection letters, the Good …

    line 17
  2. Very specific:

    No itemized bill in hand? → that request goes out today (templates/letters/itemized-request.md).

    line 42

“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “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

Intake — open the case

Goal: a complete case file, a screened set of opportunities, and a clear next step, in one session.

Steps

  1. Create the case folder: cases/<yyyy-mm-provider-context>/ (e.g. cases/2026-07-st-marys-er/). Copy templates/case-file.md in as case.md. Create an empty call-log.md and a letters/ subfolder.
  2. Get the documents. Ask the user to drop into the case folder (or share) whatever they have: the bill, any EOB, collection letters, the Good Faith Estimate if one was given. Read them with the Read tool (PDFs and photos both work). Extract into case.md: provider name and billing address/phone, account number, dates of service, total billed, every line item visible, insurance status, and all deadlines mentioned.
  3. Interview — only what the documents don't answer:
    • What happened medically, in the user's words? (Flags upcoding: a "quick stitches" visit billed as Level 5 is a finding.)
    • Insured at the time? Did insurance process it — where's the EOB?
    • Emergency? Was any provider out-of-network? (No Surprises Act flags.)
    • Any estimate given beforehand? (GFE dispute flag.)
    • Has anything been paid, or a payment plan started?
    • Any collection contact yet? First contact date? (30-day validation clock.)
    • With permission, household size and approximate income — explain it's for charity-care screening and stays in the local case file only.
    • What outcome do they want, and what could they actually pay?
  4. Immediate triage — check in this order:
    • Court summons in the papers? → stop, flag rule 5 of AGENTS.md, point to legal aid today, everything else is secondary.
    • Collector first contact <30 days ago? → debt validation letter now (.claude/skills/collections/), it's a hard deadline.
    • No itemized bill in hand? → that request goes out today (templates/letters/itemized-request.md).
    • Nonprofit hospital + income plausibly under ~4x federal poverty line? → run .claude/skills/financial-assistance/ before negotiating.
  5. Write it all into case.md, set the status line, and tell the user: what you found, the single next action, and who does it (you or them).

Rules

  • Personal data goes only in cases/ (gitignored). Remind the user of this.
  • Empathy first, plan second: many users arrive scared by a five-figure number. State early and plainly that first bills are opening numbers, errors are common, and there is a process.

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.