agentleFS
corebits-iocorebits-io/deal-origination-system/skills/outreach-writer/SKILL.md

outreach-writer

Skill1 starsChanged 3 months agoMITView on GitHub

Write personalized outreach to business owners about a possible acquisition, grounded in each company's actual, sourced signal. Enforces voice rules, sender voice, and compliance guardrails. Never fabricates familiarity. Triggers on: write outreach, owner outreach, write to owners, draft acquisition emails, seller outreach, write cold email to owner, outreach copy, personalize messages, draft letters to owners, approach a business owner.

2 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    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:

    Read thesis-profile.md: sections 1 (who is buying, funding honesty), 2 (thesis), 8 (why an owner should talk to you), 9 (senders), 10 …

    line 24
  2. Very specific:

    Read targets.csv, filtered to scored rows with a contact route.

    line 28
  3. Distinctive:

    Before writing anything, extract from sections 1 and 8 the exact phrases for who the buyer is, funding status, and proof points.

    line 69
  4. Distinctive:

    No em dashes, ever

    line 100
  5. Very specific:

    No banned phrases (the full list is in references/outreach-voice-rules.md)

    line 101
  6. Distinctive:

    Never open with "I"

    line 104
  7. Distinctive:

    No stated or implied valuation, multiple, or price

    line 108
  8. Distinctive:

    No implied offer, LOI, or committed process

    line 109
  9. Distinctive:

    No claimed committed capital unless section 1 permits it

    line 110
  10. Distinctive:

    No false urgency ("we are closing our list this month")

    line 111
  11. Distinctive:

    No manufactured familiarity or invented admiration

    line 112
  12. Distinctive:

    No implication you know their financials — you do not

    line 113
  13. Distinctive:

    Never write a sentence that is false about the person whose name is on it

    line 120
  14. Distinctive:

    Run this before showing anything.

    line 126
  15. Very specific:

    Write drafts to outreach/ in the workspace.

    line 149
  16. Distinctive:

    Every variation, in full, grouped by segment and channel

    line 151
  17. Distinctive:

    Shorter always wins: When a message will not fit, you are explaining rather than stating.

    line 191
  18. Distinctive:

    The user knows their market: If they rewrite your copy, learn the pattern and apply it to the rest rather than defending the draft.

    line 197

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

Owner Outreach Writer

Writes the messages. Personalization comes from the quoted signal captured during research, never from invention.

Owners are not SaaS leads. They built the thing you are writing about, they get approached constantly by people who have not read past the company name, and they can smell a template in the first line. Shorter, human, direct.

Read first, in full:

  • references/outreach-voice-rules.md — the rules are hard rules, not preferences
  • references/compliance-and-ethics.md — what can never be said

Step 0 — Load and gate

  1. Read thesis-profile.md: sections 1 (who is buying, funding honesty), 2 (thesis), 8 (why an owner should talk to you), 9 (senders), 10 (compliance notes). If it does not exist, stop and walk the user through creating it from templates/thesis-profile.md.
  2. Read targets.csv, filtered to scored rows with a contact route.

🚧 HARD GATE — compliance

Confirm from the thesis profile before writing a word:

  • The buyer description in section 1 is true and the user has permission to say "funded" only if committed capital actually exists
  • Nothing in the copy will imply an offer, a valuation, or an LOI that does not exist
  • The proof points and permission-to-name list from section 8. You will use only these. Not hint at more. Not gesture at more.
  • Intermediary status from section 10. If the user is a fee-based intermediary rather than a principal buyer, stop and point them at references/compliance-and-ethics.md and counsel.

Step 1 — Segment

Segment by bridge tier, per references/outreach-voice-rules.md. The bridge determines the message shape.

SegmentWhoBridge
A — SpecificQuoted signal about this exact business"I read about your [specific, sourced thing]."
B — Sector/localReal thesis fit, sector or geography level signal"We are looking at [their sector] in [their region]."
C — CategoricalRight profile, no specific signal"Writing to a small number of [type] owners."
D — No bridgeNo factual connection existsNo bridge. Honest general letter.

Segment D is a real segment with a real message. Per the voice rules, an honest general message outperforms a manufactured connection every time. "I have long admired your business" from a stranger is worse than nothing.

