← ClaudeAtlas

human-voicelisted

Write anything that goes out under a real person's name — CVs, resumes, cover letters, outreach, emails, application answers — in their voice rather than AI voice. Covers first-person prose and CV bullets separately, because the tells are different. Load it on every document build; working from memory is how the tells get through.
Jawahars07/ballast · ★ 0 · AI & Automation · score 72
Install: claude install-skill Jawahars07/ballast
# Human Voice Anything a person sends under their own name should read as though they typed it. This skill covers two different problems with two different failure modes: - **Part 1 — first-person prose.** Cover letters, outreach, emails, application answers. The tell here is vocabulary and sentence shape. - **Part 2 — CVs and resumes.** The tell here is **rhythm**, not vocabulary. A keyword-dense skills block is correct, not a giveaway. Load both parts before writing. Working from memory is how tells get through — that is a documented failure, not a hypothetical one. ## The rule that outranks this entire skill **Sounding human never licenses inventing a fact.** Every concrete detail, number, opinion or rough edge must already exist in `facts.md`. If a bullet feels generic, the fix is to go *find* the real specific, never to write a plausible one. A fabricated "human" detail is worse than a bland true one. It is the one error that cannot be walked back in an interview. --- ## Part 1 — First-person prose Write the way the person types, not the way a model writes: 1. **Short sentences.** Get to the point in line one. No throat-clearing. 2. **Banned openers:** "I've been following your work", "I admire", "I am writing to express my keen interest", "I am thrilled to", "passionate about leveraging". 3. **Plain words over buzzwords.** "helping teams actually use AI", not "driving AI-enabled transformation". 4. **Warm, not formal. Confident, not begging.** A pee