humanize

Remove robotic language and enforce terminology rules in user-facing content.

Updated Aug 23, 2026

Search Tags:#documentation #writing #tone #editing #clarity #humanize

Ready to run

npx skills add https://github.com/lukeslp/accessibility-skills --skill humanize-lukeslp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: humanize
Source: https://github.com/lukeslp/accessibility-skills/tree/main/plugins/accessibility/skills/humanize
Command: npx skills add https://github.com/lukeslp/accessibility-skills --skill humanize-lukeslp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires doc_humanizer, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes robotic, overly formal, or buzzword-laden language from user-facing content, ensuring it sounds natural and human-written.

Core Features & Use Cases

Robot Voice Detection: Identifies and suggests fixes for common AI-generated writing patterns.
Terminology Enforcement: Bans vague terms like "AI" and enforces specific replacements.
Use Case: You've written a README file for your open-source project, but it sounds a bit stiff. Use this Skill to make it more approachable and engaging for potential contributors.

Quick Start

Use the humanize skill to improve the tone of the README.md file.

Frequently Asked Questions about humanize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make my README documentation sound less robotic and more human?▼

To make README documentation sound less robotic, use this Skill to detect common AI-generated writing patterns and suggest tone fixes for a more natural, approachable style. It targets stiff language to improve user-facing content engagement.

What's the best way to enforce terminology rules in project documentation?▼

The best way to enforce terminology rules in project documentation is applying automated editing checks that ban vague terms like "AI" and enforce specific replacements. This ensures your public-facing content maintains descriptive language consistency.

Can I use automated editing to fix robotic tone in code comments?▼

Yes, you can use automated editing to fix robotic tone in code comments. This Skill specifically removes overly formal language and buzzwords from code comments intended for public consumption, ensuring they sound natural and human-written.

Why does my open-source package description sound stiff and how do I fix it?▼

Your open-source package description sounds stiff due to common AI-generated writing patterns. You can fix it by applying this Skill to remove buzzword-laden language and enforce specific, descriptive terminology for better contributor engagement.

Does this content editing approach work for public-facing documentation?▼

Yes, this content editing approach works specifically for public-facing documentation. It analyzes READMEs, code comments, and package descriptions to remove robotic language and ensure your text sounds human-written before public release.

When should I not use a humanizer for documentation editing?▼

You should not use a humanizer for documentation editing when your content requires strict formal compliance or technical precision where altering terminology might violate established standards. It is built for user-facing clarity rather than internal technical specifications.