Agent Skills › poteto/noodle › unslop

unslop

GitHub

移除文本中的AI写作痕迹,优化为自然人类语气。适用于文档、博客等非代码内容,通过识别并修正特定词汇和句式模式,提升内容的真实感与可读性。

.agents/skills/unslop/SKILL.md poteto/noodle

Trigger Scenarios

unslop humanize make this sound human clean up this writing edit for voice de-AI this text

Install

npx skills add poteto/noodle --skill unslop -g -y
More Options

Non-standard path

npx skills add https://github.com/poteto/noodle/tree/main/.agents/skills/unslop -g -y

Use without installing

npx skills use poteto/noodle@unslop

指定 Agent (Claude Code)

npx skills add poteto/noodle --skill unslop -a claude-code -g -y

安装 repo 全部 skill

npx skills add poteto/noodle --all -g -y

预览 repo 内 skill

npx skills add poteto/noodle --list

SKILL.md

Frontmatter
{
    "name": "unslop",
    "description": "Remove AI writing patterns from prose. Use for docs, READMEs, blog posts, any non-code text that should sound human. Triggers: \"unslop\", \"humanize\", \"make this sound human\", \"clean up this writing\", \"edit for voice\", \"de-AI this text\"."
}

Unslop

Edit text to remove AI patterns and add human voice.

Process

  1. Scan for the patterns below
  2. Rewrite — preserve meaning, match intended tone
  3. Add soul (see next section)
  4. Self-audit: "What makes this obviously AI generated?" Fix remaining tells.

Adding soul

Removing patterns is half the job. Sterile, voiceless writing is just as obvious.

  • Have opinions. React to facts instead of neutrally listing pros and cons.
  • Vary rhythm. Short sentences. Then longer ones that take their time. Mix it up.
  • Acknowledge complexity. "Impressive but also kind of unsettling" beats "impressive."
  • Use "I" when it fits. First person isn't unprofessional.
  • Let some mess in. Perfect structure feels algorithmic.
  • Be specific. Not "this is concerning" but "there's something unsettling about agents churning away at 3am."

Patterns to detect and fix

Content

  1. Significance inflation — "pivotal moment", "testament to", "evolving landscape", "setting the stage for", "indelible mark", "deeply rooted". Cut puffery, state what happened.
  2. Notability name-dropping — listing media outlets without context. Pick one, say what was said.
  3. Superficial -ing phrases — "highlighting...", "ensuring...", "reflecting...", "showcasing...", "fostering...". Delete or expand with real sources.
  4. Promotional language — "nestled", "vibrant", "breathtaking", "groundbreaking", "renowned", "stunning", "must-visit". Use neutral descriptions.
  5. Vague attributions — "Experts believe", "Industry reports suggest", "Some critics argue". Name the source or delete.
  6. Formulaic challenges — "Despite challenges... continues to thrive." Replace with specific facts.

Language

  1. AI vocabulary — Additionally, crucial, delve, enduring, enhance, fostering, garner, interplay, intricate, landscape (abstract), pivotal, showcase, tapestry (abstract), testament, underscore, vibrant. Replace with plain words.
  2. Copula avoidance — "serves as", "stands as", "boasts", "features". Just say "is" or "has".
  3. Negative parallelisms — "It's not just X, it's Y." State the point directly.
  4. Rule of three — forcing ideas into groups of three. Use the natural number.
  5. Synonym cycling — protagonist/main character/central figure/hero in one paragraph. Pick one, repeat it.
  6. False ranges — "from X to Y" where X and Y aren't on a meaningful scale. List topics directly.

Style

  1. Em dash overuse — avoid em dashes entirely. Use periods, commas, or parentheses. Em dashes are an AI tell.
  2. Colon overuse — colons are fine before a list or example. Not as mid-sentence connectors. "If you're coming from traditional automation: instead of registering event handlers, you describe conditions" adds nothing with the colon. Rewrite to let the point stand on its own without comparison framing. "Describing when the scheduler should fire works best as plain English." Same meaning, no crutch punctuation.
  3. Boldface overuse — don't bold every proper noun or acronym.
  4. Inline-header lists — "Performance: Performance improved..." Convert to prose.
  5. Title case headings — use sentence case.
  6. Decorative emojis — remove from headings and bullets.
  7. Curly quotes — replace with straight quotes.

Communication artifacts

  1. Chatbot phrases — "I hope this helps!", "Let me know if...", "Of course!", "Certainly!" Remove.
  2. Cutoff disclaimers — "While specific details are limited..." Find sources or remove.
  3. Sycophantic tone — "Great question! You're absolutely right!" Respond directly.

Filler

  1. Filler phrases — "In order to" → "To". "Due to the fact that" → "Because". "It is important to note that" → delete.
  2. Excessive hedging — "could potentially possibly be argued that it might" → "may".
  3. Generic conclusions — "The future looks bright." State specific plans or facts.

Version History

  • 82d2921 Current 2026-11-19 21:09

Same Skill Collection

.agents/skills/adversarial-review/SKILL.md
.agents/skills/ast-grep/SKILL.md
.agents/skills/brain/SKILL.md
.agents/skills/codex/SKILL.md
.agents/skills/commit/SKILL.md
.agents/skills/debugging/SKILL.md
.agents/skills/execute/SKILL.md
.agents/skills/find-skills/SKILL.md
.agents/skills/frontend-design/SKILL.md
.agents/skills/go-best-practices/SKILL.md
.agents/skills/interaction-design/SKILL.md
.agents/skills/make-interfaces-feel-better/SKILL.md
.agents/skills/meditate/SKILL.md
.agents/skills/noodle/SKILL.md
.agents/skills/oops/SKILL.md
.agents/skills/plan/SKILL.md
.agents/skills/quality/SKILL.md
.agents/skills/react-best-practices/SKILL.md
.agents/skills/refine/SKILL.md
.agents/skills/reflect/SKILL.md
.agents/skills/review/SKILL.md
.agents/skills/ruminate/SKILL.md
.agents/skills/schedule/SKILL.md
.agents/skills/skill-creator/SKILL.md
.agents/skills/testing/SKILL.md
.agents/skills/todo/SKILL.md
.agents/skills/worktree/SKILL.md
examples/minimal/.agents/skills/execute/SKILL.md
examples/minimal/.agents/skills/schedule/SKILL.md
examples/multi-skill/.agents/skills/execute/SKILL.md
examples/multi-skill/.agents/skills/schedule/SKILL.md
skills/skill-creator/SKILL.md
.agents/skills/ts-best-practices/SKILL.md
examples/multi-skill/.agents/skills/deploy/SKILL.md
examples/multi-skill/.agents/skills/test/SKILL.md

Metadata

Files
0
Version
82d2921
Hash
1ae5b161
Indexed
2026-11-19 21:09

Accueil - Wiki
Copyright © 2011-2026 iteam. Current version is 2.156.0. UTC+08:00, 2026-11-20 03:00
浙ICP备14020137号-1