agentleFS
diaryofamademandiaryofamademan/skills/comms/SKILL.md

comms

Skill3 starsChanged 4 days agoMITView on GitHub

Founder communications — how a founder names the moment, takes the narrative personally, and says it directly. Covers announcements, launches, crises, and everyday content. Built on Lulu Cheng Meservey's Go Direct doctrine, with narrative structure from Andy Raskin, a positioning diagnostic from Al Ries, distribution from Gary Vaynerchuk, and a plain-writing gate from Paul Graham.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 14

    Distinctive

    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:

    Every run of this skill, whatever the mode, returns the same four things, in this order:

    line 20
  2. Distinctive:

    The claim sort: Every material claim in the message, listed and marked: said by the founder, or needs a witness — and for each witness …

    line 23
  3. Distinctive:

    Every audience already has a slot for you in its mind, and that mind is oversimplified and resistant: it keeps what matches what it already …

    line 43
  4. Distinctive:

    If it vacates it, what position is rushing in to replace it — and who benefits from that replacement?

    line 47
  5. Distinctive:

    Every claim in the message then gets sorted:

    line 49
  6. Distinctive:

    Run the plain-writing gate before anything ships:

    line 68
  7. Distinctive:

    Read it aloud. Where it stops sounding like a person talking, it is not finished.

    line 70
  8. Distinctive:

    Keep the edges. An unorthodox founder sanded down into a corporate voice has traded away the only advantage they had.

    line 73
  9. Distinctive:

    Document the work instead of inventing content.

    line 86
  10. Distinctive:

    After you speak, the reactions become the story.

    line 91
  11. Distinctive:

    Claim only what the documents support: When a matter ends — a case, an investigation, a negotiation — your statement may say what the …

    line 97
  12. Distinctive:

    Never outsource the story.

    line 101
  13. Distinctive:

    If a committee could have written it, it says nothing.

    line 104
  14. Distinctive:

    Bad ending that is actually an ending: When the signed record closes a matter, publish the record's own facts and let witnesses carry the …

    line 119

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

<img src="assets/icons/megaphone-01.svg" width="20" height="20" alt="" /> comms

Communications is not a service the founder buys. It is one of the founder's jobs, because the story is the product: nobody would outsource the product, and outsourcing the story is the same mistake in a different department. This skill is a decision procedure for the moments when a founder or a company has to say something that matters — and for the everyday content that decides whether anyone is listening when those moments come.

It runs in four modes. The procedure is the same; the stakes and the clock change.

  • Announcement — news you choose to make: a launch, a raise, a hire, a result.
  • Crisis — news made about you: an attack, a failure, a scandal, a regulator, a story you did not start and cannot stop.
  • Response — the moves after either of the above, when other people's reactions become the story.
  • Everyday — the steady output (posts, videos, newsletter) that builds the audience and the position the other three modes draw on.

<img src="assets/icons/check-list.svg" width="20" height="20" alt="" /> What a run returns

Every run of this skill, whatever the mode, returns the same four things, in this order:

  1. The moment, named in one sentence. "This is a crisis about X; what is at stake is Y." If the sentence cannot be written, the run stops here and says why.
  2. The claim sort. Every material claim in the message, listed and marked: said by the founder, or needs a witness — and for each witness claim, the witness (the document, the filing, the coverage, the customer) and whether it exists yet.
  3. The statement. The text itself, written to ship: founder's voice, plain-writing gate passed, narrative structure in place where the moment needs one.
  4. The response plan. What happens after it lands: who watches, what would trigger a follow-up, the resistance price of the likely pushbacks, and the date and owner of the next word. In everyday mode this collapses to the posting cadence and the ship-to-yap check.

<img src="assets/icons/workflow.svg" width="20" height="20" alt="" /> The procedure

<img src="assets/icons/target-01.svg" width="20" height="20" alt="" /> 1. Name the moment

Before writing a word, say plainly what kind of moment this is and what is actually at stake. An announcement is priced by whether it travels. A crisis is priced by what the audience will believe about you when it ends. A silence can be the moment: if other people are telling the story and you are not, the story is being told — by them.

Output of this step: one sentence. "This is a crisis about X; what is at stake is Y." If you cannot write that sentence, you are not ready to say anything.

<img src="assets/icons/mic-01.svg" width="20" height="20" alt="" /> 2. Decide who speaks

