no-ai-slop

name	no-ai-slop
description	Prose cleanup for filler, hype, vague claims, repetition, detection tells, or uncited specifics. Not for Markdown architecture or archival work.

No-Slop Writing

Boundary

Use this skill for wording quality and docs for document structure. Archival work is outside this skill. pi/AGENTS.md owns implementation strategy.

Core Principle

Keep only language that is specific, supported, and useful. Prefer plain words and direct statements, but preserve the author's meaning, voice, terminology, and level of certainty.

Practical Steps

• Cut throat-clearing, repeated conclusions, and any word that can be removed without losing meaning.
• Prefer a familiar, precise word to jargon, stock phrases, stale metaphors, or inflated wording.
• Use concrete verbs instead of abstract noun phrases.
• Name the actor when responsibility matters. Use passive voice when the actor is unknown or the action or recipient deserves emphasis.
• Replace hype and unsupported superlatives with evidence, or delete the claim.
• Vary sentence shape and length around the content rather than imposing a mechanical style.
• Keep citations and qualifiers that prevent overclaiming. If a claim needs missing support, mark it or remove it.
• Break a style preference rather than distort meaning, voice, or audience expectations.

Conditional Reference

For comments, messages, release notes, procedures, or other code-adjacent technical prose, read Technical prose. Do not load it for general prose cleanup.

Anti-Patterns

Anti-pattern	Fix
"Comprehensive, robust, seamless"	Name the actual capability
Vague benefit claims	Add evidence or delete
Repeated intro/body/conclusion rhythm	Organize around the content
Automatic active-voice or sentence-length rewrites	Change only what improves meaning for this audience
Overconfident certainty	Match the evidence