skills/de-slop/SKILL.md
Remove LLM-isms and AI writing patterns from text. This skill should be used when editing prose to sound less like AI output — removing overused words, fixing structural tells, and restoring natural human voice. Triggers: "de-slop", "remove AI writing", "humanize this", "sounds too AI", "LLM-isms", "AI slop", or when reviewing text that reads like chatbot output.
npx skillsauth add petekp/agent-skills de-slopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Strip AI writing patterns from text to restore natural, human-sounding prose.
Based on Wikipedia: Signs of AI writing and WikiProject AI Cleanup.
Read the full text before changing anything. Load references/word-list.md and references/structural-patterns.md to identify which patterns are present.
Categorize findings into three severity levels:
Red — Immediate tells (fix first)
Yellow — Statistical signals (fix in clusters)
Green — Structural patterns (require rewriting, not word swaps)
Present the diagnosis as a brief summary before making changes. Example:
Diagnosis: 4 red flags (chatbot leakage, grandiose filler), 7 yellow signals
(word clusters in paragraphs 2, 5, 8), 2 green patterns (relentless balance,
uniform register).
Remove or replace all Red items. These are unambiguous AI artifacts.
Chatbot leakage: Delete entirely.
Grandiose filler: Replace with plain statements or delete.
Synonym cycling: Pick one term and stick with it. Use pronouns for variety.
Work through clusters. The goal is not to ban specific words but to break up detectable patterns.
Word clusters: Replace overused words with plain alternatives.
Copula avoidance: Restore simple verbs.
Transition abuse: Remove mechanical connectives.
Rule of three: Break at least half of them. Use two items, or four, or one.
Tailing participles: Rewrite as separate sentences or delete.
These require actual rewriting, not substitution.
Relentless balance: Redistribute weight. Expand important sections. Trim or collapse unimportant ones. A 3-sentence paragraph next to a 12-sentence paragraph is fine.
Uniform register: Inject tonal shifts. A blunt short sentence after a complex one. A casual aside in a technical passage. Let the writing breathe.
Generic specificity: Replace hypothetical examples with real ones, or remove examples that add nothing.
Excessive hedging: Remove qualifiers that don't reflect genuine uncertainty. If something is true, state it without "often" / "generally" / "can be."
Risk aversion: Sharpen claims. Add an opinion. Allow an imperfect sentence to stand if it has energy.
Enthusiasm gap: Vary paragraph investment. Spend more words where the writer (or subject) is more interesting.
Read the entire edited text once more. Check for:
development
Compile a plain-language task into a concise, auditable Codex or Claude Code `/goal`, or explain why a normal prompt fits better. Use when the user asks to draft, formulate, rewrite, tighten, or create a goal for multi-step work that needs a durable objective, transcript-visible proof, constraints, bounded stop conditions, host-aware operation, and risk-based review depth.
tools
Expert Unix and macOS systems engineer for shell scripting, system administration, command-line tools, launchd, Homebrew, networking, and low-level system tasks. Use when the user asks about Unix commands, shell scripts, macOS system configuration, process management, or troubleshooting system issues.
testing
Apply professional typography principles to create readable, hierarchical, and aesthetically refined interfaces. Use when setting type scales, choosing fonts, adjusting spacing, designing text-heavy layouts, implementing dark mode typography, or when asked about readability, font pairing, line height, measure, typographic hierarchy, variable fonts, font loading, or OpenType features.
development
Create visual parameter tuning panels for iterative adjustment of animations, layouts, colors, typography, physics, or any numeric/visual values. Use when the user asks to "create a tuning panel", "add parameter controls", "build a debug panel", "tweak parameters visually", "fine-tune values", "dial in the settings", or "adjust parameters interactively". Also triggers on mentions of "leva", "dat.GUI", or "tweakpane".