ape-cut-fluff
openbooklet.com/s/ape-cut-fluffopenbooklet.com/s/[email protected]GET /api/v1/skills/ape-cut-fluffA surgical editor that strips fluff and redundant information out of a piece of writing and drives the word count down to the bare minimum needed to convey the concept. Flags and removes hedging, empty disclaimers, throat-clearing intros, cliché openers, empty subject openers, filler transitions, self-reference and meta-structure, summarising conclusions, rhetorical-question tails, intro-body-conclusion symmetry, padded constructions, nominalisations, filler qualifiers, adjective and intensifier stacks, redundant pairs, restatement and cross-paragraph repetition, redundant examples and analogies, redundant background and context, redundant elaboration, dead sentences, AI-slop framing, code-narration, ceremonial closers, and non-load-bearing filler words (articles, auxiliaries, connective tissue) whose removal does not change meaning. Use this skill whenever the user says "ape cut fluff", "cut the fluff", "trim this", "tighten this", "strip the fluff", "make this crisp", "remove filler", "remove redundancy", "deduplicate this", "edit this down", "bare minimum words", or shares a text file, raw content, blog post, research paper, or URL and asks to cut the fluff. The skill accepts input as a file path, pasted content, or a URL (which it downloads first). Output is the tightened version of the same content, reduced to the fewest words and the fewest ideas that still carry the essence.
Reviews engineering blog drafts. Use this skill whenever the user says "ape review blog", "review blog", "review this post", "give feedback on draft", "what is wrong with this post", or pastes a blog draft asking for critique, feedback, or editorial review. Also trigger when the user shares a draft and asks if it is ready to publish. Always use this skill for any engineering blog review request, even if the user just says "thoughts?" after pasting a post.
Guidelines for writing pseudocode for functions and algorithms. Use this skill whenever the user asks to write pseudocode, sketch out an algorithm, or describe the logic of a function at a high level. Trigger on phrases like "write pseudocode", "sketch this algorithm", "pseudocode for this function", or "describe the logic".
Auto-indexed from arpitbbhayani/ape-skills
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.