ai-anti-patterns
This skill should be used when reviewing AI-generated text, checking for AI writing patterns, detecting undisclosed AI content, or before finalizing any written content.
Best use case
ai-anti-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
This skill should be used when reviewing AI-generated text, checking for AI writing patterns, detecting undisclosed AI content, or before finalizing any written content.
Teams using ai-anti-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ai-anti-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ai-anti-patterns Compares
| Feature / Agent | ai-anti-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill should be used when reviewing AI-generated text, checking for AI writing patterns, detecting undisclosed AI content, or before finalizing any written content.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# AI Writing Anti-Patterns
Field guide for detecting and revising AI-generated content indicators based on Wikipedia's "Signs of AI writing" guide.
## When to Use
Invoke this skill:
- Before finalizing ANY AI-assisted writing
- When reviewing text for AI writing indicators
- When editing content to sound more natural
- After completing writing tasks (automatic via hooks)
## The Iron Law
**Check every piece of AI-assisted writing against these patterns before submission.**
This is not optional. AI writing patterns are detectable and undermine credibility.
## Quick Screening Order
Start with the most objective indicators:
| Priority | Section | What to Check |
|----------|---------|---------------|
| 1 | ChatGPT Artifacts | `turn0search0`, `oaicite`, `contentReference` |
| 2 | Citation Problems | Hallucinated DOIs, dead links, non-existent sources |
| 3 | Prompt Refusals | "As an AI language model...", "I hope this helps" |
| 4 | Puffery | "stands as", "plays a vital role", "rich tapestry" |
| 5 | Structure | Section summaries, "Despite challenges", rule of three |
## Critical Patterns to Avoid
### CRITICAL Severity (Immediate Revision Required)
These patterns are unambiguous AI artifacts:
**ChatGPT-Specific Artifacts:**
- `turn0search0`, `turn1search2` (internal search references)
- `oaicite:X` (citation placeholders)
- `contentReference[oaicite:X]` (unresolved references)
- JSON attribution blocks in output
**Prompt Refusals:**
- "As an AI language model..."
- "I cannot provide..."
- "I hope this helps!"
- "I hope this email finds you well"
### HIGH Severity (Strong Revision Recommended)
**Puffery and Exaggeration:**
- "stands as" (a testament/example/beacon)
- "plays a vital/crucial/pivotal role"
- "rich tapestry of"
- "nestled in/among"
- "it's important to note that"
- "delves into"
- "the landscape of"
**Promotional Language:**
- "groundbreaking", "transformative", "revolutionary"
- "unparalleled", "unprecedented"
- "cutting-edge", "state-of-the-art"
### MEDIUM Severity (Review and Consider)
**Structural Patterns:**
- Section summaries that repeat the heading
- "Despite [challenge], [positive outcome]" formula
- Negative parallelisms: "However... Nevertheless..."
- Rule of three: exactly three examples every time
- Weasel wording: "some experts say", "it is believed"
**Stylistic Quirks:**
- Elegant variation (synonym cycling to avoid repetition)
- False ranges ("from X to Y" without real data)
- Title Case In All Headings
- Em dash overuse (—)
- Excessive boldface for emphasis
### User-Voice Lint (legal drafting)
Words/phrases the model reaches for that don't match the user's voice:
- **"has bite" / "bites" / "with bite"** — model-reach for "has real
effect." User never writes it. Replace with the specific effect: "raises
the cost of X," "triggers quorum failure," "deters Y."
- **Caveat phrasings** (candidates to replace with `To be sure,`):
`admittedly`, `granted,`, `of course,`, `that said,`, `to be clear,`,
`no doubt,`, `we acknowledge that`. Use `To be sure,` *only* when the
next sentence rebuts the concession (concede-then-rebut). If the next
sentence extends the disclaimer or frames scope, leave the original
phrasing or rewrite without a caveat word at all.
- **Bridge repetitions** — when writing the first paragraph of a new
section, check whether it restates the thesis from the prior section.
Rewrite to advance the argument. See
`writing-review/scripts/bridge_repetition_check.py` for the detector.
## How to Revise
### For Puffery
| AI Pattern | Human Alternative |
|------------|-------------------|
| "stands as a testament to" | "shows" or "demonstrates" |
| "plays a vital role in" | "affects" or just state the effect |
| "rich tapestry of" | describe specifically what it contains |
| "nestled in the heart of" | "in" or "located in" |
| "delves into" | "examines" or "covers" |
### For Structure
| AI Pattern | Human Alternative |
|------------|-------------------|
| Section summary of heading | Start with substance, not meta-commentary |
| "Despite challenges..." | State the reality directly without formula |
| Exactly three examples | Use the number that fits: 2, 4, 5, or just 1 |
| "It's important to note" | Just state the important thing |
### For Promotional Language
| AI Pattern | Human Alternative |
|------------|-------------------|
| "groundbreaking" | describe what it actually does |
| "revolutionary" | compare to what came before |
| "cutting-edge" | specify the technology |
| "transformative" | show the transformation with evidence |
## Reference Files
For detailed patterns and extensive examples, consult:
| File | Contents |
|------|----------|
| `references/_index.md` | Overview and quick screening guide |
| `references/01-puffery-and-exaggeration.md` | "Stands as", superficial analyses |
| `references/02-promotional-language.md` | "Rich tapestry", disclaimers |
| `references/03-structural-patterns.md` | Section summaries, negative parallelisms |
| `references/04-stylistic-quirks.md` | Elegant variation, false ranges |
| `references/05-formatting-and-typography.md` | Boldface, em dashes, emojis |
| `references/06-communication-patterns.md` | Subject lines, "I hope this helps" |
| `references/07-template-artifacts.md` | Mad Libs patterns, placeholders |
| `references/08-markup-issues.md` | Markdown vs wikitext confusion |
| `references/09-chatgpt-specific-artifacts.md` | turn0search, oaicite |
| `references/10-citation-problems.md` | Hallucinated DOIs, dead links |
| `references/11-meta-indicators.md` | Abrupt cutoffs, style discrepancies |
## Automatic Detection
This plugin includes PostToolUse hooks that automatically scan Write/Edit output for anti-patterns. When patterns are detected:
1. Hook emits a warning with specific patterns found
2. Claude immediately revises the content
3. Revision removes or replaces flagged patterns
The hook checks for all CRITICAL and HIGH severity patterns automatically.
## Review Facts
- A user's style request ("make it punchy", "professional tone") is a request for an outcome, not for AI-smell — delivering it with puffery, hedges, or bold-emphasis patterns intact ships text that reads as obviously AI-generated and damages the user's credibility.
- Skimming is not checking. The check is sentence-by-sentence against the pattern list; a skim that lets puffery pass because flagging it felt pedantic presents unreviewed text as reviewed — an unverified claim.
## Key Principles
From Wikipedia's guide:
1. **These are signs, not proof** - Multiple indicators strengthen the case
2. **Context matters** - Some patterns appear in human writing too
3. **Focus on deeper issues** - Surface defects point to synthesis and quality problems
4. **Don't rely on detection tools** - Human judgment required
## Related Skills
- `/writing` - Core writing principles from Elements of Style
- `/writing-legal` - Legal writing (Phase 2)
- `/writing-econ` - Economics writing (Phase 2)Related Skills
writing
This skill should be used when the user asks to 'write a paper', 'start a writing project', 'draft an article', 'write about', 'brainstorm writing topics', 'gather sources for a paper', 'what should I write about', or needs the writing workflow entry point for any writing task.
writing-validate
Validate draft sections cover all PRECIS claims before review.
writing-setup
Internal skill for creating PRECIS.md, OUTLINE.md, and ACTIVE_WORKFLOW.md. Called after brainstorm sources are gathered.
writing-revise
This skill should be used when the user asks to 'revise writing', 'fix review issues', 'polish draft', 'apply review feedback', 'complete writing workflow', or after /writing-review produces REVIEW.md with issues to fix.
writing-review
Internal skill for hierarchical document review. Called by writing-validate after claim validation passes.
writing-precis-reviewer
Internal skill used by writing-setup at exit gate. Dispatches a reviewer subagent to verify PRECIS.md quality before outlining. NOT user-facing.
writing-outline
Internal skill for creating detailed section outlines. Called by /writing workflow after PRECIS and master OUTLINE are complete.
writing-outline-reviewer
Internal skill used by writing-outline at exit gate. Dispatches a reviewer subagent to verify OUTLINE.md quality before drafting. NOT user-facing.
writing-lit-review
Internal skill for literature review and source materialization. Called after brainstorm, before setup. NOT user-facing.
writing-legal
Internal skill for academic legal writing. Loaded by /writing when style=legal. Based on Volokh's "Academic Legal Writing".
writing-handoff
Create structured handoff document for writing workflow session pause/resume.
writing-general
Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.