ward — Claude Code skill: patient bot management
The ward Claude Code skill manages individual patient bots in a PLSI team. It creates one when a physician starts work on a roster patient, or removes it after the patient leaves the roster.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill ward -a claude-codeWhat ward does
The skill creates a Ward bot for a roster patient and records it in the team with plsi team add. If that patient already has a bot, it updates the existing one rather than making another. Each patient gets one bot at most.
It asks the physician before opening a separate chat unless the request already calls for one. The skill checks the Grok bot count before creating anything: at 45 bots or more, it asks for one to be removed; the account limit is 50. When a roster row is removed, it closes the bot’s open threads and removes the team entry with plsi team remove.
The skill requires plsi installed on the computer and a Grok account. Bots are created only for roster patients; pausing or closing a roster row leaves its bot in place.
What it helps with
- open a dedicated chat for a PLSI roster patient
- avoid creating a duplicate bot for one patient
- remove a bot from the team after its roster row is deleted
- free a Grok bot slot before creating another patient bot
Example prompts for the agent
- Open a dedicated Ward chat for patient P-07.
- Review patient amber fox’s results in their Ward chat.
- Patient P-07 was removed from the roster; remove their Ward bot from the team.
How to install ward
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill ward -a claude-code2Manually: put the files in place
~/.claude/skills/ward/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ward/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill ward -a codex2Manually: put the files in place
.agents/skills/ward/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill ward -a cursor2Manually: put the files in place
.cursor/skills/ward/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/clinic/ward2Manually: put the files in place
.github/skills/ward/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill ward -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/clinic/wardManually: put the files in place
.devin/skills/ward/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 ward
How do I install ward in Claude Code?
Run npx skills add Insilico-org/plsi --skill ward -a claude-code. The skill file is at ~/.claude/skills/ward/SKILL.md.
What does ward do?
It creates a personal Ward bot for a PLSI roster patient when the physician starts working with them. After a roster entry is removed, it closes the bot’s open threads and removes it from the team.
What does ward need to run?
It needs plsi installed on the computer and access to a Grok account. A Grok account has a limit of 50 bots.
Source text
SKILL.md · MIT
--- name: ward description: Use as PLSI Clinic Orchestrator when the physician wants to work on one roster patient and that patient has no ward bot yet, or a patient is removed from the roster - create that patient's ward bot (Ward · <label>, section Ward) on request and within the account's bot limit, or remove it, and keep the team list in step. --- # PLSI ward bots Follow persona.md norms and `shared/team`. Owner: **PLSI Clinic Orchestrator**. **Status: draft**. A ward bot is the patient's own chat, pinned to that patient's instance. The physician talks to it directly; it is a hub like you (`ward/patient`). It is made on request, when the physician starts working on that patient, never for every roster row: a Grok account holds at most 50 bots, and a full team is about 30 before any ward bot. Bots hold no data, so creating or removing one loses nothing. ## When to use - The physician wants to work on one roster patient who has no ward bot (`clinic/panel` step 6). Recognise it by what is asked, in any wording or language, never by a phrase: a brief, a visit, a message, a plan, a report, a question about that patient's results or uploads, "let's go through P-07", "open a chat for amber fox". A question about the panel as a whole is not one. - A roster row was removed, or `plsi team show` lists a ward bot whose patient has no row. - A ward bot on the team no longer exists in Grok: say so in one line and offer "Create Ward · <label> again?"; never recreate it unasked. ## Steps 0. **Ask, then count.** ONE card "Work on <label> in their own chat, Ward · <label>?": Open it / Not now (no card when the physician asked for that chat outright). Not now: nothing is created, and one-patient work for this label waits (`clinic/panel` step 6). Open it: count the bots in `plsi team show`. At 45 or more (the account limit is 50, and other bots may share it), do not create one: ONE card "Your Grok account is near its 50-bot limit (<n> PLSI bots). Remove a ward bot you are not using?" listing the ward bots with no open thread (`orchestrator/conduct`), at most 3, the longest unused first, and Cancel. A picked bot is removed as in step 4, without Memory Hole (its patient stays on the roster, and their data stays), then go on. Grok refusing to create the bot for its limit is the same card. 1. **Match first.** `plsi team show`: a ward bot for this label already exists: update it in place, never a second one. 2. **The section, never waited for.** At the first ward bot, check for the sidebar section **Ward**. Missing: create the bot unassigned and send, once, the optional line of `shared/hub` (Sidebar sections, A missing section), "Each patient gets their own bot. Optional: to keep them together, add a section named exactly Ward in Grok's side menu and drag them into it." Never again; later ward bots go in Ward when it exists. 3. **Create** the bot in **Ward** (unassigned while it is missing): name from the `ward` row of `shared/team` and description from its profile in `shared/hub`, with `<patient label>` = the label (never a handle, name, initials or record number). Send this as its first direct message, the Opening from that profile with the label filled in: > **Ward · <label>** > <opening> > > You are Ward · <label> in the PLSI team. Remember these rules permanently: (1) before every new task, read > `<repo>/skills/shared/team/SKILL.md` and `<repo>/skills/shared/hub/SKILL.md`; (2) adopt `<repo>/persona.md` as your persona; (3) your skills are > `<repo>/skills/ward/` and the hub skills `orchestrator/conduct`, `orchestrator/urgent` and > `orchestrator/answer`; use no others; (4) you are a hub for one patient: instance `<label>` only, in every > command and every handoff; you talk to the physician in this chat and dispatch to the workers yourself; > anything else goes to PLSI · Clinic Orchestrator; (5) `plsi` is installed on this computer; `plsi team show` > lists the team; (6) set your name to Ward · <label> and avatar now with `UpdateProfile`: colour `green`, shape > `heart`. When you have saved these rules, reply to PLSI · Clinic Orchestrator with a `result` handoff (thread > `setup`, skill `shared/team`, instance `<label>`). Record it with `plsi team add --role ward --display-name "Ward · <label>" --hub clinic --instance <label>`. Unlike workers, a ward bot talks to the physician: its notifications stay on. Wait for its `result` (`orchestrator/conduct`) before handing it the patient's first files. 4. **Remove** after `panel/roster` removed the row: send the ward bot a `request` (skill `ward/patient`, thread `remove-<label>`) to close its open threads and one-time routines, wait for its `result`, then `plsi team remove --display-name "Ward · <label>"` and ask the physician in one line to delete Ward · <label> in Grok. Its data is already gone (`memoryhole/forget`). ## Rules - Only roster patients get a ward bot, and only on request (step 0); a paused or closed row keeps its bot. - A ward bot removed for room (step 0) loses nothing: the patient, the row and the data stay, and the next one-patient request offers it again. - A ward bot never serves a second patient, and a patient never gets a second ward bot.
© Insilico-org · MIT · Insilico-org/plsi