diet
Skill2 starsChanged 5 months agoMITView on GitHub
Audit what is eating the context window in this project (CLAUDE.md size, MCP servers, rules that should be skills) and produce a concrete slimming plan with estimated token savings. Use when the user complains about context filling up fast, frequent compaction, or asks to optimize/reduce context usage.
In this repository3 other files it gives its agents.
- checkpointSkill
- focusSkill
- resumeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Check each of these (skip silently if absent):
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/amber:diet — context audit & slimming plan
Audit this project's fixed context costs and produce a slimming plan. Fixed costs are paid every turn of every session — a 2,000-token CLAUDE.md in a 100-turn session is 200K tokens of spend and a fatter, dumber context.
1. Measure the consumers
Check each of these (skip silently if absent):
| Consumer | How to check | Red flag |
Project CLAUDE.md (+ imports) | Read it, estimate tokens (~chars/3.5) | > 300 lines |
User ~/.claude/CLAUDE.md | Read it | Project-specific content in a global file |
| MCP servers | .mcp.json, ~/.claude.json mcpServers for this project | Servers with 10+ tools that are rarely used — every tool schema is always-loaded context |
.claude/rules/, large always-on context files | List + size | Rules that only apply to specific situations |
.claude/skills/ | List descriptions | Bloated descriptions (the description line is the only always-loaded part — bodies are free) |
2. Classify every instruction in CLAUDE.md
- Keep (always-relevant): build commands, hard constraints, style rules that apply to every edit.
- → Skill (situational): anything starting with "when X, do Y" that isn't hit every session — deploy procedures, release checklists, how to run a specific tool. Move the body into a skill; only its one-line description stays resident.
- → Delete: things Claude can derive from the code, duplicated docs, stale instructions.
3. Deliver the plan
Output a short report:
- Current fixed cost estimate (tokens per turn) by consumer.
- Specific moves: "lines X–Y of CLAUDE.md → new skill
deploy-checklist", "disable MCP server Z (used 0 times in recent sessions, costs ~N tokens of tool schemas)". - Estimated fixed-cost after the diet.
Then ask whether to apply the moves. If the user approves, perform them: create the skill files (with description frontmatter written for recall, ≤ 2 lines), trim CLAUDE.md, and list every change made. Do not delete anything without showing it first.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.