write-like-a-human

Name: write-like-a-human
Author: spencerpauly

15stars4forks

How to install write-like-a-human?

spencerpauly/skills-repo/write-like-a-human

$npx -y skills add spencerpauly/skills-repo --skill write-like-a-human

Installs into the current project.

Summary

Strip the AI-isms out of any text — em-dash overuse, "It's not just X, it's Y", inflated significance, sycophantic openers, rule-of-three padding. Use when the user says "humanize this", "make this less AI", "tighten this", or pastes obviously-AI prose and asks for a rewrite.

Files · 1

View on GitHub

SKILL.md

1	# Write Like a Human
2
3	Rewrite text so it stops sounding like a language model wrote it. Wraps the open-source [humanizer](https://github.com/blader/humanizer) skill, which catalogs ~30 specific tells (em-dash overuse, "stands as a testament", `-ing` analyses, rule-of-three padding, inline-bold lists, and so on).
4
5	## When to use
6
7	- The user pastes a chunk of writing and asks to "humanize", "de-AI", "tighten", or "make this sound like me".
8	- The user asks for editing on something they wrote with an LLM.
9	- A blog post / launch email / README draft has tells the user wants gone.
10
11	## Steps
12
13	1. Load the reference list of patterns the first time this skill activates in a session. On Spencer's machine, read the canonical local copy (newer than upstream):
14	```bash
15	cat ~/.agents/skills/humanizer/SKILL.md
16	```
17	Otherwise pull it from upstream:
18	```bash
19	curl -fsSL https://raw.githubusercontent.com/blader/humanizer/main/SKILL.md
20	```
21	There are ~30 patterns; you don't need to memorize them, just keep them visible while editing.
22
23	2. Ask for a voice sample if you don't already have one. One paragraph the user wrote themselves is enough. Match cadence, vocabulary, and how they handle transitions. For content written as Spencer, the voice layer is the `spencers-writing-style` skill in the stack repo (`.agents/skills/spencers-writing-style/`) — use it instead of asking.
24
25	3. Do a first pass removing the highest-signal tells in this order:
26	1. Sycophantic openers ("Great question!", "Absolutely!").
27	2. Em-dashes that should be commas, periods, or parens.
28	3. "It's not just X, it's Y" / "Not only … but …" parallelisms.
29	4. Inflated significance words: testament, pivotal, landscape, vibrant, tapestry, underscore.
30	5. Rule-of-three lists that pad ideas into groups of three.
31	6. Inline-bold vertical lists (`- Speed: …`).
32
33	4. Do a second "audit" pass. Re-read your draft and ask out loud: "What still makes this sound AI-generated?" Answer briefly, then revise once more. This step is the difference between "cleaned up" and "actually sounds human".
34
35	5. Return three things:
36	- A draft rewrite.
37	- A short list of remaining tells you noticed during the audit.
38	- A final rewrite with those fixed.
39
40	## Don't
41
42	- Don't replace AI mush with new AI mush. If the original said "stands as a testament to" and you change it to "represents a key milestone in", you haven't fixed anything.
43	- Don't sand off the user's voice. Quirks, opinions, and the occasional sentence fragment are the point.
44	- Don't add em-dashes back in. If you must use a punctuation break, prefer a period.
45
46	## Reference
47
48	Patterns and examples: <https://github.com/blader/humanizer>

People who liked this also viewed

6 picks

Type

write-like-a-human

15stars4forks

View on GitHub

How to install write-like-a-human?

spencerpauly/skills-repo/write-like-a-human

$npx -y skills add spencerpauly/skills-repo --skill write-like-a-human

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Write Like a Human
2
3	Rewrite text so it stops sounding like a language model wrote it. Wraps the open-source [humanizer](https://github.com/blader/humanizer) skill, which catalogs ~30 specific tells (em-dash overuse, "stands as a testament", `-ing` analyses, rule-of-three padding, inline-bold lists, and so on).
4
5	## When to use
6
7	- The user pastes a chunk of writing and asks to "humanize", "de-AI", "tighten", or "make this sound like me".
8	- The user asks for editing on something they wrote with an LLM.
9	- A blog post / launch email / README draft has tells the user wants gone.
10
11	## Steps
12
13	1. Load the reference list of patterns the first time this skill activates in a session. On Spencer's machine, read the canonical local copy (newer than upstream):
14	```bash
15	cat ~/.agents/skills/humanizer/SKILL.md
16	```
17	Otherwise pull it from upstream:
18	```bash
19	curl -fsSL https://raw.githubusercontent.com/blader/humanizer/main/SKILL.md
20	```
21	There are ~30 patterns; you don't need to memorize them, just keep them visible while editing.
22
23	2. Ask for a voice sample if you don't already have one. One paragraph the user wrote themselves is enough. Match cadence, vocabulary, and how they handle transitions. For content written as Spencer, the voice layer is the `spencers-writing-style` skill in the stack repo (`.agents/skills/spencers-writing-style/`) — use it instead of asking.
24
25	3. Do a first pass removing the highest-signal tells in this order:
26	1. Sycophantic openers ("Great question!", "Absolutely!").
27	2. Em-dashes that should be commas, periods, or parens.
28	3. "It's not just X, it's Y" / "Not only … but …" parallelisms.
29	4. Inflated significance words: testament, pivotal, landscape, vibrant, tapestry, underscore.
30	5. Rule-of-three lists that pad ideas into groups of three.
31	6. Inline-bold vertical lists (`- Speed: …`).
32
33	4. Do a second "audit" pass. Re-read your draft and ask out loud: "What still makes this sound AI-generated?" Answer briefly, then revise once more. This step is the difference between "cleaned up" and "actually sounds human".
34
35	5. Return three things:
36	- A draft rewrite.
37	- A short list of remaining tells you noticed during the audit.
38	- A final rewrite with those fixed.
39
40	## Don't
41
42	- Don't replace AI mush with new AI mush. If the original said "stands as a testament to" and you change it to "represents a key milestone in", you haven't fixed anything.
43	- Don't sand off the user's voice. Quirks, opinions, and the occasional sentence fragment are the point.
44	- Don't add em-dashes back in. If you must use a punctuation break, prefer a period.
45
46	## Reference
47
48	Patterns and examples: <https://github.com/blader/humanizer>

People who liked this also viewed

6 picks

Type