agentleFS
guerrilla2799guerrilla2799/sdr-copilot/skills/voice-interview/SKILL.md

voice-interview

Skill1 starsChanged 4 months agoMITView on GitHub

One-time interview that captures how the rep actually talks and writes, producing a voice profile every drafting skill uses so emails and scripts sound like them instead of AI. Use when the rep says "voice interview", "set up my voice", "make it sound like me", or when write-email/draft-sequence can't find voice-profile.md.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. ARCASSystems/FounderOS★ 7same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository14 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Ask one question at a time, conversationally.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Interview

A 15-minute conversation that ends with voice-profile.md saved in the working folder. After this runs once, every email and call script the other skills draft gets calibrated to the rep's real voice.

How to run it

Ask one question at a time, conversationally. React to answers, follow up on anything colorful, and pull real phrases out of them. Do NOT dump all questions at once — this is an interview, not a form.

The questions

  1. "Paste 2-3 emails you've sent that got replies — cold or not, doesn't matter. Real ones, typos and all." (This is the single most valuable input. If you have none handy, forward yourself a few and come back — but continue the interview meanwhile.)
  2. "How do you open a cold call when it's going well? Say it like you'd say it — I'll transcribe."
  3. "What words or phrases do you say all the time? What would your friends say is your verbal tic?"
  4. "How formal are you? Do you write 'Hi Eric,' or 'Eric —' or 'Hey Eric'? Sign-off?"
  5. "Read this line out loud, then tell me how YOU'D say it instead: '[one of your locked-messaging lines — see messaging.md]'" (Calibrates how you metabolize the locked messaging.)
  6. "What's a real conversation with a prospect that went great? Tell me the story — what did you actually say?"
  7. "What kind of email would you never send? What sales-y stuff makes you cringe?"
  8. "Humor: none, dry, or actually funny? Give me an example of a joke you'd put in a work email."
  9. "Sentence length: are you a short-and-punchy texter or do you write full paragraphs?"
  10. "Anything you're bad at in writing that I should quietly fix? (Comma splices, rambling, whatever — no judgment.)"

Producing the profile

Analyze the pasted emails harder than the self-description (people misreport their own voice — the samples are ground truth). Then write voice-profile.md to the working folder:

# Voice Profile — [rep name] · built [date]

## Voice in one paragraph
[how the rep sounds, so a drafting skill can imitate it]

## Mechanics
- Greeting / sign-off: ...
- Sentence length + rhythm: ...
- Formality: X/10
- Humor: [type + example]
- Punctuation habits: ...

## Phrase bank (things they actually say)
- "..."  [use these in drafts]

## Never-say list (their cringe list + anything in their samples they want gone)
- ...

## The locked messaging, in their mouth
[2-3 of the key locked-messaging lines rewritten the way THEY phrased them in Q5]

## Quiet fixes
[what to silently correct when drafting as them]

## Calibration sample
[one full cold email drafted in their voice, structure per write-email skill — shown to them and revised until they say "yeah, I'd send that"]

The exit test: draft the calibration sample, show it, and iterate until the rep says they'd send it as-is. Don't save the profile until they approve the sample. Tell them they can rerun this skill anytime their style evolves — it overwrites the old profile.

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.