Outbound Copy Humanizer

What this does

Generated outbound has a recognizable surface: tripled adjectives, a hedge before every claim, transitions nobody says out loud, and a closing sentence that restates the email. This skill strips those patterns and rebuilds the sentence rhythm against the sender's own writing, without flattening the message into slang.

Requirements

This skill needs no account, API key or paid service. It works from the files, exports and answers you give it, in any agent that reads SKILL.md.

When to use it

• this sounds robotic
• make this sound human
• too much AI voice
• rewrite in my voice
• humanize this copy

Inputs

• draft: the copy to rewrite
• samples: two or three things the sender actually wrote, if available

Shared context this skill reads

Before doing anything else, read whichever of these exist at the project root and use them instead of asking the user to repeat themselves:

• VOICE.md
• BRAND.md

If none exist, do the work from what the user gives you, then offer to write the missing file so the next skill in the pack starts warmer.

Tool connection

This skill needs no live data tool. It works from the files, exports and answers you give it, so it runs the same in any agent with no setup.

Method

1. Read the voice file or the samples first and extract three concrete markers: average sentence length, whether contractions are used, and how the sender opens a message.
2. Remove the tells: adjective triples, hedges stacked in front of a claim, transitional phrases nobody speaks, and the summary sentence at the end.
3. Vary the sentence length deliberately. Uniform sentence length is the strongest tell and the easiest to fix.
4. Replace abstract nouns with the concrete thing they stand for. Solutions becomes the actual thing being sold.
5. Keep every fact. Humanizing is a rewrite of the surface, not a license to soften a claim into vagueness or to invent warmth that is not earned.
6. Read the result out loud in your head, sentence by sentence, and cut whatever you would not say.
7. Check the output with scripts/check-output.py before you return it.

Approval stop

This skill does not send email or write to a CRM. If the user asks it to, stop first: show what would be sent or written and wait for an explicit yes.

Output

The rewrite, plus a short list of what was removed and why, so the sender learns the pattern rather than depending on the skill.

Check the output before you return it

Save the output to a file and run python3 scripts/check-output.py <file>. The contract it checks is scripts/output-contract.json.

• Exit 0, COMPLETE: return the output.
• Exit 2, INCOMPLETE: do not present the output as finished. Fill what you can, run the check again, and if parts stay missing, return the output under the heading Incomplete with every reason the check printed.

Quality bar

• Every factual claim in the original survives in the rewrite
• Sentence lengths vary across the rewrite
• No adjective triples remain
• The removal list names the pattern, not just the words

Related skills

• cold-email-structure-checker
• subject-line-lab
• linkedin-post-writer

Ships in the cold-email-system pack.