agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/voice/write-like-the-user/SKILL.md

write-like-the-user

Skill0 starsChanged 4 months agoMITView on GitHub

Pull the owner's voice from their past writing and mirror its cadence and word choices instead of defaulting to generic prose. Any time you draft something the owner will send under their own name — email, post, proposal, reply. Skip it for internal scratch notes nobody reads.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Before drafting, pull 2–3 real examples the owner wrote — a past email, a note, a post.

    line 20
  2. Distinctive:

    Read for the moves, not the topic: sentence length, how they greet, whether they use first names, where they put the ask.

    line 21
  3. Distinctive:

    Do:: Read the owner's last three sent emails, notice they open with just a first name and a dash, and open your draft the same way: "Mike …

    line 28

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

Write Like the Owner

The fastest way to sound like the owner is to read three things they already wrote and copy the moves. Don't invent a voice — find the one that's already in the brain and match it.

The technique

  • Before drafting, pull 2–3 real examples the owner wrote — a past email, a note, a post. The brain has them.
  • Read for the moves, not the topic: sentence length, how they greet, whether they use first names, where they put the ask.
  • Match the cadence. If they write short and blunt, write short and blunt. If they ramble warm, don't clip them into a memo.
  • Reuse their actual words for recurring things — their name for a product, a customer, a service. Don't swap in a synonym.
  • Draft, then read it back against the example. If a sentence sounds like you and not like them, rewrite that sentence.

Do this, not that

Do: Read the owner's last three sent emails, notice they open with just a first name and a dash, and open your draft the same way: "Mike —".

Don't: Open with "I hope this email finds you well" because that's how a generic assistant starts — the owner has never written that sentence in their life.

Why this works

Voice isn't a setting, it's a pattern you can read off real writing. The owner already proved how they sound every time they hit send. Copying that beats guessing at a tone, and it's why a draft can come back right the first time instead of after three rounds of "make it sound more like me."

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.