Assign a sender to each segment from section 9. A principal writing to an owner works. An analyst's name on a letter about selling a life's work does not.


Step 2 — Lock the core claims

Before writing anything, extract from sections 1 and 8 the exact phrases for who the buyer is, funding status, and proof points. Write them down verbatim.

These are locked strings. They appear identically in every message. If an owner forwards two versions to their accountant and the descriptions differ, that becomes a credibility question you will not get to answer.

Show the locked list to the user for approval before writing.


Step 3 — Write

For each segment, write three variations so a sequence does not look like a mail merge to owners who compare notes at the trade association meeting.

Structure — four parts, in order, nothing else

  1. Who is writing. The sender, plainly, as a principal. Named person, named firm, one sentence.
  2. Why this company. The bridge. Factual, sourced. Omit for segment D.
  3. What you want. Stated plainly: you buy companies like theirs, you are interested in whether they would ever consider a conversation about selling. No euphemism, no "partnership opportunities."
  4. Small ask. A short call or a reply, at their pace. Never an offer.

Hard limits

  • Cold email: under 120 words
  • Posted letter: under one page, same structure, slightly warmer
  • LinkedIn note: under 300 characters
  • No em dashes, ever
  • No banned phrases (the full list is in references/outreach-voice-rules.md)
  • Sixth grade reading level. Owners are busy, not stupid — plain wins
  • Never open with "I"

Compliance, enforced in every message

  • No stated or implied valuation, multiple, or price
  • No implied offer, LOI, or committed process
  • No claimed committed capital unless section 1 permits it
  • No false urgency ("we are closing our list this month")
  • No manufactured familiarity or invented admiration
  • No implication you know their financials — you do not
  • Confidentiality respected: never reference their possible sale in a subject line a receptionist might read

Sender voice, enforced per sender

  • Principal or founder of the buyer: first person, direct
  • Never write a sentence that is false about the person whose name is on it

Step 4 — Self-check every message

Run this before showing anything. Fix, do not flag.

  • Under the word or character limit
  • Zero em dashes, zero banned phrases
  • Bridge is traceable to a quoted signal with a signal_source
  • No fabricated familiarity
  • No valuation, offer, or urgency language
  • Buyer description matches the locked strings exactly
  • True about the named sender
  • One ask, and it is small
  • Says plainly that this is about a possible acquisition
  • Reads out loud like a person talking

The owner test. Would you read this if it were about your company, from a stranger? If not, rewrite it. This catches more than every other check combined.


Step 5 — Present for approval

🚧 HARD GATE

Write drafts to outreach/ in the workspace. Show the user:

  • Every variation, in full, grouped by segment and channel
  • Which sender is assigned to each
  • The word or character count on each
  • The exact quoted signal each segment A message is built on, with its URL
  • How many targets each segment covers

Nothing enters a send queue without explicit approval. Nothing sends from this system, ever.


Step 6 — Report

Outreach copy drafted — 4 segments, 14 variations

  Segment A (specific signal)   22 owners   3 email + 1 letter   sender: [principal]
  Segment B (sector/local)      31 owners   3 email              sender: [principal]
  Segment C (categorical)       28 owners   3 email              sender: [principal]
  Segment D (no bridge)         12 owners   3 email + 1 letter   sender: [principal]

Compliance check:  passed on all 14
Voice check:       passed on all 14
Longest email:     114 words (limit 120)
Weakest segment:   D — honest but generic by design; expect the lowest
                   reply rate here

Signals backing segment A: all 22 traced to a quoted source URL

Drafts written to: outreach/
Nothing sent. Awaiting your approval.

Notes

  • If a segment A message will not write without inventing something, the company belongs in segment C. Drop the tier. Do not manufacture the bridge.
  • Shorter always wins. When a message will not fit, you are explaining rather than stating.
  • Say the word "selling." Owners respect directness. "Exploring strategic alternatives" is broker language and they know it.
  • Never write copy for a target with a warm path. Route the intro instead.
  • The user knows their market. If they rewrite your copy, learn the pattern and apply it to the rest rather than defending the draft.

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.