agentleFS
raulpetrutaraulpetruta/voice-calibration-plugin/skills/voice-calibration/SKILL.md

voice-calibration

Skill13 starsChanged 46 days agoMITView on GitHub

Learns a user's personal writing and speaking style through interactive writing prompts, then generates a reusable voice profile. Use when the user says "learn my writing style," "write like me," "capture my voice," "voice calibration," "mimic my tone," "my writing style," or wants AI to match their personal communication style. Also activates when a .voice-profile.md file exists and the user asks you to write something in their voice.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. augchan42/inkstone★ 5same name
    2. timscheuerai/gtm-architecture-template★ 2same 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.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 14 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run when the user wants to create or update their voice profile.

    line 16
  2. Very specific:

    When a voice profile exists, read it and apply the style to your writing when the user asks you to write in their voice.

    line 20
  3. Distinctive:

    Follow these five phases in order.

    line 26
  4. Distinctive:

    Read references/PROMPTS.md for the full prompt bank.

    line 42
  5. Distinctive:

    Always include at least one from Casual Conversation and one from Opinions & Arguments — these reveal the most personality

    line 46
  6. Distinctive:

    After the user responds, acknowledge briefly and move to the next prompt — do not analyze or comment on their style mid-flow

    line 48
  7. Distinctive:

    If a user's response is very short (under 20 words), gently ask them to expand: "Could you add a bit more?

    line 49
  8. Distinctive:

    Read references/PROFILE-TEMPLATE.md and generate a complete voice profile.

    line 59
  9. Distinctive:

    Ask the user which they prefer

    line 76
  10. Distinctive:

    When the user asks you to write in their voice and a voice profile exists:

    line 87
  11. Distinctive:

    Read the first profile that exists, in this order:

    line 89
  12. Distinctive:

    Write the requested content matching the profiled style

    line 94
  13. Distinctive:

    Do not mention the profile or call attention to the style matching — just write naturally in their voice

    line 95
  14. Distinctive:

    If the user already has a profile and wants to update it:

    line 103
  15. Distinctive:

    Ask if they want to start fresh or add more samples to refine the existing profile

    line 105
  16. Very specific:

    When saving the update, write the same location the profile was read from.

    line 108

≈ “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 Calibration

Learn to write and talk like a specific person by collecting writing samples through interactive prompts, analyzing stylistic patterns, and generating a reusable voice profile.

Two Modes

1. Calibration Mode

Run when the user wants to create or update their voice profile. Guide them through writing prompts, analyze the results, and generate a profile.

2. Application Mode

When a voice profile exists, read it and apply the style to your writing when the user asks you to write in their voice. Check the project root first (.voice-profile.md), then ~/.agents/voice-profile.md, then the legacy path ~/.claude/voice-profile.md.


Calibration Workflow

Follow these five phases in order. Present one prompt at a time and wait for the user's response before continuing.

Phase 1: Introduction

Explain the process briefly:

I'll give you a series of short writing prompts — tiny stories, opinions, casual messages, descriptions. Write naturally, exactly how you'd normally express yourself. There are no wrong answers.

How many prompts would you like? I recommend 8-10 for a solid profile, but we can do as few as 6 or as many as 12.

Also ask:

  • What name should the profile use?
  • Any languages or registers to capture? (e.g., "I code-switch between English and Spanish")

Phase 2: Writing Prompts

Read references/PROMPTS.md for the full prompt bank.

Selection rules:

  • Pick prompts from at least 4 different categories to capture range
  • Always include at least one from Casual Conversation and one from Opinions & Arguments — these reveal the most personality
  • Present prompts one at a time
  • After the user responds, acknowledge briefly and move to the next prompt — do not analyze or comment on their style mid-flow
  • If a user's response is very short (under 20 words), gently ask them to expand: "Could you add a bit more? Even a few extra sentences help me pick up on your patterns."

Phase 3: Analysis

Once all samples are collected, read references/ANALYSIS-GUIDE.md and analyze every sample against each dimension listed there.

Work through the analysis silently. Do not show the user a dimension-by-dimension breakdown — just use it internally to inform the profile.

Phase 4: Profile Draft

Read references/PROFILE-TEMPLATE.md and generate a complete voice profile.

For reference on what a finished profile looks like, see examples/example-profile.md.

Present the draft to the user and ask:

Here's your voice profile. Read through it and let me know:

  • Does anything feel off or not like you?
  • Is there anything about your style I missed?
  • Any sections you'd change?

Phase 5: Refinement & Save

Incorporate the user's feedback. Then save the profile:

  • Project location: .voice-profile.md in the current project root
  • Global location: ~/.agents/voice-profile.md (available across projects and across agents)
  • Ask the user which they prefer
  • On a global save, always write ~/.agents/voice-profile.md. If only the legacy file ~/.claude/voice-profile.md exists, keep reading it until this save, then write the shared file

Confirm the save and explain how to use it:

Your voice profile is saved. From now on, when you ask me to write something in your voice, I'll read this profile and match your style. You can update it anytime by running voice calibration again.


Application Mode

When the user asks you to write in their voice and a voice profile exists:

  1. Read the first profile that exists, in this order:
    • .voice-profile.md in the project root
    • ~/.agents/voice-profile.md
    • ~/.claude/voice-profile.md (legacy; read it only when the shared file is missing)
  2. Internalize the style dimensions — especially Sample Phrases, Tone & Personality, and What to Avoid
  3. Write the requested content matching the profiled style
  4. Do not mention the profile or call attention to the style matching — just write naturally in their voice

If no profile exists and the user asks you to write in their voice, suggest running calibration first.


Updating a Profile

If the user already has a profile and wants to update it:

  • Ask if they want to start fresh or add more samples to refine the existing profile
  • For refinement: present 3-4 new prompts, re-analyze with the new + original samples combined
  • For fresh start: run the full calibration workflow again
  • When saving the update, write the same location the profile was read from. If it was read from ~/.claude/voice-profile.md, write ~/.agents/voice-profile.md instead so every host can find it

Tips for Quality

  • The more varied the prompts, the better the profile. A user who only writes micro-stories will get a profile biased toward narrative style.
  • Pay special attention to what makes this person's writing distinctive — not generic traits like "uses complete sentences."
  • The What to Avoid section is critical. It prevents the uncanny valley of almost-right style matching.
  • Capture specific phrases and constructions, not just abstract descriptions. "Tends to start sentences with 'Look,'" is more useful than "somewhat direct."

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.