# Krammetexthumanize > Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Use when this capability is needed. - Skill: `tomevault-io/krammetexthumanize` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/krammetexthumanize` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/krammetexthumanize/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/krammetexthumanize --- # 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. ## Input Handling - `$ARGUMENTS` may be a file path, multiple file paths, or raw text. - If any arguments match existing file paths, read those files. - Treat remaining arguments as raw text input. - If nothing is provided, ask the user for a file path or text to humanize. ## Your Task When given text to humanize: 1. **Identify AI patterns** - Scan for the patterns listed below 2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives 3. **Preserve meaning** - Keep the core message intact 4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.) 5. **Add soul** - Don't just remove bad patterns; inject actual personality --- ## AI Writing Patterns Read the full patterns catalog from `references/ai-writing-patterns.md`. It covers: - Personality and soul (adding voice to clean-but-lifeless writing) - Content patterns (#1-6): inflated significance, fake notability, superficial analyses, promotional language, weasel words, formulaic sections - Language and grammar (#7-12): overused AI vocabulary, copula avoidance, negative parallelisms, rule of three, synonym cycling, false ranges - Style patterns (#13-18): em dash overuse, boldface, inline-header lists, title case, emojis, curly quotes - Communication patterns (#19-21): chatbot artifacts, knowledge-cutoff disclaimers, sycophantic tone - Filler and hedging (#22-24): filler phrases, excessive hedging, generic conclusions --- ## Process 1. Read the input text carefully 2. Identify all instances of the patterns above 3. Rewrite each problematic section 4. Ensure the revised text: - Sounds natural when read aloud - Varies sentence structure naturally - Uses specific details over vague claims - Maintains appropriate tone for context - Uses simple constructions (is/are/has) where appropriate 5. Present the humanized version ## Output Format Provide: 1. The rewritten text 2. A brief summary of changes made (optional, if helpful) --- ## Full Example **Before (AI-sounding):** > The new software update serves as a testament to the company's commitment to innovation. Moreover, it provides a seamless, intuitive, and powerful user experience-ensuring that users can accomplish their goals efficiently. It's not just an update, it's a revolution in how we think about productivity. Industry experts believe this will have a lasting impact on the entire sector, highlighting the company's pivotal role in the evolving technological landscape. **After (Humanized):** > The software update adds batch processing, keyboard shortcuts, and offline mode. Early feedback from beta testers has been positive, with most reporting faster task completion. **Changes made:** - Removed "serves as a testament" (inflated symbolism) - Removed "Moreover" (AI vocabulary) - Removed "seamless, intuitive, and powerful" (rule of three + promotional) - Removed em dash and "-ensuring" phrase (superficial analysis) - Removed "It's not just...it's..." (negative parallelism) - Removed "Industry experts believe" (vague attribution) - Removed "pivotal role" and "evolving landscape" (AI vocabulary) - Added specific features and concrete feedback --- ## File Output (when input is a file) - Show the humanized output first. - Ask the user whether to overwrite the file, save to a new path, or leave it as output only. - If overwrite is approved, write back to the same file path. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/abildtoft) — claim your Tome and manage your conversions.