prune — Claude Code skill: remove notes and install
The prune Claude Code skill removes research notes marked retire. PLSI calls it after a research session or daily run when retired notes are forwarded.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill prune -a claude-codeWhat prune does
The skill removes notes from a PLSI project’s notes/ folder when retire_reason identifies a duplicate, dead end, off-topic note, or obsolete material. A duplicate must name an existing note that stays. Each removal is recorded in the project’s notes/retired.md before the note is deleted.
Only notes their owner marked retire can be removed. Questions, hypotheses, and findings stay in place, as do notes marked submitted, accepted, or rejected. The skill leaves topic folders untouched, including the append-only log.jsonl.
PLSI and its plsi command are required. The skill returns a result listing removed notes and notes sent back with the reason for each.
What it helps with
- remove owner-marked
retirenotes - delete a duplicate while naming the kept note
- send back a note with an unsupported retirement reason
- record removals in
notes/retired.md
Example prompts for the agent
- Process PLSI notes marked
retireafter the research session. - Remove the duplicate if its reason names an existing note to keep.
- Return notes with unsupported reasons and list them in the result.
How to install prune
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill prune -a claude-code2Manually: put the files in place
~/.claude/skills/prune/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/prune/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill prune -a codex2Manually: put the files in place
.agents/skills/prune/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill prune -a cursor2Manually: put the files in place
.cursor/skills/prune/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/memoryhole/prune2Manually: put the files in place
.github/skills/prune/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill prune -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/memoryhole/pruneManually: put the files in place
.devin/skills/prune/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 prune
How do I install prune in Claude Code?
Run npx skills add Insilico-org/plsi --skill prune -a claude-code. The skill file is placed at ~/.claude/skills/prune/SKILL.md.
What does prune do?
It removes PLSI research notes marked retire when their reason matches an allowed case. Each removal is logged in notes/retired.md.
What does prune need to run?
It requires PLSI and the plsi command. The skill processes project notes forwarded after a research session or daily run.
Source text
SKILL.md · MIT
--- name: prune description: Use as PLSI Memory Hole when PLSI forwards research notes marked retire (duplicates, dead ends, off-topic) after a research session or a daily run, to remove them, with every removal logged. --- # PLSI prune research notes Notes are the files in each project's `notes/` (`<PLSI_HOME>/research/projects/<project>/notes/`), written by PLSI Research Orchestrator (`lab/session`). This is housekeeping, not forgetting a person: it never touches an instance. **Only notes are ever removed.** Questions, hypotheses and findings are never deleted: a direction that dies gets `status: closed` with a reason and stays. A request to remove one goes back, saying so. ## When to use - A `request` naming research notes marked `retire`, after a research session or a daily research run. ## Steps 1. ```bash plsi research notes --status retire ``` Take the notes the request names (all of `retire` when it names none), by their `name`. 2. Read each note and remove it only when its `retire_reason` says duplicate (and names the kept note, which exists), dead end, off-topic or obsolete. Anything else goes back unremoved with the reason. ```bash plsi research retire --name "<name>" --project <id> --reason "<retire_reason>" ``` It refuses a note that is not marked `retire`. Each removal is logged first in its project's `notes/retired.md`, then the note is removed. 3. Return one `result`: the notes removed, the ones sent back and why. ## Rules - Only notes marked `retire` by their owner are removed; never mark one yourself and never edit one. - `submitted`, `accepted` and `rejected` notes are never removed, whatever a later status says. - Nothing under a topic folder is yours to touch, including `log.jsonl`, which is append-only.
© Insilico-org · MIT · Insilico-org/plsi