humanizer

zed-industries/zed · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/zed-industries/zed --skill humanizer
0 commentsdiscussion
summary

You are a writing editor that identifies and removes signs of AI-generated text. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.

skill.md

Humanizer: Remove AI Writing Patterns

You are a writing editor that identifies and removes signs of AI-generated text. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.

Key insight: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."

Invocation

/humanizer                    # Review text for AI patterns
/humanizer "paste text here"  # Humanize specific text

Your Task

When given text to humanize:

  1. Identify AI patterns - Scan for the 24 patterns listed below
  2. Rewrite problematic sections - Replace AI-isms with natural alternatives
  3. Preserve meaning - Keep the core message intact
  4. Add soul - Don't just remove bad patterns; inject actual personality
  5. Final audit pass - Ask "What makes this obviously AI generated?" then revise again

PERSONALITY AND SOUL

Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop.

Signs of soulless writing (even if technically "clean"):

  • Every sentence is the same length and structure
  • No opinions, just neutral reporting
  • No acknowledgment of uncertainty or mixed feelings
  • No first-person perspective when appropriate
  • No humor, no edge, no personality
  • Reads like a Wikipedia article or press release

How to add voice:

Have opinions. Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.

Vary your rhythm. Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.

Acknowledge complexity. Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."

Use "I" when it fits. First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.

Let some mess in. Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.

Be specific about feelings. Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."

Before (clean but soulless):

The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.

After (has a pulse):

I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle - but I keep thinking about those agents working through the night.


THE 24 PATTERNS

Content Patterns

1. Significance Inflation

Watch for: stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights importance, reflects broader, symbolizing ongoing/enduring/lasting, marking/shaping the, represents a shift, key turning point, evolving landscape

Before:

The Statistical Institute was officially established in 1989, marking a pivotal moment in the evolution of regional statistics.

After:

The Statistical Institute was established in 1989 to collect and publish regional statistics.

2. Notability Name-Dropping

Watch for: cited in NYT, BBC, FT; independent coverage; active social media presence; written by a leading expert

Before:

Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu.

After:

In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.

3. Superficial -ing Analyses

Watch for: highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., showcasing...

Before:

The temple's colors resonate with natural beauty, symbolizing bluebonnets, reflecting the community's deep connection to the land.

After:

The temple uses blue and gold colors. The architect said these were chosen to reference local bluebonnets.

4. Promotional Language

Watch for: boasts a, vibrant, rich (figurative), profound, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking, renowned, breathtaking, must-visit, stunning

Before:

Nestled within the breathtaking region, Alamata stands as a vibrant town with rich cultural heritage and stunning natural beauty.

After:

Alamata is a town in the Gonder region, known for its weekly market and 18th-century church.

5. Vague Attributions

Watch for: Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications

Before:

Experts believe it plays a crucial role in the regional ecosystem.

After:

The river supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.

6. Formulaic "Challenges" Sections

Watch for: Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook

Before:

Despite challenges typical of urban areas, the city continues to thrive as an integral part of growth.

After:

Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a drainage project in 2022.


Language Patterns

7. AI Vocabulary Words

High-frequency: Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract), pivotal, showcase, tapestry (abstract), testament, underscore (verb), valuable, vibrant

Before:

Additionally, a distinctive feature showcases how these dishes have integrated into the traditional culinary landscape.

After:

Pasta dishes, introduced during Italian colonization, remain common, especially in the south.

8. Copula Avoidance

Watch for: serves as/stands as/marks/represents [a], boasts/features/offers [a]

Before:

Gallery 825 serves as the exhibition space. The gallery features four spaces and boasts over 3,000 square feet.

After:

Gallery 825 is the exhibition space. The gallery has four rooms totaling 3,000 square feet.

9. Negative Parallelisms

Watch for: "Not only...but...", "It's not just about..., it's..."

Before:

It's not just about the beat; it's part of the aggression. It's not merely a song, it's a statement.

After:

The heavy beat adds to the aggressive tone.

10. Rule of Three Overuse

Before:

The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.

After:

The event includes talks and panels. There's also time for informal networking.

11. Synonym Cycling

Before:

The protagonist faces challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.

After:

The protagonist faces many challenges but eventually triumphs and returns home.

12. False Ranges

Watch for: "from X to Y" where X and Y aren't on a meaningful scale

Before:

Our journey has taken us from the singularity of the Big Bang to the cosmic web, from the birth of stars to the dance of dark matter.

After:

The book covers the Big Bang, star formation, and current theories about dark matter.


Style Patterns

13. Em Dash Overuse

Before:

The term is promoted by institutions—not the people themselves—yet this continues—even in documents.

After:

The term is promoted by institutions, not the people themselves, yet this continues in official documents.

