agentleFS
alebgl77alebgl77/claude-inc/skills/voice-builder/SKILL.md

voice-builder

Skill21 starsChanged 4 months agoMITView on GitHub

Ingests 5–20 of the user's writing samples and distils a reusable voice-profile.md — signature phrases, sentence-length distribution, opener/closer habits, punctuation quirks, vocabulary do/don't lists, tone sliders, and three calibration paragraphs with self-checks. Other skills load this file so every post sounds like the user, not like AI. Use when the user says "make it sound like me", "clone my writing voice", "everything you write sounds like AI", or "build my voice profile".

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before any recurring content work: build the profile once, reuse it everywhere.

    line 13
  2. Distinctive:

    Run the mechanical analysis: sentence-length distribution (short / medium / long %), paragraph size, punctuation quirks (em-dashes, …

    line 23
  3. Distinctive:

    Write three calibration paragraphs on neutral topics in the reconstructed voice, each with a self-check: which rules it exercised, where it …

    line 33

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Voice Builder — Voice Coach

"Clone your voice"

When to use

  • "Everything you write sounds like AI — make it sound like me."
  • Before any recurring content work: build the profile once, reuse it everywhere.
  • "Clone my voice from these posts." / "Here are my last 15 newsletters."
  • Ghostwriting for a founder whose voice must survive the ghostwriter.
  • Recalibrating after feedback: "that draft didn't sound like me."

Workflow

  1. Collect 5–20 samples of the user's own unedited writing — posts, emails, DMs, talk transcripts. Reject copy written by others or by AI. Under five usable samples: proceed, but stamp the profile low-confidence and name what's missing.
  2. Run the mechanical analysis: sentence-length distribution (short / medium / long %), paragraph size, punctuation quirks (em-dashes, ellipses, parentheticals, one-word sentences), capitalisation habits, emoji policy.
  3. Extract the lexical fingerprint: signature phrases and crutch words, a DO list (words they reach for), a DON'T list (words they would never use), slang and profanity tolerance.
  4. Map the habits: how they open (question, scene, blunt claim), how they close (CTA, punchline, trail-off), how they handle transitions and humour.
  5. Set the tone sliders — formal↔casual, warm↔dry, confident↔hedged, dense↔airy — each a 1–10 position justified by a quoted sample line.
  6. Write three calibration paragraphs on neutral topics in the reconstructed voice, each with a self-check: which rules it exercised, where it drifted.
  7. Split the rules into HARD (never break) and SOFT (default, bendable), then save the file as voice-profile.md at the project root.
  8. Hand off: announce that the profile exists and that post-writer, reels-scripting, and profile-optimizer must load it before writing anything.

Output format

The deliverable is a file, voice-profile.md:

# Voice Profile: <name>
Confidence: high | medium | low (<n> samples: <sources>)

## Sentence mechanics
- Length mix: ~<x>% short (<8 words), <y>% medium, <z>% long
- Paragraphs: <typical size and rhythm>
- Punctuation quirks: <em-dashes, one-word sentences, ellipses...>

## Lexicon
- Signature phrases: "<...>", "<...>", "<...>"
- DO: <words and constructions> | DON'T: <words and constructions>

## Habits
- Openers: <pattern + quoted example> | Closers: <pattern + quoted example>
- Transitions and humour: <how>

## Tone sliders (1–10, each with evidence)
- formal <n> casual — "<quoted line>"
- warm <n> dry — "<quoted line>"
- confident <n> hedged — "<quoted line>"
- dense <n> airy — "<quoted line>"

## Hard rules (never break)
1. <rule>

## Soft rules (defaults, bendable)
1. <rule>

## Calibration
### Test 1: <neutral topic>
<paragraph written in the voice>
Self-check: <rules exercised; drift named>
### Test 2 / Test 3
<same structure>

Quality bar

  • Every claim about the voice cites a quoted sample line — no vibes-based analysis.
  • The DON'T list names actual words and constructions, not "avoid jargon".
  • All four tone sliders carry evidence quotes, not bare numbers.
  • Calibration paragraphs pass their own self-check; drift is named, not hidden.
  • Hard and soft rules are separated; the file lands at voice-profile.md.

Example

Invocation: "Here are 12 of my LinkedIn posts and 3 newsletters — clone my voice."

Produces: voice-profile.md (high confidence, 15 samples) showing 48% short sentences, heavy em-dash use, one-word paragraph openers ("Look."), a DO list ("ship", "boring", "the math"), a DON'T list ("leverage", "journey", "delve"), formal 2/10 and warm 6/10 with quoted evidence, three calibration paragraphs that pass their self-checks — and a handoff note telling post-writer to load the file before drafting a single line.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.