agentleFS
agiea-brainagiea-brain/agency-skills/skills/paul-munro/write-in-the-owners-voice/SKILL.md

write-in-the-owners-voice

Skill1 starsChanged 17 days agoMITView on GitHub

Use this skill when an agent drafts outward messages that go out under a firm owner's name (email, direct messages, posts, comments, texts) and the owner keeps catching wording they would never write. Drafts come from the owner's real sent writing: the agent changes the nouns of the nearest sent message, checks the draft against hard rules, never-written phrases, usual length and past corrections, and sends only on a pass from the last hour. Every night, drafts matched to sent mail become swaps, and a held-out test scores whether a judge can tell a draft from the real thing. Also use for "write it like me", "draft this in my voice", "reply for me", "that doesn't sound like me", "why does this read like a robot".

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    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 you write a word, pull the nearest examples and the register:

    line 24
  2. Distinctive:

    Write the draft by changing the nouns of the nearest example.

    line 30
  3. Distinctive:

    Put the exact text to be sent in a file, with no subject line, and check it:

    line 31
  4. Distinctive:

    When the owner corrects your wording, record the correction the same turn as a swap: your phrase, their phrase.

    line 41
  5. Distinctive:

    MUST pull examples and the register before drafting, for every outward message in the owner's name.

    line 54
  6. Distinctive:

    MUST check the exact text to be sent, and check again after any change.

    line 55
  7. Distinctive:

    MUST rewrite every BLOCK line as a new sentence.

    line 56
  8. Distinctive:

    MUST send within 60 minutes of the pass, or check again.

    line 57
  9. Distinctive:

    MUST record each wording correction from the owner as a swap in the same turn.

    line 58
  10. Distinctive:

    MUST keep the corpus local, on the owner's machine.

    line 59
  11. Distinctive:

    NEVER upload, quote, post or link the corpus or any message in it to a connector, a shared page, a task tool or any remote host.

    line 60
  12. Distinctive:

    NEVER draft from the style rules alone.

    line 61
  13. Distinctive:

    NEVER work around a gate refusal.

    line 62
  14. Distinctive:

    NEVER let the drafting side of the nightly test see the real message it is drafting.

    line 63
  15. Distinctive:

    NEVER expect a script to do a model's job.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Applies whenever you draft a message that will go out under the owner's name, to a client, a peer, a vendor, a prospect or the public. Produces one checked draft built from the owner's own sent writing, and a pass that lets it be sent within the hour.

The play

  1. Keep a local corpus of what the owner wrote: one record per sent message, the owner's words only. Quoted replies, forwarded blocks, the signature and tracking footers are cut. It is built from mail and chat exports, or from messages you read through a connector. The corpus holds client mail and personal messages, so it stays on the owner's machine. Record shapes are in references/json-shapes.md.
  2. Before you write a word, pull the nearest examples and the register:
    examples --to ADDRESS_OR_NAME --channel email --n 8
    examples --to ADDRESS_OR_NAME --channel email --stats
    Examples rank by the same recipient first, then the same email domain, then the same channel and kind of recipient, then a similar length, then word overlap with the facts you give. A message that breaks a hard rule is never offered, so you cannot copy a habit the owner has since dropped. --stats gives the median length, the median sentence length, and the owner's usual openers and closers.
  3. Write the draft by changing the nouns of the nearest example. Keep its opener, its length and its close. The rules are the check, never the source.
  4. Put the exact text to be sent in a file, with no subject line, and check it:
    check FILE --to ADDRESS_OR_NAME --channel email --save-draft
    The check returns BLOCK, FLAG or PASS. What each catches is in references/the-check.md.
  5. Act on the result:
    • BLOCK: rewrite each listed line as a new sentence. Changing its punctuation is not a rewrite. Run the check again.
    • FLAG: read each flagged word, phrase or length note. Change whatever the owner would not write. Keep what they would, such as a name or a term from the thread.
    • PASS or FLAG writes a pass for that exact text and saves the draft for the nightly loop.
  6. Send that same text within 60 minutes. One changed word after the check needs a new check. A hook in front of every send tool refuses a send whose text has no pass from the last hour. A refusal is never worked around. The draft goes back to step 2.
  7. When the owner corrects your wording, record the correction the same turn as a swap: your phrase, their phrase. From then on the check catches it.
  8. Let the nightly loop run without the owner: yesterday's sent mail goes into the corpus, saved drafts are matched to what was sent, the changes become swaps, and a held-out test scores the drafting. The order is in references/the-loop.md.

What good looks like

  • First thing I check: whether the draft started from a sent example or from a description of my style. A draft written from rules reads like a draft written from rules. One note carried a technical phrase I had to catch myself, and that is why the system exists.
  • The mediocre version is a long style guide and a reminder to follow it. It drifts within a week. The check and the gate hold because they are mechanical.
  • I know it is working when I send drafts unchanged. Each one is recorded as a pass, and the swap list stops growing.
  • I know the drafting is good when the held-out judge sits near 0.5. That means it cannot tell the draft from what I really sent.
  • Red flag: a swap list full of the agent's own rewrites. Several drafts of one note once got written up as my corrections. Only the newest draft of a note is matched to what I sent now. The earlier ones are marked superseded and never become swaps.

Rules

  • MUST pull examples and the register before drafting, for every outward message in the owner's name.
  • MUST check the exact text to be sent, and check again after any change.
  • MUST rewrite every BLOCK line as a new sentence.
  • MUST send within 60 minutes of the pass, or check again.
  • MUST record each wording correction from the owner as a swap in the same turn.
  • MUST keep the corpus local, on the owner's machine.
  • NEVER upload, quote, post or link the corpus or any message in it to a connector, a shared page, a task tool or any remote host.
  • NEVER draft from the style rules alone.
  • NEVER work around a gate refusal. Go back to the examples.
  • NEVER let the drafting side of the nightly test see the real message it is drafting.
  • NEVER expect a script to do a model's job. The scripts call no model. The agent does that part.

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.