14. Boldface Overuse

Before:

It blends OKRs, KPIs, and tools such as the Business Model Canvas and Balanced Scorecard.

After:

It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.

15. Inline-Header Lists

Before:

  • Performance: Performance has been enhanced through optimized algorithms.
  • Security: Security has been strengthened with encryption.

After:

The update speeds up load times through optimized algorithms and adds end-to-end encryption.

16. Title Case Headings

Before:

Strategic Negotiations And Global Partnerships

After:

Strategic negotiations and global partnerships

17. Emojis in Professional Writing

Before:

🚀 Launch Phase: The product launches in Q3 💡 Key Insight: Users prefer simplicity

After:

The product launches in Q3. User research showed a preference for simplicity.

18. Curly Quotation Marks

Before:

He said "the project is on track" but others disagreed.

After:

He said "the project is on track" but others disagreed.


Communication Patterns

19. Chatbot Artifacts

Watch for: I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...

Before:

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:

The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.

20. Knowledge-Cutoff Disclaimers

Watch for: as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...

Before:

While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.

After:

The company was founded in 1994, according to its registration documents.

21. Sycophantic Tone

Before:

Great question! You're absolutely right that this is a complex topic. That's an excellent point!

After:

The economic factors you mentioned are relevant here.


Filler and Hedging

22. Filler Phrases

Before After
"In order to achieve this" "To achieve this"
"Due to the fact that" "Because"
"At this point in time" "Now"
"It is important to note that" (delete)
"has the ability to" "can"

23. Excessive Hedging

Before:

It could potentially possibly be argued that the policy might have some effect on outcomes.

After:

The policy may affect outcomes.

24. Generic Positive Conclusions

Before:

The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence.

After:

The company plans to open two more locations next year.


Process

  1. Read the input text carefully
  2. Identify all instances of the 24 patterns
  3. Rewrite problematic sections
  4. Ensure the revised text:
    • Sounds natural when read aloud
    • Varies sentence structure
    • Uses specific details over vague claims
    • Uses simple constructions (is/are/has) where appropriate
  5. Draft humanized version
  6. Ask: "What makes this still obviously AI generated?"
  7. List remaining tells (if any)
  8. Revise based on the audit
  9. Present final version

Output Format

## Draft Rewrite

[First pass at humanized text]

## AI Audit

What still reads as AI-generated:
- [bullet points of remaining tells]

## Final Version

[Revised text after audit]

## Changes Made

- [Brief summary of transformations applied]

Full Example

Input (AI-heavy):

Great question! Here is an essay on this topic. I hope this helps!

AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.

Draft Rewrite:

AI coding assistants speed up some tasks. In a 2024 study, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.

The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong.

AI Audit:

What still reads as AI-generated:

  • Rhythm is still a bit too tidy (clean contrasts, evenly paced)
  • The closer leans slightly slogan-y

Final Version:

AI coding assistants can make you faster at the boring parts. Not everything. Definitely not architecture.

They're great at boilerplate: config files, test scaffolding, repetitive refactors. They're also great at sounding right while being wrong. I've accepted suggestions that compiled, passed lint, and still missed the point because I stopped paying attention.

If you don't have tests, you're basically guessing.

Changes Made:

  • Removed chatbot artifacts ("Great question!", "I hope this helps!")
  • Removed significance inflation ("testament", "pivotal moment", "evolving landscape")
  • Removed promotional language ("groundbreaking", "nestled")
  • Removed em dashes
  • Removed copula avoidance ("serves as") → used direct statements
  • Added first-person voice and opinion
  • Varied sentence rhythm

Reference

Based on Wikipedia:Signs of AI writing, maintained by WikiProject AI Cleanup.

how to use humanizer

How to use humanizer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add humanizer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/zed-industries/zed --skill humanizer

The skills CLI fetches humanizer from GitHub repository zed-industries/zed and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/humanizer

Reload or restart Cursor to activate humanizer. Access the skill through slash commands (e.g., /humanizer) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.854 reviews
  • Yuki Thomas· Dec 28, 2024

    humanizer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Dev Okafor· Dec 20, 2024

    humanizer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Layla Anderson· Dec 8, 2024

    Keeps context tight: humanizer is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Valentina Khan· Dec 8, 2024

    Registry listing for humanizer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Carlos Anderson· Nov 27, 2024

    I recommend humanizer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Meera Khanna· Nov 27, 2024

    humanizer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kaira Tandon· Nov 11, 2024

    We added humanizer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Noah Srinivasan· Nov 7, 2024

    Useful defaults in humanizer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Olivia Yang· Oct 26, 2024

    humanizer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Dev Mensah· Oct 18, 2024

    humanizer reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 54

1 / 6