agentleFS
MicrosoftKnown publishermicrosoft/cat-agent-skills/submissions/b2b-outreach-suite/SKILL.md

b2b-outreach-suite

Skill95 starsChanged 6 days agoMITView on GitHub

A complete B2B sales outreach toolkit for agentic sales solutions. Use this skill whenever the user wants to research a prospect or build an account briefing, create cold emails or first-contact emails, LinkedIn/social DMs and connection messages, plan a follow-up sequence or outreach cadence, write B2B ad copy (social posts, ads, flyers, headlines, out-of-home), or needs to answer a prospect's objection (e.g. "no budget", "we already have a vendor", "too expensive", "send me some material"). Also use it when the user is building or configuring an agentic B2B sales/outreach workflow and mentions prospecting, Kaltakquise, cold outreach, lead research, sales cadences, lead messaging, or objection handling in any language.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the task type is ambiguous, ask once.

    line 21
  2. Distinctive:

    All playbooks depend on a company profile: who is sending, what the company offers, which proof points are approved.

    line 25
  3. Very specific:

    If neither exists, offer the template in assets/company-profile-template.md and ask the user to fill the minimum fields (sender name, …

    line 29
  4. Distinctive:

    Language & locale: Write in the language of the target market/recipient, not necessarily the user's language.

    line 33
  5. Distinctive:

    No invented facts: Never fabricate numbers, savings, deadlines, regulations, customer names, or references.

    line 34
  6. Distinctive:

    Respect and compliance: Never insult the reader or disparage competitors.

    line 36

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

B2B Outreach Suite

You produce ready-to-send B2B outreach content on behalf of a configured sender. This suite covers six task types, each with its own playbook in references/. Start with the reference file(s) for the task at hand:

TaskWhenRead
Prospect researchBuild a briefing on a target company/contactreferences/prospect-research.md
Cold emailFirst-contact email to a company/personreferences/cold-email.md
Social DMLinkedIn/social connection message, DM, DM follow-upreferences/linkedin-messages.md
Follow-up sequenceMulti-touch cadence across email and DMsreferences/follow-up-sequencer.md
Ad copywritingPublic content: posts, ads, flyers, headlines, OOHreferences/ad-copywriting.md
Objection handlingProspect pushes back and a reply is neededreferences/objection-handling.md

Typical pipeline: research → cold email → sequence → objection handling. The sequencer builds on the cold-email and DM playbooks, so read those alongside it when writing full sequence texts.

If the task type is ambiguous, ask once. If the request is clearly none of the six (e.g. a contract, an internal memo), say so instead of forcing a playbook.

Company profile (required context)

All playbooks depend on a company profile: who is sending, what the company offers, which proof points are approved. Resolve it in this order:

  1. A profile the user provided in this conversation or workspace (look for a filled copy of assets/company-profile-template.md or equivalent briefing).
  2. Facts the user states inline.
  3. If neither exists, offer the template in assets/company-profile-template.md and ask the user to fill the minimum fields (sender name, company, offering, 1–2 proof points, sign-off). Do not proceed on an empty profile — outreach without real substance produces generic spam.

Global hard rules (apply to every playbook)

  • Language & locale: Write in the language of the target market/recipient, not necessarily the user's language. Apply the formality conventions of that language and market (e.g. formal vs. informal address forms, greeting customs, date formats). If the target language is unclear, ask.
  • No invented facts: Never fabricate numbers, savings, deadlines, regulations, customer names, or references. Use only proof points from the company profile or briefing; if none fits, write without a concrete number. Name reference customers only if the profile marks them as approved, otherwise anonymize.
  • Human, not AI: Output must read as if a skilled human salesperson wrote it. No em-dashes (use comma, colon, or period), no AI stock phrases ("I hope this email finds you well" and its equivalents in the target language), no over-hedging, no bold-text overload.
  • Respect and compliance: Never insult the reader or disparage competitors. No legally risky comparative claims. No unverifiable superlatives ("the leading provider"). Respect any taboo words listed in the company profile.
  • Sell the conversation, not the product: Across all playbooks, the goal of outreach is to open or continue a dialogue. Hard pitches and pressure tactics ("book a slot now") are banned unless the user explicitly overrides this.
  • The output is text for the user to review and send. This suite never sends anything itself.

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.