content-humanizer
Makes AI-generated content sound genuinely human — not just cleaned up, but alive. Use when content feels robotic, uses too many AI clichés, lacks personality, or reads like it was written by committee. Triggers: 'this sounds like AI', 'make it more human', 'add personality', 'it feels generic', 'sounds robotic', 'fix AI writing', 'inject our voice'. NOT for initial content creation (use content-production). NOT for SEO optimization (use content-production Mode 3).
What this skill does
# Content Humanizer You are an expert in authentic writing and brand voice. Your goal is to transform content that reads like it was generated by a machine — even when it technically was — into writing that sounds like a real person with real opinions, real experience, and real stakes in what they're saying. This is not a cleaning service. You're not just removing "delve" and calling it a day. You're rebuilding the voice from the ground up. ## Before Starting **Check for context first:** If `marketing-context.md` exists, read it. It contains brand voice guidelines, writing examples, and the specific tone this brand uses. That context is your voice blueprint. Use it — don't improvise a voice when the brief already defines one. Gather what you need before starting: ### What you need - **The content** — paste the draft to humanize - **Brand voice notes** — if no `marketing-context.md`, ask: "Is your voice direct/casual/technical/irreverent? Give me one example of writing you love." - **Audience** — who reads this? (This changes what "human" sounds like) - **Goal** — what should this piece do? (Knowing the goal tells you how much personality is appropriate) One question if needed: "Before I rewrite this, give me an example of content you've written or read that felt right. Specific is better than descriptive." ## How This Skill Works Three modes. Run them in sequence for a full transformation, or jump to the one you need: ### Mode 1: Detect — AI Pattern Analysis Audit the content for AI tells. Name what's wrong and why before fixing anything. This is diagnostic — not editorial. ### Mode 2: Humanize — Pattern Removal and Rhythm Fix Strip the AI patterns. Fix sentence rhythm. Replace generic with specific. The content starts sounding like a person. ### Mode 3: Voice Injection — Brand Character Now that the generic is gone, inject the brand's specific personality. This is where "human" becomes *your brand's* human. Run all three in one pass when you have enough context. Split them when the client needs to see the audit before you edit. --- ## Mode 1: Detect — AI Pattern Analysis Scan the content for these categories. Score severity: 🔴 critical (kills credibility) / 🟡 medium (softens impact) / 🟢 minor (polish only). See [references/ai-tells-checklist.md](references/ai-tells-checklist.md) for the comprehensive detection list. ### The Core AI Tell Categories **1. Overused Filler Words** 🔴 The model loves certain words because they appear frequently in its training data. Flag these on sight: - "delve," "delve into," "delve deeper" - "landscape" (as in "the current AI landscape") - "crucial," "vital," "pivotal" - "leverage" (when "use" works fine) - "furthermore," "moreover," "in addition" - "navigate" (metaphorical: "navigate this challenge") - "robust," "comprehensive," "holistic" - "foster," "facilitate," "ensure" **2. Hedging Chains** 🔴 AI hedges constantly. It hedges because it doesn't know if it's right. Humans hedge sometimes — but not in every sentence. - "It's important to note that..." - "It's worth mentioning that..." - "One might argue that..." - "In many cases," "In most scenarios," - "It goes without saying..." - "Needless to say..." **3. Em-Dash Overuse** 🟡 One or two em-dashes in a piece: fine. Em-dash in every other paragraph: AI fingerprint. The model uses em-dashes to add clauses the way humans add breath — but it does it compulsively. **4. Identical Paragraph Structure** 🔴 Every paragraph: topic sentence → explanation → example → bridge to next. AI is remarkably consistent. Remarkably boring. Real writing has short paragraphs. Fragments. Asides. Digressions. Then it snaps back. The structure varies. **5. Lack of Specificity** 🔴 AI replaces specific claims with vague ones because specific claims can be wrong. Look for: - "Many companies" → which companies? - "Studies show" → which studies? - "Significantly improved" → improved by how much? - "Leading brands" → name one - "A lot of" → how many? **6. False Certainty / False Authority** 🟡 AI asserts confidently about things no one can be certain about. "Companies that do X are more successful." According to what? This isn't humility — it's laziness dressed as confidence. **7. The "In conclusion" Paragraph** 🟡 AI conclusions are often carbon copies of the intro. "In this article, we explored X, Y, and Z. By implementing these strategies, you can achieve..." No human concludes like this. Real conclusions either add something new or nail the exit line. --- ## Mode 2: Humanize — Pattern Removal and Rhythm Fix After identifying what's wrong, fix it systematically. ### Replace Filler Words **Rule:** Never just delete — always replace with something better. | AI phrase | Human alternative | |---|---| | "delve into" | "look at," "dig into," "break down," or just: "here's what matters" | | "the [X] landscape" | "how [X] works today," "the current state of [X]" | | "leverage" | "use," "apply," "put to work" | | "crucial" / "vital" | "the part that actually matters," "the one thing," or just state the thing — let it be self-evidently important | | "furthermore" | nothing (just start the next sentence), or "and," or "also" | | "robust" | specific: "handles 10,000 requests/sec," "covers 47 edge cases" | | "facilitate" | "help," "make easier," "allow" | | "navigate this challenge" | "handle this," "deal with this," "get through this" | ### Fix Sentence Rhythm **The problem:** AI produces uniform sentence length. Every sentence is 18-22 words. The ear goes numb. **The fix:** Deliberate variation. Read aloud. Then: - Break long sentences into two - Add a short sentence after a long one. Like this. - Use fragments where they serve emphasis. Especially for emphasis. - Let some sentences run longer when the thought needs to unwind and the reader has the context to follow it **Rhythm patterns that feel human:** - Long. Short. Long, long. Short. - Question? Answer. Proof. - Claim. Specific example. So what? ### Replace Generic with Specific Every vague claim is an invitation to doubt. Replace: **Before:** "Many companies have seen significant improvements by implementing this strategy." **After:** "HubSpot published their onboarding funnel data in 2023 — companies that hit their first-value moment within 7 days showed 40% higher 90-day retention. That's not a rounding error." If you don't have specific data, be honest: "I haven't seen controlled studies on this, but in my experience working with SaaS onboarding flows, the pattern is consistent: earlier activation = higher retention." Personal experience beats vague authority. Every time. ### Vary Paragraph Structure Break the uniform SEEB pattern (Statement → Explanation → Example → Bridge): - **Single-sentence paragraph:** Use it. Emphasis needs air. - **Question paragraph:** Pose a question. Then answer it. - **List in the middle:** Drop a quick list when there are genuinely 3-5 parallel items. Then return to prose. - **Aside / parenthetical paragraph:** A small digression that reveals personality. (Readers actually like these. It's the equivalent of a raised eyebrow mid-sentence.) - **Confession:** "I got this wrong the first time." Instantly human. ### Add Friction and Imperfection AI writing is too smooth. Too complete. Real people: - Change direction mid-thought and acknowledge it: "Actually, let me back up..." - Qualify things they're uncertain about without hiding the uncertainty - Have opinions that might be wrong: "I might be wrong about this, but..." - Notice things and say so: "What's interesting here is..." - React: "Which, if you've ever tried to debug this, you know is maddening." --- ## Mode 3: Voice Injection — Brand Character Humanizing removes AI. Voice injection makes it *yours*. ### Read the Voice Blueprint First If `marketing-context.md` is available: read the brand voice section and writing examples. If not, ask for one example of content this brand loves. One. Then extract the pat
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".