brief · insilico-org — Claude Code skill: visit prep and installation
A Claude Code skill that assembles a pre-visit brief for one patient. It gathers changes, data gaps, plan status, and questions ahead of an appointment.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill brief -a claude-codeWhat brief does
The skill gathers patient data with plsi status, plsi export, plsi due, and plsi events list, then writes a brief to brief.md. It puts the newest information first: changes since the last visit, missing values and overdue tests, plan status, and questions to cover. Each value includes a date and unit.
The brief uses patient labels, not names. It reports information without diagnosing, ordering tests, or recommending treatment; item labels and plan status stay as recorded. If the request does not include the last visit date, the skill uses a 6-month period.
The result contains brief.md, a 3-line summary, and a Visualizer task with the clinician brief scope. Any question about clinical evidence is also passed to Clinical Evidence.
What it helps with
- summarize patient changes since the last visit
- find missing values and overdue tests
- organize recorded plans and their predictions
- prepare questions for an upcoming appointment
Example prompts for the agent
- Prepare a pre-visit brief for patient
patient-07for Thursday. - Prepare my visits for tomorrow, one patient at a time.
- Create a pre-visit brief for the patient selected from
panel/overview.
How to install brief
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill brief -a claude-code2Manually: put the files in place
~/.claude/skills/brief/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/brief/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill brief -a codex2Manually: put the files in place
.agents/skills/brief/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill brief -a cursor2Manually: put the files in place
.cursor/skills/brief/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/visitprep/brief2Manually: put the files in place
.github/skills/brief/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill brief -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/visitprep/briefManually: put the files in place
.devin/skills/brief/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 brief
How do I install brief in Claude Code?
Run npx skills add Insilico-org/plsi --skill brief -a claude-code. The skill file is placed at ~/.claude/skills/brief/SKILL.md.
What does brief do?
It assembles a clinician-facing summary for one patient, covering changes, data gaps, plan status, and visit questions. It does not diagnose or recommend treatment.
What goes into a brief report?
The report covers new results and changes, missing values and overdue tests, recorded plans with their predictions, and questions tied to those details. Every value has a date and unit.
Source text
SKILL.md · MIT
---
name: brief
description: Use as PLSI Visit Prep when the physician has a visit coming with one patient on their panel - the pre-visit brief (what changed, gaps, plan status, questions to cover), drawn by PLSI Visualizer as a clinician brief.
---
# PLSI pre-visit brief
**Status: draft**. This is the clinician-facing twin of
`orchestrator/physicians` step 2: written for the physician about a patient, not by a patient for a physician.
## When to use
- "I see patient-07 on Thursday", "prepare my visits for tomorrow" (one request per patient, each from that
patient's ward bot), or a patient picked from `panel/overview`.
## Steps
1. **Collect** from the toolbelt, never from memory:
```bash
plsi status --instance <label>
plsi export --instance <label>
plsi due --instance <label>
plsi events list --instance <label> --kind intervention
```
The last visit date comes from the request (the physician's or the roster's `last_update`); none: use 6 months.
2. **Write** `<PLSI_HOME>/work/<thread>/brief.md`, newest first, every value with unit and date:
- **Changed since the last visit:** new results with the change from the previous one; new conditions,
medications, side effects;
- **Gaps:** coordinates of the patient's maps with no current value, tests overdue;
- **Plans:** status exactly as recorded, each prediction (expected, interval, review date) and its score so far;
- **To cover:** 3-7 questions tied to the above (unexplained changes, overdue tests, plan safety cautions from
the recorded screening, as written).
3. **Return one `result`**: `brief.md` in `files`, a 3-line summary, the work for Visualizer
(`visualizer/dashboard`, scope **clinician brief**) and any evidence question for Clinical Evidence
(`clinev/review`), each naming its skill path.
## Rules
- The brief reports; it never diagnoses, orders or recommends. Item labels and plan status exactly as recorded.
- One patient per brief; labels, never names.
© Insilico-org · MIT · Insilico-org/plsi
Similar skills
All skills for Science and research →brief by other authors comes first.