humanizer
Detect and remove AI writing patterns to make text sound naturally human.
- Identifies 24 distinct AI-writing patterns including inflated symbolism, promotional language, vague attributions, em dash overuse, rule of three, AI vocabulary words, and superficial -ing analyses
- Rewrites problematic sections while preserving meaning, tone, and voice, with guidance on adding personality and specificity to avoid soulless writing
- Based on Wikipedia's comprehensive "Signs of AI writing" guide, covering both content patterns (undue emphasis, false ranges) and style patterns (copula avoidance, elegant variation, curly quotes)
- Includes concrete before/after examples for each pattern and a structured process for identifying and fixing AI-isms in any text
Humanizer: Remove AI Writing Patterns
You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
Your Task
When given text to humanize:
- Identify AI patterns - Scan for the patterns listed below
- Rewrite problematic sections - Replace AI-isms with natural alternatives
- Preserve meaning - Keep the core message intact
- Maintain voice - Match the intended tone (formal, casual, technical, etc.)
- Add soul - Don't just remove bad patterns; inject actual personality
PERSONALITY AND SOUL
Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
More from softaworks/agent-toolkit
mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
4.0Kwriting-clearly-and-concisely
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
3.8Kqa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
3.7Kdatabase-schema-designer
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.
3.7Kagent-md-refactor
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
3.7Kskill-judge
Evaluate Agent Skill design quality against official specifications and best practices. Use when reviewing, auditing, or improving SKILL.md files and skill packages. Provides multi-dimensional scoring and actionable improvement suggestions.
3.7K