Agent skill
treat
Prune bloated session with a prescription. Removes progress ticks, stale reads, duplicate content, and more.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/treat
SKILL.md
Apply a pruning prescription to the current session. Default is standard if no argument given.
When to use treat vs reload: prefer the reload skill — it does the same prune plus auto-resume in one step (/exit → new terminal opens with the pruned session). Use treat only when the user explicitly wants to stay in the current session, work in a multi-pane setup, or resume manually.
Steps
-
Diagnose first — show the user what they're working with:
bashcozempic current --diagnose -
Dry-run the treatment — show savings without applying:
bashcozempic treat current -rx $ARGUMENTSIf no argument was provided, use
standard:bashcozempic treat current -rx standard -
Show results — present the dry-run output including token savings (the
Tokens:line). Always surface both byte and token savings. -
Ask confirmation — use AskUserQuestion to confirm before applying.
-
Apply on confirmation:
bashcozempic treat current -rx $ARGUMENTS --execute -
Tell the user: "Treatment applied. A backup was created automatically. To resume with the pruned session, exit and run
claude --resume. (Tip: next time, thereloadskill does this in one step —/exitand a fresh terminal opens automatically.)"
Prescriptions
| Rx | Strategies | Typical Savings |
|---|---|---|
gentle |
progress-collapse, file-history-dedup, metadata-strip | 40-55% |
standard |
gentle + thinking-blocks, tool-output-trim, stale-reads, system-reminder-dedup | 50-70% |
aggressive |
standard + error-retry-collapse, document-dedup, mega-block-trim, envelope-strip | 70-95% |
Safety
- Always dry-run first — never execute without showing the user what will change
- Backups are automatic (timestamped .bak files)
- Never touches uuid/parentUuid — conversation DAG stays intact
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?