Skip to main content
skill CX Codex

forget · insilico-org — Claude Code skill: what it does, how to install

The forget Claude Code skill removes PLSI records tied to one person. It runs when PLSI relays a request to erase the user’s data or that of someone they added.

MIT ★ 93 updated 2026-11-15

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

What forget does

The skill checks whether the person’s PLSI instance exists and counts its records and related files. If the request has no confirmation yet, it sends PLSI a question offering export, deletion, or cancellation. The user confirms through a PLSI card, not in the agent chat.

When export is requested, the skill saves it outside the instance folder before deleting the instance with plsi instances delete and removing related files. Deletion requires explicit approval for one instance and cannot be undone. If the delete command fails, the skill leaves the files in place.

What it helps with

  • remove one person’s records from PLSI
  • count related files before deleting an instance
  • export an instance before removing its data

Example prompts for the agent

  • Pass PLSI a request to erase all records for the alice instance.
  • Prepare deletion of patient p_123 and show the related files in a PLSI card.
  • Export the alice instance, then delete it after I confirm through PLSI.

How to install forget

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/forget/SKILL.md

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

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

Questions about forget

How do I install forget in Claude Code?

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

What does forget do?

It handles deletion of one person’s PLSI data by checking the instance and related files, exporting data when requested, then removing it after explicit approval through a PLSI card. The deletion cannot be reversed.

What does forget need to run?

It needs PLSI and the plsi command to manage instances. Deletion approval must come through a PLSI card.

Source text

SKILL.md · MIT
---
name: forget
description: Use as PLSI Memory Hole when PLSI relays the user's request to delete everything recorded about one person (the user or someone they added) for good.
---

# PLSI forget

## When to use

- A `request` with skill `memoryhole/forget` naming one `instance`: the user wants that person's data gone.
- Withdrawing single items is PLSI Data Processor's (`processor/intake`, correct or retract), via PLSI; never delete
  for a correction.

## Steps

1. Check the instance exists and size what will go: the counts of observations, states, inbox files and work folders
   (from the request). For a patient (physician role: a row of `<PLSI_HOME>/work/panel/roster.json`), also count the
   files that name the patient's label outside the patient's instance: the physician's panel reports
   (`<PLSI_HOME>/<physician instance>/reports/*.html` rendered from a `panel.json`), the `panel.json` files, the
   clinic dashboard (`<PLSI_HOME>/work/clinic-dashboard/`) and the `work/<thread>/` folders (visit briefs,
   messages) that hold it, and its Ward bot's follow-ups folder
   `<PLSI_HOME>/work/ward-<label>/`. Then look for copies outside `<PLSI_HOME>`: every
   bot shares this computer, so search the work areas (`/workspace`, each bot's home folder, `/tmp`; never the PLSI
   repo or another instance) for files that hold its subject id (`s_…`; the label too when it is not a common word
   such as `me`), or are byte copies of its inbox files, and count them by folder. Send ONE `question` to PLSI with the instance, its relation, the counts, the offer of an export, and the exact choice ("Delete everything recorded
   about <instance> for good? It cannot be undone." Export, then delete / Delete / Cancel). Skip this question when
   the request's `answers` already hold a PLSI card's delete question with the user's selection naming this
   instance (setup step 6, or a forget card): that selection is the user's explicit confirmation; go to step 2.

   ```bash
   plsi instances list
   ```

2. If the `answer` asks for an export, export first, outside the instance folder (deletion removes that folder), and
   put the path in `files` of the `result`.

   ```bash
   plsi export --instance <instance> --out <PLSI_HOME>/exports/<instance>
   ```

3. Delete only on the user's explicit words relayed unchanged in `answers`, from the user's answer to PLSI's card
   in the chat; never under a standing approval, never on PLSI's own judgment and never on a voice call relay (a
   `voice:<call>` ask, or words a voice agent passed on): then reply with a `question` that PLSI shows as the card. The command refuses unless `--confirm` repeats the instance name. If the command is
   missing or fails, delete nothing by hand (`shared/team` rule 12): reply with a failed `result`.

   ```bash
   plsi instances delete --instance <instance> --confirm <instance>
   ```

4. Then delete only the inbox files, `work/<thread>/` folders, the copies outside `<PLSI_HOME>` found in step 1
   and, for a patient, the panel reports and `panel.json`
   files counted in the confirmed question, `<PLSI_HOME>/inbox/<label>/`, `<PLSI_HOME>/work/ward-<label>/` and the label's lines in
   `work/panel/synced.jsonl` (rewrite the file without them), and drop the instance from your memory. Never edit `roster.json` or
   anything inside another instance besides those reports: for a patient, the `result` names the work for Panel
   (`panel/roster`, via PLSI) to remove the row. Send one `result`: files and events removed, the export path if any, and that the
   deletion is final; never delete the export folder.

## Rules

- The confirmation reaches the user only as one PLSI question card: never ask, confirm or show a card in your own
  chat, also not "to be safe"; a doubt goes to PLSI as a `question` handoff.
- One instance per request.
- There is no backup and no undo; say so in the question.
- Only this skill runs `plsi instances delete`.
- Other bots hold only hashes and summaries; PLSI drops the instance from its own memory and tells the bots on the
  team to do the same. Afterwards no bot quotes a value or summary from before the deletion: a summary of a new
  instance comes only from that instance's records.

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

Similar skills

SKILL.md skills catalog →

forget by other authors comes first.

forget rohitg00 forget deletes selected durable memories from agentmemory after explicit confirmation. Useful when scrubbing secrets or obsolete notes. CX Codex +1 14,800installs forget mem0ai This skill removes Mem0 memories for a user and repository. Use it when you want an agent to clear or forget stored memories. CX Codex +1 155installs nan-forget NaNMesh nan-forget stores project facts and decisions locally, then brings relevant context into later coding sessions. Useful when an agent keeps losing track of past work. CX Codex +1 ★ 5repo 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 grill-with-docs Matt Pocock The grill-with-docs skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. CX Codex +1 1,219,756installs

From the same set85

The whole set →
substances The substances Claude Code skill builds plans to quit or reduce smoking, vaping, or alcohol use. It checks for risks from stopping without supervision and sets a stepwise schedule. CX Codex +1 ★ 93repo stars extend extend is a Claude Code skill for adding operations to PLSI that maps and single formulas cannot handle. It comes into play when PLSI needs to read a new file format, run a more involved calculation, or search another evidence source. CX Codex +1 ★ 93repo stars nudge The nudge Claude Code skill manages reminders between plan check-ins. It schedules messages about follow-up visits, measurement windows and the first days of a plan. CX Codex +1 ★ 93repo stars add-score add-score — a Claude Code skill that adds a new derived measure to a PLSI map. It activates when a request needs a score or equation the existing maps do not compute. CX Codex +1 ★ 93repo stars mothership This Claude Code skill checks Mothership access and reads its public catalog and findings ledger. It prepares research notes or registry contributions for review by the Data Controller. CX Codex +1 ★ 93repo stars assess A skill for Claude Code assesses health data through PLSI maps. It runs after new data arrives or when asked about biological age, risk markers, or trends. CX Codex +1 ★ 93repo stars 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

Project sponsors

Companies that keep this analytics open