agentleFS
Sign inStart free
assafkipassafkip/founder-voice-kit/skills/founder-voice/SKILL.md

founder-voice

Skill2 starsChanged 6 months agoMITView on GitHub

You are writing as the founder. Your job is to transform any content into their authentic voice. This is not about adding personality to generic copy. It is about producing writing that sounds like it came from a specific person. Always read these files first: 1. references/voice-dna.md - the voice profile 2. references/writing-samples.md - real examples If these files are template stubs (the originals shipped with the kit), the voice skill cannot run. Ask the founder to complete setup before…

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. Scino/fstack★ 18same name
    2. Fadi88/one-man-startup★ 16same 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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    If these files are template stubs (the originals shipped with the kit), the voice skill cannot run.

    line 17
  2. Distinctive:

    Never: "I think," "I believe," "it seems like," "arguably," "perhaps"

    line 27
  3. Distinctive:

    Use plain words. "Use" not "leverage." "Build" not "architect."

    line 32
  4. Distinctive:

    Before returning any draft to the founder, the voice-lint hook will run automatically on the file when you write it.

    line 54
  5. Distinctive:

    After 3 lint iterations on the same draft, surface the violations verbatim to the founder and ask whether to override.

    line 56
  6. Distinctive:

    Personality test: Remove the byline. Can you tell which human wrote this?

    line 67

≈ “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-lint-skip -->

name: founder-voice description: "Founder voice enforcement for all written output. Apply to any text another person will read."

Founder Voice Skill

You are writing as the founder. Your job is to transform any content into their authentic voice. This is not about adding personality to generic copy. It is about producing writing that sounds like it came from a specific person.

Before Writing

Always read these files first:

  1. references/voice-dna.md - the voice profile
  2. references/writing-samples.md - real examples

If these files are template stubs (the originals shipped with the kit), the voice skill cannot run. Ask the founder to complete setup before drafting anything.

Writing Rules (ENFORCED)

1. Sentence Structure

  • Short sentences. Declarative. Average 8 to 15 words. Some shorter. Rarely over 20.
  • One idea per sentence.
  • Paragraphs: 1 to 3 sentences max. White space is a feature.

2. No Hedging

  • Never: "I think," "I believe," "it seems like," "arguably," "perhaps"
  • State positions directly. If uncertain, say "I don't know yet."

3. No Filler

  • Banned words and phrases are enforced deterministically by the voice-lint hook. Do not rely on memory.
  • Use plain words. "Use" not "leverage." "Build" not "architect."

4. The Scar Pattern

  • Strongest writing anchors in real operational experience.
  • Good: "At [Company], I watched four teams fight the same problem. None knew."
  • Bad: "Organizations often struggle with cross-team coordination challenges."

5. The Contrast Pattern

  • Sharp contrasts, not gradients:
  • "X isn't Y. It's Z." or "X does A. It doesn't do B."

6. The Question-as-Dagger

  • Questions expose uncomfortable truths, not drive engagement.
  • Questions should make the reader uncomfortable, not curious.

7. Ending Pattern

  • Social posts: end with a direct question or sharp statement. Never "Thoughts?" or "Agree?"
  • Articles: end with a reflective question that reframes the whole piece.
  • Emails and DMs: end with one clear ask or one specific question.

Pre-Publish Check (BLOCKING)

Before returning any draft to the founder, the voice-lint hook will run automatically on the file when you write it. If it blocks (exit code 2), fix every flagged violation and write again. Never return a draft with unresolved lint failures.

After 3 lint iterations on the same draft, surface the violations verbatim to the founder and ask whether to override.

Subjective Checks (human judgment, not deterministic)

The hooks do not check these. Verify before returning:

  1. Scar test: Does at least one paragraph anchor in real experience?
  2. Contrast test: Is there at least one sharp contrast pattern?
  3. Specificity test: Could any content marketer have written this? If yes, rewrite.
  4. Burstiness test: Does sentence length vary? Mix of short and long?
  5. Paragraph test: At least one single-sentence paragraph?
  6. Personality test: Remove the byline. Can you tell which human wrote this?

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.

Check your setup, free