Treat Skill for Claude
Prune bloated session with a prescription. Removes progress ticks, stale reads, duplicate content, and more.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/Ruya-AI/cozempic --skill treatThe instruction itself
3 sections, as written by the authorApply 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:
cozempic current --diagnose
- Dry-run the treatment — show savings without applying:
cozempic treat current -rx $ARGUMENTS
If no argument was provided, use standard:
cozempic 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:
cozempic 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
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take ruya-ai/treat from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.