overview — Claude Code skill: patient panel and installation
This Claude Code skill builds a PLSI patient-panel overview and ranks items for a physician’s attention. It runs when the physician asks about patient status, due follow-ups, or who needs attention.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill overview -a claude-codeWhat overview does
The skill gathers data for active patients in roster.json and assigns each to one category: red flag, due, out of range, off plan, quiet, or on track. It calls plsi due, plsi status, and plsi state show; when clinic folders are present, it also checks waiting files and sync records.
It writes panel.json in the current thread folder and prepares up to 10 priority rows for the summary and PLSI Visualizer. The skill reports status only: it does not diagnose, recommend treatment, or change a plan. It uses patient labels rather than names and keeps each patient’s data out of other patients’ rows. The skill is marked draft.
What it helps with
- compile a status overview for active patients
- surface critical results and overdue follow-ups
- flag measurements outside their reference range
- find patients with no recent data
- prepare priority rows for PLSI Visualizer
Example prompts for the agent
- Build a PLSI panel overview and show who needs attention.
- List patients with overdue visits or follow-ups.
- Prepare the active-patient panel for PLSI Visualizer.
How to install overview
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill overview -a claude-code2Manually: put the files in place
~/.claude/skills/overview/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/overview/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill overview -a codex2Manually: put the files in place
.agents/skills/overview/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill overview -a cursor2Manually: put the files in place
.cursor/skills/overview/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/panel/overview2Manually: put the files in place
.github/skills/overview/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill overview -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/panel/overviewManually: put the files in place
.devin/skills/overview/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 overview
How do I install overview in Claude Code?
Run npx skills add Insilico-org/plsi --skill overview -a claude-code. The skill file is at ~/.claude/skills/overview/SKILL.md.
What does overview do?
It gathers status for active PLSI patients, sorts them by priority, and creates panel.json plus rows for Visualizer. It does not diagnose or recommend treatment.
Which patient records does overview collect?
It reads active entries from work/panel/roster.json. When clinic folders are present, it also checks waiting files and entries in work/panel/synced.jsonl.
Source text
SKILL.md · MIT
---
name: overview
description: Use as PLSI Panel when the physician asks how their patients are doing - across the panel, who is due, out of range, off plan or without new data, ranked for the physician's attention and drawn by PLSI Visualizer.
---
# PLSI panel overview
**Status: draft**.
## When to use
- "How are my patients doing?", "who needs attention?", "who is due this month?".
- The Clinic Orchestrator's weekly routine "PLSI panel overview".
## Steps
1. **Collect** for every `active` row of `<PLSI_HOME>/work/panel/roster.json` (`panel/roster`):
```bash
plsi due --all
plsi status --instance <label>
plsi state show --instance <label> --map <map_id>
```
`due --all` once; per active row `status` once, then `state show` for each map in its `states`; off plan comes
from `status`'s `plans`. With clinic folders (`panel/clinic`): `plsi clinic check` (`waiting` files per
patient, `problems`) and the lines of `<PLSI_HOME>/work/panel/synced.jsonl` since the last overview (`new`,
`failed`, `held`, `unrouted`, `published`, by label and date), for the `next` column. A state not `current`:
list it as "needs re-projection" (Data Processor, through that patient's ward bot).
2. **Sort** each patient into at most one row, first match wins:
- **red flag**: a lab-flagged critical value or a `red_flag:` in a recent result; add the `red_flag:` line
(`orchestrator/urgent`) to your `summary` at once;
- **due**: predictions or follow-ups due or overdue;
- **out of range**: a current coordinate outside its reference range;
- **off plan**: an adopted plan with missing adherence answers, a reported side effect or an overdue review;
- **quiet**: no new data for 6 months or more;
- **on track**.
3. **Write** `<PLSI_HOME>/work/<thread>/panel.json`: `{"as_of": "2026-10", "rows": [{"label", "handle", "group",
"reason", "since", "next"}]}`, the reason in clinical terms with value, unit and date, `next` one step ("prepare a visit
brief", "ask for the repeat lipid panel"). Write each panel into its own thread folder, never into
`work/panel/`, so that `memoryhole/forget` can find and delete every panel that names a patient.
4. **Return one `result`**: `panel.json` in `files`, the top 10 rows in `summary` (red flags first) and the work for
Visualizer (`visualizer/dashboard`, scope **panel**). A patient the physician picks goes to that patient's ward
bot (`ward/patient`), which asks Visit Prep for the brief.
## Rules
- You report; you never recommend a treatment, diagnose or order. Plan changes go through `clinev/protocol` and
Nostradamus.
- Labels only, never names; no patient's data in another patient's row.
- Only roster rows are patients; an instance with relation `other` and no row is never collected.
© Insilico-org · MIT · Insilico-org/plsi