The best spokesperson is whoever holds the knowledge the enterprise is built on — the person who can describe the idea and, under opposition, fight for it and win. That is almost always the founder. Polish, tenure, and credentials are not the qualification.

Exceptions are real but narrow: a statement about a process (an investigation, a transition, a search) belongs to whoever owns the process. A statement about the mission, the product, the failure, or the future belongs to the founder. If a committee could have written the draft in front of you, it says nothing — send it back.

<img src="assets/icons/search-01.svg" width="20" height="20" alt="" /> 3. Diagnose the position you already hold

Every audience already has a slot for you in its mind, and that mind is oversimplified and resistant: it keeps what matches what it already believes and discards the rest. So before building any message, answer three questions.

  • What position do we hold in this audience's mind today, in a few words?
  • Does this moment reinforce that position, contest it, or vacate it?
  • If it vacates it, what position is rushing in to replace it — and who benefits from that replacement?

Every claim in the message then gets sorted:

  • Say it yourself. Your story, your reasons, your vision, your decision. Nobody credible can tell these for you, and your own audience is the channel.
  • Needs a witness. Facts about yourself that the audience cannot check — your character, your innocence, how something ended. Said by you, these are claims. Said by a source the audience already trusts, they are evidence. Plan for the witness version: the document, the filing, the coverage, the customer.

<img src="assets/icons/book-open-01.svg" width="20" height="20" alt="" /> 4. Build the narrative

For any moment that needs to travel, structure it so other people can retell it without you in the room:

  1. Name a big change in the world that is already underway.
  2. Show that the change creates winners and losers.
  3. Describe the promised land the change makes possible.
  4. Present what you built as the means to get there.
  5. Show evidence the story is already coming true.

A message that depends on the audience reading your full text has already failed. Write the version a supporter would repeat in one breath; that version is the message.

<img src="assets/icons/message-01.svg" width="20" height="20" alt="" /> 5. Say it plainly

Run the plain-writing gate before anything ships:

  • Read it aloud. Where it stops sounding like a person talking, it is not finished.
  • It must tell the reader something important, something they did not already know, and something true, in words they actually use.
  • Cut every sentence whose purpose is to avoid upsetting somebody. A statement that offends no one informs no one.
  • Keep the edges. An unorthodox founder sanded down into a corporate voice has traded away the only advantage they had.

<img src="assets/icons/rocket-01.svg" width="20" height="20" alt="" /> 6. Go direct

Say it on channels you own, at a time you choose, to the audience that is actually yours. Intermediaries — press, platforms' editors, partners — get it after your audience does, or at the same moment, never instead of them.

Going direct does not mean doing every communications task yourself forever, refusing all help, or boycotting the press. It means the story is crafted and told by its owner and never depends on an intermediary's permission or framing.

<img src="assets/icons/share-01.svg" width="20" height="20" alt="" /> 7. Run the distribution layer

Attention is a market and it moves. For everyday mode especially:

  • Give value in the platform's own language, repeatedly, before asking for anything. The ask lands because of what came before it.
  • Document the work instead of inventing content. The running record of building is the material; it never runs out and it cannot be faked by a competitor.
  • Watch for underpriced attention and move early, but price the total output honestly with the ship-to-yap ratio: talk is worth what has been shipped underneath it. In announcement and crisis modes this step shrinks — one statement, well placed, beats a week of posting.

<img src="assets/icons/security-check.svg" width="20" height="20" alt="" /> 8. Response discipline

After you speak, the reactions become the story. Rules for that phase:

  • Resistance is escalation. Pushing back on a narrative is a move that raises the stakes of the exchange. Sometimes that is the right move. Never make it by reflex.
  • Admissions are complete or not yet made. A partial admission does not end a story; it schedules the second one, on a worse day, with your credibility already spent. If you cannot yet admit the whole of something, say what is true and say that more is coming — do not stage the truth in installments that events will overtake.
  • Confidence is debt. A public statement of confidence, support, or certainty creates an obligation that comes due when events test it. Make such statements only when you are prepared for them to be quoted back at the worst moment.
  • Correct the record once, completely, with documents. Then stop. Arguing in installments keeps the story alive and moves you down the ladder in the audience's mind with every round.
  • Claim only what the documents support. When a matter ends — a case, an investigation, a negotiation — your statement may say what the signed record says, no cleaner and no dirtier. The audience's witnesses (coverage, filings, counterparties) will carry the rest.

