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
- skillberry-ai/cap-evolvetheir own version, first seen Nov 8, 2026
- cdfarkas/cdfarkas-skillstheir own version, first seen Nov 8, 2026
- Mathews-Tom/armorytheir own version, first seen Nov 1, 2026
- ghvinashvili/specagenttheir own version, first seen Nov 1, 2026
- bmtrnavsky/disciplined-vibe-codingtheir own version, first seen Nov 1, 2026
- AdityaZxxx/skillstheir own version, first seen Oct 20, 2026
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.
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 4 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 4 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 4 projects that use this
Microsoft AzureSkillbuild
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
VercelSkilldeploy
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 AzureSkillverify
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
Other versions34 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 34
- openai/plugins★ 7.8ksame name
- Mathews-Tom/armory★ 340same name
- skillberry-ai/cap-evolve★ 70same name
- bmtrnavsky/disciplined-vibe-coding★ 19same name
- Consortium-team/project-creator★ 17same name
- awslabs/service-onboarding-accelerator-on-aws★ 7same name
- ghvinashvili/specagent★ 7same name
- ndisisnd/msg★ 6same name
- tonydzi/second-brain-starter-kit★ 6same name
- stevehansen/eidet★ 4same name
24 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- benchmark-priceSkill
- collectionsSkill
- draft-emailSkill
- financial-assistanceSkill
- insurance-appealSkill
- phone-prepSkill
- review-billSkill
- send-letterSkill
- strategySkill
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
- Distinctive: line 17
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 …
- Very specific: line 42
No itemized bill in hand? → that request goes out today (templates/letters/itemized-request.md).
“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.
Files
Intake — open the case
Goal: a complete case file, a screened set of opportunities, and a clear next step, in one session.
Steps
- Create the case folder:
cases/<yyyy-mm-provider-context>/(e.g.cases/2026-07-st-marys-er/). Copytemplates/case-file.mdin ascase.md. Create an emptycall-log.mdand aletters/subfolder. - 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. - 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?
- 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.
- 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.
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
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.

