agentleFS
allthriveaiallthriveai/amplify/.claude/skills/voice/SKILL.md

voice

Skill0 starsChanged 3 months agoMITView on GitHub

Sets up your Voice.md through a guided conversation. Asks five questions about who you are, your mission, audience, beliefs, and communication style, then writes a populated Voice.md to the vault. Use when the user runs /voice or after running amplify init.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use claude-buddy, face-enroll and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • autonomous-aiSkill

    claude-buddy

    Coordinate with the Claude Buddy companion (Claude Desktop + Claude Code on the user's Mac) — voice-approve tool permission prompts and stay aware of Claude activity.

    Also in 3 projects that use this

  • autonomous-aiSkill

    face-enroll

    Manage the device's face recognition roster — enroll new faces (3 paths: user-supplied photo, agent-captured snapshot on user request, or HAL's familiar-stranger prompt) and maintain the enrolled set (status / remove / reset). All enrolled persons are friends; strangers stay unnamed until promoted via one of the enroll flows.

    Also in 3 projects that use this

  • +10 more from autonomous-ai

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user runs /voice:

    line 10
  2. Distinctive:

    Read the config and extract:

    line 20
  3. Very specific:

    Read the existing Voice.md at {vaultPath}/{paths.voice}.

    line 29
  4. Distinctive:

    If it exists and has real content (not just placeholder brackets), ask: "You already have a Voice.md.

    line 31
  5. Very specific:

    If it exists but is the blank template (has [Your name or [What you placeholder text), proceed to the interview.

    line 32
  6. Distinctive:

    If it doesn't exist, proceed to the interview.

    line 33
  7. Distinctive:

    Use AskUserQuestion or natural conversation to ask these five questions one at a time.

    line 37
  8. Distinctive:

    If the user gives a real answer, use it for that section.

    line 55
  9. Distinctive:

    If the user says "skip", presses enter with no input, or says they'll do it later, use the placeholder text for that section.

    line 56
  10. Very specific:

    Write the file to {vaultPath}/{paths.voice}.

    line 95
  11. Distinctive:

    Before writing, run a humanizer pass on any prose you wrote (not the user's own words).

    line 108

“Common” is measured: kept by at least 6 in 10 of the 25 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 Interview

Instructions

When the user runs /voice:

Step 0: Load Configuration

Find the .amplifyrc config file to resolve the vault path and voice file location. Check these locations in order:

  1. .amplifyrc in the current working directory
  2. .amplifyrc at the path specified by VAULT_PATH environment variable
  3. .amplifyrc at the fallback vault path (if configured in CLAUDE.md or known from previous sessions)

Read the config and extract:

vaultPath    → absolute path to the Obsidian vault
paths.voice  → voice file relative to vault root (default: "Amplify/Voice.md")

Step 1: Check for Existing Voice.md

Read the existing Voice.md at {vaultPath}/{paths.voice}.

  • If it exists and has real content (not just placeholder brackets), ask: "You already have a Voice.md. Want to start fresh or update specific sections?"
  • If it exists but is the blank template (has [Your name or [What you placeholder text), proceed to the interview.
  • If it doesn't exist, proceed to the interview.

Step 2: Ask the Five Questions

Use AskUserQuestion or natural conversation to ask these five questions one at a time. Wait for each answer before asking the next.

Question 1: Who I am "What's your name, what do you do, and what's your background? Tell me whatever feels relevant."

Question 2: My mission "What are you trying to accomplish? What change do you want to make?"

Question 3: My audience "Who are you talking to? What do they need? What keeps them up at night?"

Question 4: What I believe "What are your core beliefs? What hills will you die on? What makes your perspective different?"

Question 5: How I talk "How do you talk? Direct? Warm? Technical? Casual? What words do you use or avoid?"

For each question:

  • If the user gives a real answer, use it for that section.
  • If the user says "skip", presses enter with no input, or says they'll do it later, use the placeholder text for that section.

Step 3: Build Voice.md

Construct the Voice.md content using the user's answers. Write in first person, preserving their words and voice. Clean up grammar if needed but don't rewrite their personality.

Placeholder text for skipped sections:

SectionPlaceholder
Who I am[Your name, what you do, your background. Write in first person.]
My mission[What you're trying to accomplish. The change you want to make in the world.]
My audience[Who you're talking to. What they need. What keeps them up at night.]
What I believe[Your core beliefs. The hills you'll die on. What makes your perspective different.]
How I talk[Your voice: direct? warm? technical? casual? Funny? Serious? What words do you use? What do you never say?]

Format:

# Voice

## Who I am
{answer or placeholder}

## My mission
{answer or placeholder}

## My audience
{answer or placeholder}

## What I believe
{answer or placeholder}

## How I talk
{answer or placeholder}

Step 4: Write and Report

Write the file to {vaultPath}/{paths.voice}.

Report back:

Voice.md written to {paths.voice}

Sections filled: {count}/5
{if any skipped: "Run /voice again anytime to fill in the rest."}

Humanizer Pass

Before writing, run a humanizer pass on any prose you wrote (not the user's own words). No AI vocabulary, no filler, no significance inflation. The user's voice should come through, not yours.

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.