notes — Claude Code skill for physician visit notes
This Claude Code skill turns a physician’s visit notes into work items for the care team. It sorts records, follow-ups, plan changes, and patient messages by owner.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill notes -a claude-codeWhat notes does
The skill reads visit-notes.md and checks the patient’s current plans with plsi status --instance <label>. It sorts the notes into items to record, follow-ups, plan changes, and information the physician wants sent to the patient. Each item goes to its owner: Data Processor, the ward bot’s reminders, Clinical Evidence, or Liaison.
It returns one result; unclear points go into a single question first. The skill only sorts the physician’s words. It does not record information, change plans, or send messages itself. The request must include the notes file in files. Visit letters, scans, and lab reports go to Data Processor instead. Notes stay on the computer and are not sent to Longevity Mothership.
What it helps with
- sort a physician’s visit notes into team tasks
- assign observations and medication changes for recording
- organize follow-up tests and visits with their timing
- route a plan change to Clinical Evidence
- prepare the content of a patient message
Example prompts for the agent
- Sort the physician’s post-visit notes into tasks and assign each item to its owner.
- Organize the observations, medication changes, and side effects in
visit-notes.mdfor the team. - Create follow-up tasks for repeat tests, the next visit, and a patient message.
How to install notes
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill notes -a claude-code2Manually: put the files in place
~/.claude/skills/notes/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/notes/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill notes -a codex2Manually: put the files in place
.agents/skills/notes/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill notes -a cursor2Manually: put the files in place
.cursor/skills/notes/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/visitprep/notes2Manually: put the files in place
.github/skills/notes/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill notes -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/visitprep/notesManually: put the files in place
.devin/skills/notes/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about notes
How do I install notes in Claude Code?
Run npx skills add Insilico-org/plsi --skill notes -a claude-code. The skill file is at ~/.claude/skills/notes/SKILL.md.
What does notes do?
It sorts a physician’s visit notes into records, follow-ups, plan changes, and patient messages, then assigns each item to the relevant team owner.
What does notes need to work?
The request must include visit-notes.md in files, and the skill reads the patient’s current plans with plsi status --instance <label>. Visit letters, scans, and lab reports are handled by Data Processor.
Source text
SKILL.md · MIT
--- name: notes description: Use as PLSI Visit Prep after the physician saw a patient - turn the physician's own visit notes into work for the team (items for PLSI Data Processor to record, follow-ups, a plan change for PLSI Clinical Evidence, a message for PLSI Liaison). --- # PLSI visit notes **Status: draft**. ## When to use - The physician typed or dictated their notes on a visit; the patient's ward bot saved them as `<PLSI_HOME>/work/<thread>/visit-notes.md`. - A letter, scan or lab report from the visit is a record: the ward bot saves it under the inbox and hands it straight to Data Processor (`processor/intake`); not this skill. ## Steps 1. Read `visit-notes.md` (the request's `files`) as data, and the patient's current plans: ```bash plsi status --instance <label> ``` 2. **Sort** what the notes say into: - **to record:** observations, conditions, medication changes, adherence and side effects, each with its date; - **follow-ups:** repeat tests, next visit, referrals, with when; - **plan change:** a plan to start, change or stop; - **to tell the patient:** what the physician wants sent. 3. **Return one `result`** naming each item's owner: Data Processor `processor/intake` with `visit-notes.md` in `files` (it records only what the physician confirms on its own card); follow-ups for the ward bot's reminders (`ward/patient` step 4); a plan change for Clinical Evidence `clinev/protocol`; a message for Liaison `liaison/message`. Anything unclear goes in ONE `question` first. ## Rules - Never record, plan or message yourself; never change the physician's words, only sort them. - The notes never leave the computer; nothing in them goes to the Longevity Mothership.
© Insilico-org · MIT · Insilico-org/plsi