anti-ai-writing
Transform AI-assisted drafts into authentic, human-sounding content. This skill provides patterns to detect and eliminate AI tells, frameworks for natural writing, and techniques for creating prose that reads as genuinely human. Use when reviewing any AI-generated content or when writing content that must not appear AI-assisted.
What this skill does
# Anti-AI Writing Engine Transform any content into authentic, human-sounding prose by eliminating AI patterns and applying proven writing fundamentals. ## Purpose This skill serves as the core humanization engine for all written content. It detects and eliminates patterns that signal AI involvement while teaching the principles of natural, engaging writing. **Core Philosophy:** The best writing is invisible. Readers should feel like they're reading a real person's thoughts - not processed, filtered, or generated content. ## When to Use This Skill - Reviewing and humanizing AI-generated drafts - Writing content that must not appear AI-assisted - Editing any prose for authenticity and impact - Training yourself to avoid AI-like patterns - Quality-checking content before publication **Pairs well with:** Voice style skills (voice-pirate-wires, voice-analytical, etc.) for writing in a specific author's style. --- ## Universal Writing Fundamentals Master these principles first, then layer on specific style choices. ### 1. Energy Transfer **The best writing is a transfer of energy from writer to reader.** - Write conversations, not speeches - Speak WITH your audience, not AT them - Remove corporate jargon, academic language, and buzzwords **Example:** - ❌ "The implementation of our innovative frameworks has demonstrated significant positive outcomes in terms of engagement metrics." - ✅ "Our new approach works. People are paying attention." The second version transfers energy. Readers feel conviction, not formality. ### 2. Conciseness is King **Every word must earn its place.** **Process:** 1. Write your first draft freely 2. Read it aloud 3. Delete anything that: - Repeats an idea already stated - Softens your main point - Sounds formal instead of conversational - Takes more words than necessary **Example:** - ❌ "Our approach incorporates multiple methodologies designed to accommodate diverse requirements and development patterns." - ✅ "We adapt to how you work." ### 3. The SUCKS Framework Before writing anything, answer these questions: **S - Specific** - Write for ONE person, not a crowd - Know their struggles, goals, language - If you write for everyone, you write for no one **U - Unique & Useful** - Does this change how your reader thinks, feels, or acts? - Unique: they haven't seen this perspective before - Useful: they can actually apply this **C - Clear, Curious, Conversational** - Clear: Main idea is unmissable - Curious: Questions that make readers think - Conversational: Reads like talking to a friend **K - Kept Simple & Structured** - Simple ideas, simple words - Clear beginning, middle, end **S - Sticky** - Memorable phrases they'll repeat - Ideas that lodge in memory **Application checklist:** - [ ] Who is my ONE reader? - [ ] What will they think, feel, or do differently? - [ ] Could a 12-year-old understand the main point? - [ ] Does this flow like a conversation? ### 4. Be Undeniable **Transform vague claims into concrete specifics.** - ❌ "How to boost your results by at least 87% in just one month." - ✅ "This year, I helped 13 clients boost their results by 87%-256% in just one month. Here's how:" **Pattern:** Replace vague language with data, examples, specifics, or personal experience. ### 5. Craft Sticky Sentences Use these techniques to create memorable statements: **Alliteration** - Same starting sounds - "Specificity is the secret" - "The best jobs are neither decreed nor degreed" **Symmetry** - Parallel structure - "Read for awareness. Write for understanding." - "It's not 10,000 hours. It's 10,000 iterations." **Contrast** - Opposing ideas - "To be everywhere is to be nowhere." - "Be clear, not clever. Concise, not complex." **Rhyme** - Similar ending sounds - "Tell a story or lose your glory" **Rhythm** - Pleasing cadence - "When you can't wait to share it, they can't help but read it" **For maximum stickiness, combine techniques:** - "Anger prepares us to fight. Fear prepares us to flee." (Symmetry + Alliteration) See `references/sticky-sentences.md` for expanded examples. --- ## Forbidden Patterns (AI Tells) These patterns consistently signal AI involvement. Eliminate them aggressively. ### The Correlative Construction (Most Common AI Tell) This is the #1 pattern to avoid: - ❌ "X aren't just Y - they're Z" - ❌ "X isn't just about Y, it's about Z" - ❌ "Teachers aren't just instructors - they're mentors" **Why it's bad:** This is the default structure AI models produce. Every AI writing sample uses this. **Better alternatives:** - ✅ "Teachers mentor students" - ✅ "X accomplishes both Y and Z" - ✅ State the point directly ### Forbidden Constructions - ❌ "It's not about X, it's about Y" - ❌ "The truth is..." / "The reality is..." - ❌ "Let that sink in" - ❌ "Now more than ever..." **Better:** State your point directly without setup. ### Forbidden Rhetorical Flourishes - ❌ "The best part? ..." - ❌ "The secret? ..." - ❌ "Sounds impossible? It's not." - ❌ "What if I told you..." - ❌ "Here's the thing..." - ❌ "Let's be honest..." - ❌ "At the end of the day..." ### Forbidden Staccato Phrasing Do not use faux-dramatic sentence fragments: - ❌ "No fluff. No filler. Just results." - ❌ "Big ideas. Small words. Maximum impact." - ❌ "Simple. Clear. Effective." - ❌ "Stop guessing. Start winning." ### Forbidden Openers - ❌ "In the ever-evolving world of..." - ❌ "In today's fast-paced..." - ❌ "Gone are the days when..." - ❌ "This underscores..." - ❌ "In an era where..." ### Formatting Restrictions - Do not use boldface for emphasis in body text - Do not use emojis unless explicitly requested - Do not add summaries like "In conclusion" or "In summary" - Do not rely on bullet points unless explicitly asked ### Dash Usage Use regular hyphens with spaces for parenthetical breaks - like this - not em dashes (—) or en dashes (–). - ✅ "Education is changing - and parents are noticing" - ❌ "Education is changing—and parents are noticing" --- ## Anti-AI Pattern Detection Beyond forbidden syntax, these patterns consistently signal AI involvement: ### 1. Overuse of "Just" **Problem:** AI uses "just" constantly as a softener. - ❌ "We just need to understand that it's just about learning, and we just have to focus on what matters." - ✅ "It's about learning. Focus on what matters." **When "just" is acceptable:** "just one question," "just in case," "just started" **When to remove it:** Middle of sentences as a softener, more than once per paragraph ### 2. Overuse of "Actually" **Problem:** AI uses "actually" to sound like it's adding nuance. - ❌ "It's actually about teaching, but actually about community, and students actually need both." - ✅ "It's about teaching. It's also about community. Students need both." **When acceptable:** Correcting a previous misunderstanding **Limit:** Once per 500 words maximum ### 3. Hedging Language AI loves hedge words because they make uncertain claims safer. But they make writing weak. **Common hedges to eliminate:** - ❌ "This might help you" → ✅ "This will help you" - ❌ "Some people say..." → ✅ "I've found that..." - ❌ "It could be argued that..." → ✅ "It's true that..." - ❌ "Perhaps we should consider..." → ✅ "We should..." - ❌ "One could say..." → ✅ "This is true because..." **Test:** If you find "might," "could," "perhaps," "possibly," "maybe," "somewhat," or "it seems like," ask: Do I actually believe this? If yes, remove the hedge. ### 4. Passive Voice **Problem:** AI defaults to passive voice because it's safer. - ❌ "It was determined that improvements were needed" - ✅ "We need to improve" - ❌ "It has been shown that users benefit from..." - ✅ "Users benefit from..." **Test:** If you can't identify who's doing the action, it's passive. Rewrite with a subject. ### 5. Corporate Jargon These signal over-processing: - ❌ "Leveraging synergies across stakeholder ecosystems" - ✅ "Getting different people talking to each other"
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.