manage-claude-projects
Inspect, audit, and clean up your local Claude Code projects under ~/.claude. Use this whenever the user wants to see which projects Claude Code has tracked on this machine, get statistics about a project (session count, project-local skills/agents/commands/MCPs/plugins, disk usage, token usage, estimated cost), or remove/clean up a project's traces from ~/.claude. Trigger on phrases like "manage my claude projects", "list my claude code projects", "how many sessions / how much have I spent on project X", "token usage for this project", "delete this project from claude", "remove project X from ~/.claude", "clean up old claude projects", "which projects are taking up disk space", or any request to audit or purge local Claude Code project data — even when the user names a path or project instead of saying "project".
Target: Data analysis. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Manage Claude Code Projects
- Where the data lives (so you can explain it)
- Step 1 — Identify the project
- Step 2 — Show basic stats
- Step 3 — Offer actions
- Step 4a — Deep statistics
- Step 4b — Remove / clean up (destructive — be careful)
- Output style
Inventory, deep-stat, and safely clean up the projects Claude Code tracks under /.claude. All heavy lifting is done by scripts/projects.py (stdlib Python, prints JSON). Your job is to drive the interactive flow: pick a project, show stats, offer actions, and confirm anything destructive. Run everything as: python3 "${CLAUDEPLUGINROOT}/skills/manage-claude-projects/scripts/projects.py" A "project" exists in two places: /.claude.json → projects{ : {...}} — the registered project with its config, MCP servers, and last-session cost/token snapshot. /.claude/projects/ / — one .jsonl transcript per session. Encoded name = every non-alphanumeric char of the path replaced with -. Each session id (the .jsonl filename) also keys traces elsewhere: todos/ -, file-history/ /, and history.jsonl lines (matched by the project's absolute path). These are what removal targets. Resolve the target before doing anything else, in this order: 1. User gave a path or name — if they passed an absolute path, use it. If they gave a partial name (e.g. "staffing-assistant"), run list and match it against the project paths; if more than one matches, show the matches and ask which one. 2. No project given — run: T
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- svd/agent-skills
- Source file
- plugins/manage-claude-projects/skills/manage-claude-projects/SKILL.md
- Fixed revision
- cb47e43decd9132b8b9ffc29a43960cc5724435e
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: svd/agent-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-11T00:00:19.060Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.