Humanizer Agent Skill

repository·main·Indexed 12 days ago

https://github.com/blader/humanizer

A portable agent skill designed to remove signs of AI-generated writing from text. Based on WikiProject AI Cleanup patterns, it transforms formulaic AI prose into natural, human-sounding text by eliminating overused AI vocabulary, promotional language, and mechanical formatting without fabricating new facts. It supports voice calibration via writing samples and can be installed via the skills CLI, as a Claude Code plugin, or manually via SKILL.md.

Tokens
4.3K
Snippets
9
Records
17
Agent score
49%

What's inside Humanizer

  1. Apply Personality and Soul to writing

    main

    To avoid sterile, voiceless writing, you can inject "Personality and Soul" into the text. However, this should only be applied when the content and the author's voice call for it (e.g., blog posts, essays, opinion pieces, or personal writing).

    When to use it:

    • Blog posts
    • Essays
    • Opinion pieces
    • Personal writing

    How to apply it:

    • Avoid uniform sentence structures and perfect organization.
    • Allow for uncertainty, mixed feelings, humor, and asides.
    • Use uneven rhythms.

    When NOT to use it:

    • Encyclopedic text
    • Technical documentation
    • Legal text
    • Reference material

    Note: For neutral/technical text, a plain and neutral voice is the correct human voice. Never add factual claims to create personality.

  2. The Humanizer workflow process

    main

    To ensure high-quality, human-like prose, Humanizer follows a specific four-step internal loop:

    1. Pattern Identification: Read the input to identify instances of AI writing patterns (e.g., undue emphasis on significance, vague attributions, or specific linguistic tells).
    2. Drafting: Create a draft rewrite that varies sentence length, uses specific details, prefers simple constructions (like is/are/has), and maintains the appropriate register.
    3. Self-Audit: The tool must answer two critical questions to prevent errors:
      • "What makes the below so obviously AI generated?"
      • "Does the rewrite state any fact, name, number, date, or citation that isn't in the source?" (Note: Fabricating facts is considered a defect).
    4. Finalization: Produce a final rewrite that addresses the audit findings and removes all em or en dashes.
  3. Signs of human writing to preserve

    main

    To maintain the 'soul' of a piece, Humanizer is designed to recognize and preserve these human signals:

    • Specific, unusual detail: Hard-to-fabricate specifics like real addresses, weird quotes, or highly particular anecdotes.
    • Unresolved tension: Mixed feelings or non-linear thoughts (e.g., "I think this is good, but it bothers me...").
    • Era-bound references: Slang, memes, or cultural in-jokes that map to specific timeframes.
    • Sentence Variety: A natural alternation between short and long sentences (AI tends toward a mid-length cadence).
    • Self-corrections: Genuine asides or parentheticals where the writer interrupts themselves (e.g., "(I keep wanting to say 'almost' here, but it really was certain.)").
  4. Detection guidance: Avoiding false positives

    main

    When using Humanizer, it is important to distinguish between AI patterns and legitimate human writing to avoid 'gutting' good prose. The following are not reliable indicators of AI and should generally be preserved:

    • Polished Prose: Perfect grammar and consistent style (often the result of professional editing).
    • Mixed Registers: Combining casual and formal tones (common in technical or neurodivergent writing).
    • Specific Vocabulary: Using formal or academic words (e.g., "ostensibly", "constituent") is not an AI tell unless they are part of a specific cluster of 'fancy' words.
    • Standard Formatting: Curly quotes, em dashes, or correct complex formatting (often produced by CMS or Word).
    • Common Transitions: Words like Additionally, moreover, or consequently are only problematic when used excessively/formulaically.
    • Standard Salutations: Letter-style openings or closings.
    • Short Sentences: Single short, emphatic sentences used for impact.
    • Unsourced Claims: A lack of citations is common in many human-written web texts.
    • Secondhand Text: Do not rewrite text inside quotations, titles, proper names, or examples where the phrase is being discussed.
  5. Install Humanizer via Skills CLI

    main

    You can install Humanizer globally using the cross-agent skills CLI. This makes the skill available in every project on your system.

    To install globally:

    npx skills add blader/humanizer --global

    To update an existing installation:

    npx skills update humanizer --global

    To install globally into every supported agent harness:

    npx skills add blader/humanizer --global --agent '*'

    To target a specific configured harness, use its agent name:

    npx skills add blader/humanizer --global --agent <agent-name>

    Note: Omit the --global flag for a project-local installation that can be committed to version control and shared with collaborators. After installation, start a new agent session or reload skills to apply changes.

  6. How to use the Humanizer skill

    main

    The humanizer skill is designed to remove signs of AI-generated writing from text to make it sound more natural and human. It follows a specific set of editorial rules based on Wikipedia's "Signs of AI writing" guide.

    Core Principles for Humanizing Text

    1. Identify AI patterns: Scan for inflated symbolism, promotional language, superficial -ing endings, vague attributions, and overused AI vocabulary.
    2. Preserve information, not shape: Every claim from the original must survive, but you should feel free to compress dull parts, dwell on important parts, and merge or split paragraphs to improve flow. Information takes precedence over original structure.
    3. Never invent facts: Do not add any names, numbers, dates, quotes, or citations not present in the source. You may add stance or opinion (personality) where appropriate, but never new factual claims.
    4. Match the voice: Adapt to the intended tone (formal, casual, technical).

    Voice Calibration

    If you provide a writing sample of your own previous work, the humanizer will analyze your sentence lengths, vocabulary, punctuation, and transitions to match your specific habits rather than just applying generic rules.

    # Example of the humanizer's goal
    
    **Before (AI-style):**
    The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
    
    **After (Humanized):**
    The Statistical Institute of Catalonia was established in 1989, part of a wider decentralization of administrative functions in Spain.
  7. Remove AI Style Patterns: Dashes, Boldface, and Lists

    main

    To humanize text, remove mechanical formatting patterns common in AI outputs:

    • Em Dashes and En Dashes (, ): Treat these as a hard constraint. Replace them with periods, commas, colons, or parentheses, or restructure the sentence. Exception: If a user-provided writing sample uses them, match that frequency instead.
    • Overuse of Boldface: Remove mechanical emphasis on key terms or acronyms (e.g., **OKRs**).
    • Inline-Header Vertical Lists: Avoid lists where items start with a bolded header followed by a colon (e.g., - **User Experience:** ...). Instead, integrate these into fluid prose.
    • Title Case in Headings: Convert headings from Title Case to sentence case (e.g., ## Strategic negotiations and global partnerships).
    • Emojis: Remove decorative emojis from headings or bullet points.
    • Curly Quotation Marks: Replace curly quotes (“...”) with straight quotes ("...").
    // Before (AI Style)
    ## Strategic Negotiations And Global Partnerships
    - **User Experience:** The user experience has been significantly improved.
    🚀 **Launch Phase:** The product launches in Q3
    
    // After (Humanized)
    ## Strategic negotiations and global partnerships
    The update improves the interface.
    The product launches in Q3.
  8. Remove AI Communication Patterns and Disclaimers

    main

    Eliminate text that sounds like chatbot correspondence or contains AI-specific knowledge limitations:

    • Collaborative Artifacts: Remove phrases meant for a chat interface like I hope this helps!, Certainly!, Let me know if..., or Would you like me to...?.
    • Knowledge-Cutoff Disclaimers: Remove phrases like as of [date], Up to my last training update, or While specific details are limited....
    • Speculative Gap-Filling: Avoid writing paragraphs about not finding information or using stock phrases for private individuals like maintains a low profile or keeps personal details private. If information is missing, state it clearly or omit the section.
    • Sycophantic Tone: Remove overly positive, people-pleasing language such as Great question! or You're absolutely right!.
    // Before (AI Communication)
    Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
    
    // After (Humanized)
    The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
  9. Avoid AI Rhetorical Tropes and Patterns

    main

    Identify and remove patterns used by LLMs to manufacture authority or drama:

    • Hyphenated Word Pair Overuse: Humans typically only hyphenate compound adjectives in the attributive position. Drop the hyphen when the compound follows the noun (e.g., use a high-quality report but the report is high quality).
    • Persuasive Authority Tropes: Avoid phrases used to pretend to uncover deep truths, such as The real question is, At its core, In reality, or Fundamentally.
    • Diff-Anchored Writing: Avoid writing documentation as if narrating a change (e.g., This function was added to replace...). Describe the thing as it is currently.
    • Manufactured Punchlines and Staccato Drama: Avoid stacking short, declarative fragments to create artificial tension (e.g., Then it arrived. It had no fear. No limits.).
    • Aphorism Formulas: Replace profound-sounding formulas like X is the Y of Z or X is not a tool but a mirror with concrete claims.
    • Conversational Rhetorical Openers: Remove fake-candid hooks like Honestly?, Look,, or Real talk, used before making an ordinary point.
    // Before (AI Tropes)
    Is it worth the price? Honestly? It depends on how often you'll use it.
    
    // After (Humanized)
    Whether it's worth the price depends on how often you'll use it.
  10. Use Humanizer to rewrite text

    main

    Invoke the skill using your agent harness's standard method (e.g., a slash command or a direct natural language request).

    Using a slash command:

    /humanizer
    
    [paste your text here]

    Using a direct request:

    Please humanize this text: [your text]

    Rewriting a file in place: You can point the skill at a specific file to rewrite its prose:

    Humanize the prose in docs/launch-post.md
  11. Install Humanizer as a Claude Code plugin

    main

    Claude Code users can install Humanizer directly from the marketplace. Once installed, the skill is invoked using the command /humanizer:humanizer.

    /plugin marketplace add blader/humanizer
    /plugin install humanizer@humanizer
  12. Manual Installation of Humanizer

    main

    Since Humanizer is provided as a plain Markdown file (SKILL.md), any agent harness that supports skill-style instructions can use it directly. You can install it by cloning the repository or copying the SKILL.md file into your harness's skill directory.

    Option 1: Clone the repository

    git clone https://github.com/blader/humanizer.git /path/to/your/skills/humanizer

    Option 2: Copy the skill file

    mkdir -p /path/to/your/skills/humanizer
    cp SKILL.md /path/to/your/skills/humanizer/