<img src="assets/icons/security-check.svg" width="20" height="20" alt="" /> Guardrails

  1. Never outsource the story. Help is fine; dependence is not.
  2. A partial admission schedules the second scandal.
  3. A confidence statement is debt that comes due at the worst time.
  4. If a committee could have written it, it says nothing.
  5. Claim only what the documents support.
  6. Sort every claim: said by you, or needs a witness.
  7. Boring is a choice, and it has a price. The founder's edge is being the person who actually knows — do not trade it for polish.
  8. Resistance is escalation. Price the pushback before making it.
  9. Repetition inside one story is waste; repetition of your position across stories is how a position gets built.
  10. In a crisis, the fight is over which position replaces yours if yours is vacated. Name the replacement early, or your opponents will.
  11. A position held by one person, with no second name the audience can picture in the role, is a single point of failure. Build the second name in everyday mode, long before a crisis needs it.

<img src="assets/icons/presentation-01.svg" width="20" height="20" alt="" /> Worked patterns

Launch. Everyday mode has built the audience; announcement mode spends it. Founder speaks. Narrative: the change, the losers, the promised land, the product as the way there, the evidence. One direct statement, then the distribution layer carries it for days — demos, customer words (witnesses), the build record. Precondition: the narrative and the founder's statement are drafted before any date is announced anywhere. A date announced before its narrative exists is how launches drift into company-voice filler.

Crisis, first 24 hours. Name the moment honestly, including if the honest name is "we do not yet know." Founder speaks to what the founder owns; process owners speak to process. Admit completely what is already provable; commit to a specific time for the rest. Do not issue confidence you may have to retract while the facts are still arriving.

Bad ending that is actually an ending. When the signed record closes a matter, publish the record's own facts and let witnesses carry the interpretation. Resist writing the victory speech the documents do not contain.

The long middle. Some crises run for years between the first statement and the ending. In that stretch, public comms about the matter goes quiet: the first statement has set the position, and every additional public word is repetition inside one story. Disclosure does not stop — it changes form, becoming a private, sequenced act (after value lands, before a counterparty's diligence, in person or in a prepared brief) instead of a public one. Everyday mode carries the position in the meantime, by shipping.

<img src="assets/icons/legal-01.svg" width="20" height="20" alt="" /> Limits and boundaries

  • Counsel rules the legal line. This skill shapes the founder's voice, timing, and narrative. It does not decide what may legally be said. In an active legal or regulatory matter, counsel reviews any statement before it ships, and where counsel and this skill disagree about wording, counsel wins and the skill reworks the statement inside the cleared lines.
  • Style is a separate layer. This skill decides who speaks, what position a message defends, and when it ships. How the text sounds in each channel — length, format, per-platform tone — belongs to a style guide (in the author's stack, the writing-styles skill). Style never overrides a decision made here; a decision made here never excuses text that fails the plain-writing gate.
  • Facts are inputs, not outputs. The skill works on the record it is given. If the record is incomplete, the run says so and works the long-middle pattern instead of inventing certainty.

Sources

Paraphrased and credited; no source text is reproduced.

  • Lulu Cheng Meservey, "GO DIRECT: THE MANIFESTO" (Flack, 2024) — the doctrine spine: the story is the product, the founder is the spokesperson, go direct without depending on intermediaries. Her talks add "resistance is escalation" and the ship-to-yap ratio.
  • Andy Raskin, "The Greatest Sales Deck I've Ever Seen" (2016) — the five-part narrative structure in step 4.
  • Al Ries and Jack Trout, Positioning: The Battle for Your Mind (1981); Al Ries and Laura Ries, The Fall of Advertising and the Rise of PR (2002) — the position diagnostic in step 3 and the witness rule. Used in scoped form: the rest of the positioning apparatus is marketing, and the first-into-the-mind claim has known counter-evidence (Golder and Tellis).
  • Gary Vaynerchuk, Jab, Jab, Jab, Right Hook (2013) and the document-don't-create practice — step 7's distribution discipline.
  • Paul Graham, "Write Like You Talk" (2015) and "How to Write Usefully" (2020) — the plain-writing gate in step 5.

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.