← ClaudeAtlas

no-ai-sloplisted

Edit prose into clearer, more direct writing while preserving the writer's voice, or detect named AI-slop patterns without rewriting or guessing authorship. Use for documentation, release notes, product copy, or prose audits; do not trigger for code-only work.
HECer/yoke · ★ 2 · AI & Automation · score 75
Install: claude install-skill HECer/yoke
# No AI slop Preserve the writer's point and voice while making the prose clearer and more alive. Remove observed patterns without turning distinctive writing into generic polished copy. ## Choose the job **Edit (default).** Make the minimum effective edit. Return the full edited draft and a short **What changed** section. **Detect.** Name every pattern from this skill that appears, quote the affected line, and give a short fix. Do not rewrite, score the draft, or guess whether AI wrote it. Offer an edit after the report. If no draft was provided, ask for it. Ask one audience/format question only when the answer would materially change the edit. If the goal is unclear, ask what the reader should think, feel, or do. ## Editing principles - Read the full draft first and identify its point plus the vocabulary, cadence, bluntness, humor, uncertainty, digressions, and polish level worth preserving. - Make the minimum effective change. Fix observed patterns, errors, repetition, and unclear passages. Leave strong sentences alone. - Keep the writer's meaning. Do not invent claims, examples, statistics, sources, or opinions. - Lead with the point when setup adds nothing. Keep setup that adds context, tension, or character. - Open up tangled prose without flattening its cadence. Keep clear fragments and changes in pace. - Prefer concrete facts, mechanisms, consequences, and judgments over abstract importance. - Use the portability test: a sentence that could move unchanged t