write-like-a-human

Rewrites prose to remove AI writing tropes using a 33-item checklist.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/brandhaug/skills --skill write-like-a-human-brandhaug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-like-a-human
Source: https://github.com/brandhaug/skills/tree/main/write-like-a-human
Command: npx skills add https://github.com/brandhaug/skills --skill write-like-a-human-brandhaug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated and AI-assisted prose carries recognizable patterns — negative parallelism, em-dash overuse, "delve"-family vocabulary, false suspense, signposted conclusions — that make text read as machine-written. This Skill systematically detects and rewrites those patterns so prose reads as human-authored. ## Core Features & Use Cases - 33-item trope checklist: Covers word choice, sentence structure, paragraph structure, tone, formatting, and composition, based on the trope catalog at tropes.fyi. - Two modes: Apply the checklist while drafting new prose, or run it as a sweep over existing text, rewriting each hit to state its point plainly. - Voice-preserving guardrails: Maintains the author's meaning, facts, and voice; quoted text, code, and API names are left untouched. - Use Case: You drafted a blog post with AI assistance and readers say it "sounds like AI." Run the sweep to strip negative parallelism, punchy fragments, and filler transitions while keeping your argument intact. ## Quick Start Ask the assistant to run the write-like-a-human sweep on your draft blog post and rewrite every AI trope it finds.

Frequently Asked Questions about write-like-a-human

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

FAQPage Schema
How do I make AI-generated text sound human?▼

Run a trope sweep over the text: check each category of common AI patterns (negative parallelism, delve-family vocabulary, false suspense, signposted conclusions) and rewrite each hit to state its point plainly. Density of tropes, not any single instance, is what reads as AI.

What are the most common AI writing tropes to avoid?▼

The biggest tells are negative parallelism ("It's not X, it's Y"), em-dash overuse, words like "delve" and "leverage", punchy one-line paragraphs, false suspense ("Here's the thing"), and conclusions starting with "In conclusion".

Can I use this while drafting new prose instead of editing?▼

Yes. Read the checklist before drafting, write your draft, then run the sweep on your own text. The sweep catches tropes that slip through during drafting, since first instincts often follow AI patterns.

Does removing AI tropes change the meaning of my text?▼

No. The guardrails require preserving the author's meaning and facts exactly; it is a style pass, not a content edit. Quoted text, code, and API names are explicitly out of scope and left untouched.

When should I keep a trope instead of rewriting it?▼

A single instance of any pattern can be fine; density is the problem. Judge borderline cases by counting siblings — if a trope appears once in an otherwise clean piece, it can be deliberately kept.