Cut Fluff Skill

A surgical, single-pass editor. Walks the input top to bottom and removes every sentence, phrase, or word that delays the point without adding meaning. Cuts only -- does not reinterpret, restructure, or rewrite arguments. The author's voice, facts, and structural intent stay intact; the fat comes off.

The goal is the bare minimum word count that still lets a competent reader understand the concept and grasp the essence. If a word can be dropped without changing meaning, drop it. If a sentence can be shrunk into a clause without losing a fact, shrink it. If an idea, example, or piece of context appears more than once, keep only the strongest instance and cut the rest. Aim for prose so dense that every remaining word is doing work and every remaining idea is appearing for the first time.

What Counts as Fluff

The skill cuts the following on sight. Any phrase, sentence, or paragraph that matches one of these patterns is fluff:

• Hedging language: "it is important to note that", "it should be mentioned that", "it is worth pointing out that", "needless to say", "as a matter of fact", "to be honest", "in my opinion", "I think", "perhaps", "arguably" -- when they soften a claim the author is willing to make outright
• Empty disclaimers: "of course there are exceptions", "this is a simplification", "your mileage may vary", "obviously this depends on context", "every system is different" -- if the disclaimer does not name a specific exception, cut it; if it names one, keep only the naming clause
• Throat-clearing intros: "In this post we will...", "Before we begin...", "Let us first understand...", "As we all know...", "To start with...", "First of all..." -- any windup that delays the first real sentence
• Cliché openers: "In today's fast-paced world...", "In the age of AI...", "As engineers, we all know...", "We live in a world where..." -- generic openers that could front any blog; cut and let the first concrete claim be the opener
• Empty subject openers: "There is...", "There are...", "It is...that...", "What is interesting is that...", "The thing about X is that..." -- strip the placeholder and let the real subject lead. Example: "There are many systems that fail under load" → "Many systems fail under load."
• Filler transitions: "Now that we understand X, let us look at Y", "With that said...", "Having said that...", "Moving on...", "That being said...", "On a related note..."
• Self-reference and meta-structure: "in this section", "in the next section we will", "this article will cover", "as we will see", "as discussed earlier", "as mentioned above", "more on this later", "we will return to this", "(spoiler alert)" -- meta-commentary about the structure of the post that adds no information
• Summarising conclusions: "As we can see...", "In summary...", "To wrap up...", "In conclusion...", "What this essentially means is..." -- especially when the next sentence repeats what was just said
• Rhetorical-question tails: "Right?", "Isn't it?", "Make sense?", "You with me?" -- performative, not informative
• Intro→body→conclusion symmetry: the "tell them what you will tell them, tell them, tell them what you told them" pattern; the previewing intro and the summarising closer are usually both fluff and the body carries the argument on its own; cut whichever the body makes redundant, keep the one that earns its place
• Padded constructions: "in order to" → "to", "due to the fact that" → "because", "at this point in time" → "now", "a large number of" → "many", "the majority of" → "most", "in the event that" → "if", "with regard to" → "about", "for the purpose of" → "to"
• Nominalisations: verbs buried inside noun phrases that bloat the sentence; restore the verb. "make a decision" → "decide", "perform an analysis" → "analyse", "carry out an evaluation" → "evaluate", "give consideration to" → "consider", "reach a conclusion" → "conclude", "have a discussion about" → "discuss", "is in agreement with" → "agrees with"
• Filler qualifiers: "basically", "essentially", "really", "actually", "quite", "very", "just", "simply", "literally", "definitely", "totally", "absolutely" -- when they add no information
• Adjective and intensifier stacks: "extremely fast", "incredibly difficult", "super important", "really critical", "absolutely essential", "highly significant" -- the noun or adjective carries the weight alone; cut the intensifier or replace the pair with a single stronger word
• Redundant pairs: "end result" → "result", "future plans" → "plans", "completely eliminate" → "eliminate", "advance planning" → "planning", "added bonus" → "bonus", "first introduced" → "introduced", "past history" → "history", "free gift" → "gift"
• Restatement and repetition: any idea, fact, definition, or framing that the post states more than once -- adjacent sentences that say the same thing, cross-paragraph repeats where the same point reappears sections later, definitional repetition where the same term or acronym is defined twice, and heading-body restatement where a heading and its first sentence carry the same claim ("Why caching matters" → "Caching matters because..."); keep the strongest mention and cut the rest, or collapse overlapping mentions into one sharper sentence
• Redundant examples and analogies: when the post offers two or three examples, analogies, or illustrations of the same point, keep the strongest one and cut the others; do not preserve a parallel example just because the author wrote it. The rule of thumb is: if the second example does not introduce a new failure mode, a new trade-off, or a new edge case the first did not surface, it is redundant
• Redundant background and context: setup, history, or motivation that the reader already has from earlier in the post, from the title, or from the heading; cut prerequisite explanations that the post itself just covered, recaps that exist only because the author is afraid the reader has forgotten, and "as a refresher" passages that re-explain something stated a few paragraphs above
• Redundant elaboration: a claim followed by a longer paragraph that says the same thing in more words without adding mechanism, evidence, or consequence; keep the crisp claim, cut the elaboration. If the elaboration introduces a number, a system name, a failure mode, or a trade-off the claim lacked, keep the new fact and cut the rest
• Idea redundancy across the whole post: the most expensive form of redundancy. Two paragraphs in different sections that make the same argument from slightly different angles; a sidebar that repeats the main thread; a "key takeaway" box that restates the section it sits inside. During the first read, flag every place the same idea reappears; in the cutting pass, keep one canonical mention -- usually the earliest or the most concrete -- and cut every echo, even if the echoes are well-written
• Dead sentences: any sentence that survives only because the sentence before it already carried the point
• AI-slop framing: overly balanced "On one hand... on the other hand..." paragraphs where one side is obviously the answer; symmetric conclusions that restate the intro; generic exhortations ("This is a powerful technique that engineers should consider when designing systems")
• Code-narration: prose right after a fenced code block that re-describes what the code does line by line; cut the narration and keep only sentences that add intent, trade-offs, or non-obvious behaviour the code itself does not show
• Ceremonial closers: "Thank you for reading", "Hope you found this useful", "Stay tuned for more" -- cut entirely
• Non-load-bearing filler words: individual words whose removal does not change meaning -- redundant articles ("the", "a", "an") where the sentence parses without them, auxiliary verbs ("is being used" → "uses", "can be seen to" → ""), expletive subjects, relative pronouns wh