agentsclimarketplace
Sign in

Voice calibration

Skill raulpetruta/voice-calibration-plugin/skills/voice-calibration

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.From its SKILL.md

Install
npx -y skills add raulpetruta/voice-calibration-plugin --skill voice-calibration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.2 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

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 (.voice-profile.md in the project root or ~/.claude/voice-profile.md), read it and apply the style to your writing when the user asks you to write in their voice.

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:

  • Default location: .voice-profile.md in the current project root
  • Global location: ~/.claude/voice-profile.md (if the user wants it available across projects)
  • Ask the user which they prefer

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 .voice-profile.md file (check project root first, then ~/.claude/)
  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

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."

What ships with it: 4 files

14.0 KB alongside SKILL.md

examples/

references/

Gives 0 of the 12 instructions most docs writing skills give in ~1.1k tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Collect writing samples through interactive prompts
  • Present one prompt at a time
  • Analyze samples against stylistic dimensions
  • Generate a voice profile using the template
  • Save profile to project root or global directory
  • Read existing profile before writing content

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.