Skip to main content
skill CX Codex

roster — Claude Code skill: patient tracking and installation

This Claude Code skill maintains a physician’s patient roster and tracks each person’s status. It activates when a patient is added, paused, closed, or removed, or shares data with the physician.

MIT ★ 93 updated 2026-11-15

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Insilico-org/plsi --skill roster -a claude-code
Open on GitHub

What roster does

The skill keeps patient labels, statuses, and shared-data lists in roster.json. It handles panel queries and roster changes, then runs plsi clinic dashboard after an edit if the dashboard file exists.

For a new patient, it asks for a label, confirmation of consent, and sex and birth year details before handing the task to Data Processor through PLSI. It never opens shared files; PLSI routes those files to that patient’s ward bot. The physician role is required. The physician’s own records and family members do not belong on this panel.

Labels must be neutral, such as patient-07; names and record numbers are disallowed. For data deletion, the skill waits for Memory Hole’s result before removing the roster row.

What it helps with

  • track patients and their current statuses
  • add a patient after consent is confirmed
  • pause or close a patient’s roster entry
  • remove a row after data deletion is confirmed

Example prompts for the agent

  • Show me everyone on my patient panel.
  • Add a patient under patient-07; they agreed to share the data they sent.
  • Pause the entry for patient-07.

How to install roster

1Skills CLI (Vercel)

npx skills add Insilico-org/plsi --skill roster -a claude-code

2Manually: put the files in place

~/.claude/skills/roster/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/roster/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about roster

How do I install roster in Claude Code?

Run npx skills add Insilico-org/plsi --skill roster -a claude-code. The skill file is at ~/.claude/skills/roster/SKILL.md.

What does roster do?

It maintains a physician’s patient list, updates patient statuses, and passes tasks to PLSI for new or removed entries. It does not open shared patient files.

What does roster need to work?

It requires the physician role and PLSI. New-patient tasks go to Data Processor, while Memory Hole handles data deletion through PLSI.

Source text

SKILL.md · MIT
---
name: roster
description: Use as PLSI Panel when the physician adds, lists, pauses, closes or removes a patient on their panel, or a patient shared their PLSI data with the physician - keep the roster (one row and one instance per patient) and the status of each.
---

# PLSI patient roster

**Status: draft**. The user here is a physician; a patient is a person who
chose to send the physician their data.

## When to use

- A patient shared data with the physician (a PLSI export, records, a letter, mail to the `+patients` address), and
  PLSI saved it unopened.
- "Who is on my panel?", "add a patient", "pause / close / remove <label>".
- Not for the physician's own health (their `self` instance) or family members.

## Steps

1. **Role and panel.** Only for the physician role; anything else: a `result` "the panel is for the physician role".

   ```bash
   plsi role show
   plsi instances list
   ```

   The panel is `<PLSI_HOME>/work/panel/roster.json` alone, one row per patient (each patient's instance has relation
   `other`, but an `other` instance with no row, such as a friend the physician tracks, is not a patient):
   `{"label": "patient-07", "status": "active|paused|closed", "shared": ["labs", "plans"], "since": "2026-10",
   "last_update": "2026-10"}`, plus `"inbox"` and `"shared_folder"` Drive folder ids once `panel/clinic` set them
   up (`"shared"` stays the list of what the patient shared), `"patient_access"` (`none` until the patient is invited,
   then `shared`) with `"patient_id"` (the invited person's Drive permission id, never their address), and
   `"reviewed"` (the as-of date of the last report the patient received); `plsi clinic` commands write these.
   Labels are neutral (`patient-07`), never names, initials or record numbers: the patient sees theirs in their
   Drive folders. The optional `"handle"` is the physician's own name for the patient, shown to the physician as
   "JD (patient-07)": a first name, initials or nickname, at most 40 characters, never a full name, record number or
   birth date, and never another patient's handle or label (`plsi clinic check` refuses a roster where two
   patients could be confused, ignoring case, spaces and dots). It stays in the roster and the physician's chat:
   never in a Drive folder name, a report, a message,
   a handoff to another bot or anything that leaves.

2. **Whose files.** Never open the shared files. Files or mail with no label yet: ONE `question`, a patient on the
   roster (the labels with handles) or a new one. A roster patient: return a `result` naming the label; PLSI hands
   the files to that patient's ward bot.

