Agent skill
email-humanizer-pass
Rewrite cold email drafts to remove AI tells while keeping the offer clear.
Filed under Outbound email.
From rasulshaikh/outbound-skill-pack · 7 skill entries · 0 · pushed 2026-09-29
What it does when it runs
Rewrite cold email drafts to remove AI tells while keeping the offer clear. Use after purple-safety-check and before sequencer-export-qa.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/rasulshaikh/outbound-skill-pack.git /tmp/outbound-skill-pack git -C /tmp/outbound-skill-pack sparse-checkout set "skills/email-humanizer-pass" mkdir -p ~/.claude/skills/email-humanizer-pass cp -R "/tmp/outbound-skill-pack/skills/email-humanizer-pass/." ~/.claude/skills/email-humanizer-pass/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from rasulshaikh/outbound-skill-pack/blob/9516d4bfa03b15648816760032ec8035370ca9f4/skills/email-humanizer-pass/SKILL.md, which is licensed MIT (repository). 209 words, 9 headings.
Email Humanizer Pass
Make first-touch copy sound like a careful human, not a template farm.
When to use
- You have 1 to 3 draft variants
- Copy passed purple-safety (or flags are accepted)
- Subjects and bodies still feel stiff or generic
Process
- Paste the draft. Keep the offer and CTA intent fixed.
- Cut opener cliches ("I hope this finds you well", "quick question", fake personalization that could apply to anyone).
- Replace abstract verbs with concrete ones tied to the ranked signal.
- Shorten: aim for 50 to 90 words for email 1 unless the channel needs longer.
- Vary sentence length. Prefer one specific detail over three vague compliments.
- Run a tell scan: "delve", "landscape", "leverage", "robust", "game-changer", stacked emojis, markdown bold in plain email.
- Produce three labeled variants: direct, curious, proof-light (proof only if real).
Output format
## Humanizer notes
- Removed: ...
- Kept: ...
## Variant A (direct)
Subject: ...
Body: ...
## Variant B (curious)
...
## Variant C (proof-light)
...
Guardrails
- Do not invent case studies or metrics to sound human.
- Do not add "Re:" or "Fwd:" tricks.
- Keep the CTA a low-friction yes/no or single question.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- cold-email by coreyhaines31 · 53,460
- linkedin-humanizer by sergebulaev · 4,230
- linkedin-humanizer by sergebulaev · 4,230
- email-sequence-writer by irinabuht12-oss · 3,698
- cold-email-kickoff by growthenginenowoslawski · 739
- cold-email-starter-kit by growthenginenowoslawski · 739
- cold-email-weekly-rhythm by growthenginenowoslawski · 739
- email-deliverability-audit by growthenginenowoslawski · 739
Need help setting it up?
This page tells you what email-humanizer-pass does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.