Writer
Fix AI writing patterns that create repetitive and robotic content
Iván
@ivangdavila
What This Skill Does
Detects and fixes common AI writing patterns that make text repetitive, robotic, or vague. Provides specific rules for paragraph openers, sentence rhythm, vague claims, list overuse, parallel structure, transition words, voice drift, word economy, and nominalizations.
Replaces manual line-by-line editing of AI-generated text by automating the detection of nine common robotic writing patterns with concrete fix rules.
When to Use It
- Fix paragraph openers that start with 'This', 'The', or 'It' three times in a row
- Replace vague claims like 'significant growth' with specific numbers or evidence
- Break up monotonous sentence rhythm by mixing short and long sentences
- Convert nominalizations like 'implementation of' into active verbs like 'implement'
- Remove transition word crutches such as 'Furthermore' and 'Moreover' from a draft
- Check for voice drift by marking tone every 200 words in a long document
Install
$ openclaw skills install @ivangdavila/writerAI Writing Pattern Fixes
Paragraph Opener Trap
Scan first word of each paragraph - if 3+ start with "This/The/It" = robotic Vary with: "Meanwhile", "Consider", "Beyond that", action verbs, specific nouns Lead with action: "Marketing increased" not "The marketing team increased"
Rhythm Monotony Trap
Avoid same sentence length patterns - mix 5-word punches with 20-word flows Use strategic fragments. For emphasis. For pace breaks. Read aloud test: monotone rhythm = boring
Vague Claim Trap
Replace adjectives with numbers: "significant growth" → "40% growth" Swap evaluations for evidence: "impressive results" → "cut response time from 3s to 300ms" Delete weasel words: somewhat, fairly, quite, rather, slightly
List Overuse Trap
Use prose when explaining relationships or building arguments Use bullets only for instructions, features, options Flow test: if bullets feel choppy, try connected sentences
Parallel Structure Breaks
Match verb forms: "hiking, swimming, reading" not "hiking, swimming, to read" Match sentence patterns: "codes fast, debugs thoroughly, ships daily" Keep same grammatical structure in lists
Transition Word Crutches
Avoid: Furthermore, Moreover, Additionally, In conclusion Use echo technique: end paragraph with concept X, start next with concept X Pick up last idea and expand naturally
Voice Drift in Long Documents
Tone drift check: mark every 200 words - same person speaking? Pick 3-5 key phrases and use consistently throughout Don't switch from beginner-friendly to expert jargon mid-document
Word Economy Traps
Cut phrases: "in order to" → "to", "due to the fact that" → "because" One verb wins: "make improvement" → "improve", "conduct investigation" → "investigate" 80% rule: can you say it in 80% of words? Do it.
Nominalization Trap
Use verbs not nouns: "implementation of" → "implement" Action over abstraction: "decision-making process" → "decide" Zombie noun test: -tion, -ment, -ness endings often hide better verbs
Top skills in this category
Humanizer
@biostartechnologyRemove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Free Ride - Unlimited free AI
@shaivpidadiManages free AI models from OpenRouter for OpenClaw. Automatically ranks models by quality, configures fallbacks for rate-limit handling, and updates opencla...
Elite Longterm Memory
@nextfrontierbuildsUltimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vibe-coding ready.
Playwright (Automation + MCP + Scraper)
@ivangdavilaAutomates, tests, and debugs browsers with Playwright: locators, auto-waiting, traces, CI runs, and MCP browser control. Use when a test is flaky, times out, or fails only in CI or headless; when a locator matches multiple elements or the wrong one (strict mode violation); when clicks need force, waits become sleeps, or networkidle never settles; for storageState and login setup, request mocking and HAR replay, uploads and downloads, iframes and shadow DOM, popups and dialogs, screenshot diffs that change per machine, trace and report artifacts, sharding a slow suite, device and permission emulation, accessibility checks, driving a real browser through Playwright MCP, extracting data from JS-rendered pages, or porting a Cypress, Puppeteer, or Selenium suite to Playwright. Not for maintaining an existing Cypress or Puppeteer suite (cypress, puppeteer) or for work a plain HTTP request answers (http).
Model Usage
@steipeteUse CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.