3. **New patient.** Put in ONE `question`: the label to use, a handle if the physician wants one (with three random
   two-word suggestions such as "amber fox"), sex and birth year (or none), and the physician's confirmation that
   the patient agreed to share exactly what was sent. After the `answer`, return a `result` with the work for Data
   Processor (via PLSI): `init` with `--relation other` for the new label, in a request that names the physician's
   own instance (`shared/team`, The instance exists first). Add the row once Data Processor's `result`
   arrives, and return the work for PLSI: the file paths for `processor/intake` on the new label (a ward bot is made
   later, on request, `clinic/ward`).

4. **Pause, close or remove.** Pause and close change the row only. Deleting a patient's data is Memory Hole's
   (`memoryhole/forget`, through PLSI, on the physician's explicit words); it deletes the patient's instance and the
   panel reports and work files naming the label. Say so in the `result`, and remove the row from `roster.json` only
   once Memory Hole's `result` arrives (relayed by PLSI); then return the work for PLSI: remove the ward bot,
   if the patient has one (`clinic/ward`).

5. After any change to `roster.json`, when `<PLSI_HOME>/work/clinic-dashboard/dashboard.html` exists, run `plsi
   clinic dashboard` (`panel/clinic` step 6).

6. **Return one `result`**: the roster (label, status, shared, since, last update, open plans from `plsi status
   --instance <label>`) and what changed.

## Rules

- Patient data enters only from what the patient chose to send; never look for more.
- Never contact a patient (that is `liaison/message`), never record anything yourself, never move data between
  instances. Patient instances are never sent to the Longevity Mothership.
- A handoff about one patient names that patient's instance; a panel-wide one names the physician's own and lists the
  labels in `summary`.

© Insilico-org · MIT · Insilico-org/plsi

Similar skills

SKILL.md skills catalog →
recoup-roster-list-artists recoupable recoup-roster-list-artists is a Claude Code skill that lists roster artists and their IDs by scanning the workspace, then checks the live account via API if the artists folder is empty. CX Codex +1 5,200installs recoup-roster-manage-artist recoupable recoup-roster-manage-artist manages an individual artist workspace by tracking identity, releases, and songs. Keeps roster files structured and forbids placeholder entries. CX Codex +1 5,200installs persona-roster-expander chrono-meta persona-roster-expander turns a seed list of personas into a tiered, judgment-mapped cast bounded by safety rules and exports the structure to a JSON file. CX Codex +1 ★ 33repo stars find-skills vercel-labs find-skills is a Claude Code skill that locates agent skills for a task and helps assess the results. It activates when someone asks for a capability that may already be installable. CX Codex +1 4,400,000installs frontend-design official anthropics The frontend-design skill guides intentional visual design for new interfaces and redesigns. Use it when a generic generated UI is not enough. CX Codex +1 1,025,790installs agent-browser vercel-labs This Claude Code skill automates browser interaction for tasks like navigating sites, filling forms, and testing web apps. It also supports exploratory QA and Electron app automation. CX Codex +1 1,600,000installs design-taste-frontend Leonxlnx The design-taste-frontend Claude Code skill sets design rules and checks for websites. It activates for new pages, redesigns, and requests to fix a generic-looking site. CX Codex +1 802,600installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. CX Codex +1 1,424,476installs

From the same set85

The whole set →
apple-health This Claude Code skill connects Apple Health and sends metrics to PLSI. It activates for connection requests or imports covering a requested date range. CX Codex +1 ★ 93repo stars run This Claude Code skill preregisters a research hypothesis, runs its analysis, and prepares a finding. It starts after a researcher selects a hypothesis and PLSI relays the registration receipt and Challenger objections. CX Codex +1 ★ 93repo stars sleep This Claude Code skill reads sleep data and builds a plan around the user's request. It activates for requests to improve sleep or interpret sleep measurements. CX Codex +1 ★ 93repo stars ask This Claude Code skill turns a research direction into a question that search can settle, or breaks it into child questions. It activates when plsi research next selects ask. CX Codex +1 ★ 93repo stars arrow The arrow Claude Code skill turns a health history into a timeline of past events, current state, and forecasts. It runs when someone shares their story or asks to see their main risks on one chart. CX Codex +1 ★ 93repo stars hallmarks This Claude Code skill maps a gene, pathway, or candidate to aging hallmarks and supporting evidence. It activates for requests to assess those links and possible biomarkers. CX Codex +1 ★ 93repo stars company Builds sourced research dossiers on pharma and biotech companies. It runs for a company name or ticker, or before pharma/outlook when the dossier is older than 7 days. CX Codex +1 ★ 93repo stars landscape The landscape Claude Code skill finds drugs in development against a gene. It runs on demand during target discovery or evaluation when structured sources leave gaps. CX Codex +1 ★ 93repo stars

Project sponsors

Companies that keep this analytics open