debloat — Claude Code skill: what it does, how to install
Compresses bloated docs and prose down to load-bearing density without losing facts or constraints. Useful when accurate text grew verbose through successive edits.
npx skills add LilMGenius/paperthin --skill debloat -a claude-codeWhat debloat does
The skill targets verbal bloat: unnecessary qualifiers, wall-to-wall lists, fused sentences, and adjacent restatements of the same rule. It keeps every load-bearing claim intact. Facts and technical constraints stay in place while filler words get cut.
Execution happens in place without restructuring the entire document. The agent reads the text, notes the primary purpose of each section, and trims clauses. Edits are handled safely: it enforces unicode-safe editing via PYTHONUTF8=1 and reports an explicit MISS if a target block cannot be found.
This skill focuses strictly on text density. It will not rewrite stale prose (the author delegates that to re0) or deduplicate text across multiple files (which belongs to ssotize). If a sentence is already lean, the pass leaves it unchanged.
What it helps with
- strip padding and parenthetical qualifiers from docs
- collapse wall-of-text enumerations into concise lists
- split fused sentences carrying multiple thoughts
- eliminate adjacent restatements of existing rules
Example prompts for the agent
- Run debloat on
README.mdto trim padding while keeping every technical rule. - Apply the debloat skill to
docs/specs.mdto shorten verbose paragraphs.
How to install debloat
1Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill debloat -a claude-code2Manually: put the files in place
~/.claude/skills/debloat/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/debloat/
1Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill debloat -a codex2Manually: put the files in place
.agents/skills/debloat/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill debloat -a cursor2Manually: put the files in place
.cursor/skills/debloat/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install LilMGenius/paperthin debloat2Manually: put the files in place
.github/skills/debloat/SKILL.md1Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill debloat -a gemini-cli2Platform CLI
gemini skills install https://github.com/LilMGenius/paperthin --path skills/depth/debloatManually: put the files in place
.devin/skills/debloat/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill debloat -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about debloat
How do I install debloat in Claude Code?
Run npx skills add LilMGenius/paperthin --skill debloat -a claude-code. Alternatively, copy the skill definition directly into ~/.claude/skills/debloat/SKILL.md.
What is the difference between debloat, ssotize, and re0?
Debloat only increases density within a single artifact. It does not rewrite drifted content like re0 or extract duplicated sections across files like ssotize.
How does debloat ensure edit safety?
It edits with unicode safety via PYTHONUTF8=1, replaces target text per occurrence, and reports a MISS instead of failing silently when a target string is absent.
Source text
SKILL.md · MIT
--- name: debloat disable-model-invocation: true description: "Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved. Use when prose is correct and current but has grown verbose or patched-over and you want it tight without a full rewrite." --- Cut a bloated artifact to its load-bearing minimum: same meaning, fewer words. ## Goal An artifact that is correct and current can still rot a second way: it accretes. Each edit bolts a qualifier onto the nearest sentence, a rule gets restated wherever it might apply, an enumeration grows into a wall — until a reader must study what they should skim. `debloat` compresses that bloat to its load-bearing density: every claim that carries weight survives, every word that does not is cut. It is not a rewrite (`re0`), a dedup (`ssotize`), or a tell-remover (`dedash`, `detool`) — it is a density pass on prose that is otherwise fine. ## Workflow 1. Pin the artifact and read it end to end; note in one line what each section must convey — the load-bearing content that has to survive. 2. Find the bloat, not the content: padding that adds length but not meaning; a qualifier or parenthetical the sentence holds without; a fused sentence carrying three ideas; a wall of enumeration where a rule plus a short list would do; a point restated within reach of itself; litigation-history (why-we-decided-it) where the rule alone suffices. 3. Compress in place: cut the padding, split the fused sentence or drop its dead clause, collapse the wall, keep a repeated point once. Move nothing to another artifact and re-derive nothing. 4. Preserve every load-bearing claim — a rule, fact, constraint, or example that carries weight. If cutting a word would lose one, keep the word. 5. When the bloat is really duplication across artifacts, or the content has drifted stale, stop and name it: hand duplication to `ssotize` and drift to `re0`. `debloat` only tightens. 6. Re-read cold and cut again — the first pass always leaves some. ## Rules - Cut words, never load-bearing claims. Every rule, fact, and constraint that was there is still there; only the density changed. - Preserve the artifact's voice and structure; compress within it, do not re-style it. - Not a rewrite, a dedup, or a tell-remover: re-derive nothing (`re0`), move nothing to another home (`ssotize`), and leave em-dashes and stack nouns to `dedash`/`detool`. - Respect intended richness: human-facing prose meant to teach or orient (a quickstart, a worked example) earns its length — compress the bloat, not the accessibility. - A pass that finds nothing genuinely bloated changes nothing. - Mutate with edit-safety: assert each target exists (report a MISS, never a silent no-op), edit unicode-safe (`PYTHONUTF8=1`), replace per occurrence, and script a large structural move. ## Verification Before finishing: 1. Every load-bearing claim present before is present after — only words were cut. 2. The result reads tighter to a cold reader, and reads as intended-terse, not amputated. 3. Anything that was duplication or drift, not bloat, was handed to `ssotize`/`re0`, not force-compressed.
© LilMGenius · MIT · LilMGenius/paperthin