Drag the world ⟲
Open-source skills for skilled nursing

The whole SNF playbook, as skills.

Free, open-source skills that teach coding agents like Claude Code, Codex, or Cursor how a great SNF back office works — admissions, MDS, managed care, compliance. Paste in a packet, a contract, or a census export and get the answer a seasoned coordinator would give.

Screen hospital packets into accept/decline memos
Price a stay across all six PDPM components
Find NTA points buried in discharge summaries
Flag contract clauses that quietly cost money
Keep MDS/PPS and PBJ calendars on schedule
Draft prior-auth packets and appeal letters
Read a month of census like an analyst
Check benefit days before you admit
01

Skills for every desk in the building

Each pack is a playbook for one job in the building. Install a pack and Claude uses it automatically whenever your question touches that job — no setup beyond the install, free for any facility, on Magicare or not.

referral-triage

Screen a hospital packet: clinical fit, financial fit, red flags, decision memo.

"Here's a packet from Example Hospital — should we take it?"
pdpm-revenue

All six PDPM components, CMG classification, variable per-diem, stay revenue.

"What would Medicare pay for this admission?"
nta-capture

The full CMS NTA point list, with quoted evidence and a missed-points audit.

"Find every NTA point in this discharge summary."
insurance-contracts

Extract rates, levels, carve-outs, auth rules; level patients; prep negotiations.

"What should we renegotiate in this contract?"
compliance

MDS/PPS calendars, PBJ deadlines, survey readiness, Plans of Correction.

"Build the assessment calendar for these admissions."
census-operations

Occupancy, payer mix, skilled mix, trends, and backfill math from raw exports.

"Analyze this month's census — what should worry me?"
prior-auth

Auth packets, continued-stay reviews, peer-to-peer prep, appeal letters.

"Draft the continued-stay review for this resident."
eligibility

Benefit-day math, qualifying-stay traps, MA nuances, Medicaid-pending risk.

"Does this patient have benefit days left?"
magicare-ai / snf-skills

Every skill lives in this repo as plain, readable markdown — open it, audit it, fork it, improve it. Star the repo to follow new packs.

plugins/ ├─ referral-triage/ ├─ compliance/ ├─ pdpm-revenue/ ├─ census-operations/ ├─ nta-capture/ ├─ prior-auth/ ├─ insurance-contracts/ └─ eligibility/
MIT license Agent Skills format PRs welcome Browse the repo ↗
Install — Claude Code
# inside Claude Code /plugin marketplace add magicare-ai/snf-skills /plugin install pdpm-revenue@snf-skills # …or any pack above
Install — Cursor, Codex & other agents
# open Agent Skills format — works anywhere npx skills add magicare-ai/snf-skills

Each pack is independent — install one or all of them. Then just work: paste in a document and the right skill loads itself.


02

On Magicare? Give the skills live data

The skills work on whatever you paste in — no account needed. If your facility uses Magicare, you can also connect Claude directly to your live referrals, census, and PointClickCare, with the same permissions and audit trail as the app. It runs on the open Model Context Protocol ↗ and takes about two minutes to set up.

STEP 1

Get your token

Sign in to Magicare, then open app.exponentialcare.ai/cli-auth and click Generate CLI token. It starts with magi_. Treat it like a password — you can revoke it on the same page anytime.

STEP 2

Add the server

Paste one command into your terminal (Claude Code). Desktop and Cursor configs are below.

STEP 3

Just talk

Ask "who am I and which facilities can I see?" — Claude calls whoami and you're live. Everything is scoped to you, server-side.

# Claude Code — one line claude mcp add --transport http magicare \ https://app.exponentialcare.ai/api/mcp/org \ --header "Authorization: Bearer magi_YOUR_TOKEN"
Claude Desktop, Cursor, Codex, or a project .mcp.json
# .mcp.json — keep the token in an env var, not in the file { "mcpServers": { "magicare": { "type": "http", "url": "https://app.exponentialcare.ai/api/mcp/org", "headers": { "Authorization": "Bearer ${MAGICARE_CLI_TOKEN}" } } } }

Codex or another MCP-capable agent? Point it at the same URL with the same Authorization header — streamable HTTP transport, nothing else to configure. See your agent's MCP docs for where its server list lives.


03

Fourteen tools, properly scoped

Once connected, Claude can use fourteen tools. Each one respects the same permissions you already have in the Magicare app — which facilities you can see, what your role allows — enforced on our servers. Nothing you type can widen them.

Read — every member

whoamiYour identity, role, permissions, facilities. Start here.
list_facilities / get_facilityProfiles and EHR-connection status.
list_referrals / get_referralSearch and read referrals — status, insurance, the whole record.
referral_status_countsYour pipeline, grouped by workflow status.
pcc_bedboard / pcc_patientsCensus snapshots and patient lists from PointClickCare — through us.

Act — permission-gated

update_referral_statusChange StatusAccept, reject, bed-hold, admit. Attributed to you, written to the status log.
pcc_create_pending_patientCreate PCC PatientPush a referral's extracted patient into PointClickCare as a pending patient.

Manage — org admins

update_facilityOrg adminContact and profile fields — email, phone, notes, address.
list_membersOrg adminYour team, their roles, permissions, and facility assignments.
update_member_capabilitiesOrg adminGrant or revoke permissions per member.
assign_member_facilitiesOrg adminSet exactly which facilities a member can access.

04

Built like the app. Scoped like the app.

This is not a side door. It's the same front door, sized for an agent.

Your token, your reach

Tokens are per-user, hashed at rest, and revocable in one click at /cli-auth. A revoked token stops working immediately.

Scope is server-side

Org and facility scope are resolved from your token on our servers. Tool inputs can never widen what you're allowed to see.

Same permissions as the app

Org-admin role and per-member permissions gate mutations exactly as the web app does. Every change is attributed to you and logged.

PCC stays with us

PointClickCare access runs on our servers with our credentials — mTLS, OAuth, quota-governed. Nothing credential-shaped ever reaches your machine.

Working with PHI: referral and census tools return protected health information — the same data you see in the app, served only to authenticated members of your organization. Use them under your organization's AI governance and Claude commercial terms, with minimum-necessary data. The open-source skills are educational reference material, not clinical, billing, or legal advice.


05

Things people actually ask

The first two need nothing but a pasted document. The last two use a live Magicare connection.

"Here's the discharge summary — what NTA points are we missing?"
The nta-capture skill loads, walks the full CMS point list against the record, and quotes the evidence line for every point it finds — plus the ones documentation almost supports.
"What would Medicare actually pay for this admission?"
The pdpm-revenue skill classifies all six PDPM components, applies the variable per-diem schedule, and lays out expected revenue for the stay.
"Which of my facilities have open referrals right now?"
With MCP connected, Claude calls referral_status_counts and breaks the queue down per building with what's aging.
"Accept the referral for John D. at Riverside and push him into PCC."
With MCP connected, Claude confirms the match, calls update_referral_status, then pcc_create_pending_patient — each gated on your permissions.