paulund/ai v3.1.0 - Writing Humanizer skill

v3.1.0 introduces the Writing Humanizer as a standalone skill in the paulund/ai collection. It gives Claude Code a reference set of patterns to spot and remove from AI-generated text, making drafts sound more natural.

What changed

The Writing Humanizer skill is now available in the skills directory. It targets common AI writing tells and suggests plainer alternatives:

• Em dashes — replaced with commas, full stops, or restructured sentences
• Significance inflation — flags phrases like "pivotal moment", "testament to", "marks a shift in"
• Copula avoidance — replaces "serves as", "stands as", "functions as" with direct "is" or "are"
• Filler phrases — cuts "In order to", "Due to the fact that", "It is important to note that"
• Promotional tone — removes "vibrant", "groundbreaking", "stunning", "exciting"
• Rule of three — breaks up forced triplets
• Inline-header lists — avoids **Term:** explanation bullet patterns
• Hedging — trims "could potentially possibly", "might perhaps"
• Generic endings — removes "The future looks bright" style closings

This was already partially covered in v3.0.0, but v3.1.0 promotes it to a dedicated skill file that can be invoked directly during writing tasks.

Why it matters

If you use Claude Code to draft blog posts, documentation, or marketing copy, the output often carries AI signatures that readers notice. Rather than manually editing every draft, you can now reference the Writing Humanizer skill and have Claude self-correct during the writing process. It saves a pass of manual editing and improves the consistency of the final text.

How to upgrade

No breaking changes. Pull the latest version of the repo and the skill is available alongside the others in the skills directory.

Links

• Release on GitHub
• paulund/ai repository