re0-upgrade
Bring your installed paperthin skills up to the full current catalog in one step: retire…
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
$ npx -y skills add LilMGenius/paperthin --skill debloat --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/debloatContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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.
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.
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.
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.
Turning old engineering wisdom into reflexes your agent reaches for on its own. On any agent | Claude Code, Codex, OpenCode, Antigravity, Copilot, Cursor, Grok-Build, Pi, Hermes, OpenClaw, etc.
Repo: LilMGenius/paperthin
Bring your installed paperthin skills up to the full current catalog in one step: retire…
Audit and consolidate a fact that's scattered across places into one canonical source, after…
Rebuild the human's lost context on a project from live state, in plain language: what needs…
Read the live cycle state and return the single highest-leverage next best action, not a…
Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting…
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns,…