How do I install the Ctx Purge skill?

Run npx skillmds@latest add gabrielmoreira/ctx-purge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ctx Purge safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ctx Purge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ctx Purge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ctx Purge?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ctx Purge by gabrielmoreira — Agent Skill

Name: Ctx Purge
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

File contents

Context Mode Purge

Permanently deletes session data for this project. Two scopes are supported (issue #520):

Project scope (scope: "project"): wipes EVERYTHING — knowledge base, all session DB rows for every session, events markdown, and stats.
Session scope (sessionId: "<id>" or scope: "session"): wipes ONLY the matching session's rows + FTS5 chunks. Sibling sessions, project stats, and the FTS5 store file are preserved.

Instructions

Decide the scope first with the user:
- "Wipe just one session?" → ask for the sessionId.
- "Wipe the whole project?" → confirm scope:'project' (this is the destructive, irreversible default).
Warn the user about scope:'project'. Everything will be deleted:
- FTS5 knowledge base (all indexed content from ctx_index, ctx_fetch_and_index, ctx_batch_execute)
- Session events DB (analytics, metadata, resume snapshots) for ALL sessions in the project
- Session events markdown file
- In-memory session stats + persisted stats file
Call the mcp__context-mode__ctx_purge MCP tool with the chosen parameters:
- Scoped: { confirm: true, sessionId: "<id>" } — implies scope:'session'.
- Project: { confirm: true, scope: "project" } — explicit destructive form.
- Bare { confirm: true } still works but emits a deprecation warning. Prefer the explicit forms.
Report the result to the user — the response lists exactly what was deleted and (for scoped purges) confirms that other sessions and project stats were preserved.

Schema rules

confirm: true is always required.
sessionId and scope: "project" together is REJECTED as ambiguous (the sessionId implies session scope; combining with project scope contradicts intent).
scope: "session" without sessionId throws — sessionId is required.

When to Use

Scoped (per-session): scratch acceptance scenarios, drill replays, isolating a polluted session without losing the main working session's stats.
Project: KB contains stale or incorrect content polluting search results, switching between unrelated projects in the same session, completely fresh start.

Important

ctx_purge is the only way to delete session data. No other mechanism exists.
ctx_stats is read-only — shows statistics only.
/clear and /compact do NOT affect any context-mode data.
There is no undo. Re-index content if you need it again.

---name: ctx-purgedescription: Purge the context-mode knowledge base. Permanently deletes all indexed content and resets session stats. This is destructive and cannot be undone. Trigger: /context-mode:ctx-purge--- # Context Mode Purge Permanently deletes session data for this project. Two scopes are supported (issue #520): - **Project scope** (`scope: "project"`): wipes EVERYTHING — knowledge base, all session DB rows for every session, events markdown, and stats. - **Session scope** (`sessionId: "<id>"` or `scope: "session"`): wipes ONLY the matching session's rows + FTS5 chunks. Sibling sessions, project stats, and the FTS5 store file are preserved. ## Instructions 1. **Decide the scope first** with the user: - "Wipe just one session?" → ask for the `sessionId`. - "Wipe the whole project?" → confirm scope:'project' (this is the destructive, irreversible default). 2. **Warn the user about scope:'project'**. Everything will be deleted: - FTS5 knowledge base (all indexed content from `ctx_index`, `ctx_fetch_and_index`, `ctx_batch_execute`) - Session events DB (analytics, metadata, resume snapshots) for ALL sessions in the project - Session events markdown file - In-memory session stats + persisted stats file 3. Call the `mcp__context-mode__ctx_purge` MCP tool with the chosen parameters: - Scoped: `{ confirm: true, sessionId: "<id>" }` — implies scope:'session'. - Project: `{ confirm: true, scope: "project" }` — explicit destructive form. - Bare `{ confirm: true }` still works but emits a deprecation warning. Prefer the explicit forms. 4. Report the result to the user — the response lists exactly what was deleted and (for scoped purges) confirms that other sessions and project stats were preserved. ## Schema rules - `confirm: true` is always required. - `sessionId` and `scope: "project"` together is REJECTED as ambiguous (the sessionId implies session scope; combining with project scope contradicts intent). - `scope: "session"` without `sessionId` throws — sessionId is required. ## When to Use - **Scoped (per-session)**: scratch acceptance scenarios, drill replays, isolating a polluted session without losing the main working session's stats. - **Project**: KB contains stale or incorrect content polluting search results, switching between unrelated projects in the same session, completely fresh start. ## Important - `ctx_purge` is the **only** way to delete session data. No other mechanism exists. - `ctx_stats` is read-only — shows statistics only. - `/clear` and `/compact` do NOT affect any context-mode data. - There is no undo. Re-index content if you need it again.

Frequently asked questions

Ctx Purge