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
- Distinctive: line 21
If the task type is ambiguous, ask once.
- Distinctive: line 25
All playbooks depend on a company profile: who is sending, what the company offers, which proof points are approved.
- Very specific: line 29
If neither exists, offer the template in assets/company-profile-template.md and ask the user to fill the minimum fields (sender name, …
- Distinctive: line 33
Language & locale: Write in the language of the target market/recipient, not necessarily the user's language.
- Distinctive: line 34
No invented facts: Never fabricate numbers, savings, deadlines, regulations, customer names, or references.
- Distinctive: line 36
Respect and compliance: Never insult the reader or disparage competitors.
≈ “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.
Files
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:
| Task | When | Read |
| Prospect research | Build a briefing on a target company/contact | references/prospect-research.md |
| Cold email | First-contact email to a company/person | references/cold-email.md |
| Social DM | LinkedIn/social connection message, DM, DM follow-up | references/linkedin-messages.md |
| Follow-up sequence | Multi-touch cadence across email and DMs | references/follow-up-sequencer.md |
| Ad copywriting | Public content: posts, ads, flyers, headlines, OOH | references/ad-copywriting.md |
| Objection handling | Prospect pushes back and a reply is needed | references/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:
- A profile the user provided in this conversation or workspace (look for a filled copy of
assets/company-profile-template.mdor equivalent briefing). - Facts the user states inline.
- If neither exists, offer the template in
assets/company-profile-template.mdand 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.
In this repository199 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- accessibility-passSkill
- acroform-writerSkill
- action-items-todoSkill
- agent-evaluation-designerSkill
- agent-harness-explorerSkill
- agent-performance-triageSkill
- agent-red-teamSkill
- ai-demo-assistantSkill
- ai-first-process-redesignSkill
- ai-usecase-assessmentSkill
- anonymised-case-study-writerSkill
- evidence-gatherSkill
- gap-checkSkill
- readiness-packSkill
- scope-mapSkill
- blog-content-auditorSkill
- blog-post-structure-passSkill
- booth-loop-videoSkill
- brand-template-enforcerSkill
- brand-voice-passSkill
- breathing-roomSkill
- browser-uat-analystSkill
- business-osSkill
- call-for-speakers-digestSkill
- campaign-deck-builderSkill
- chart-builderSkill
- classic-text-adventureSkill
- clipchamp-videoSkill
- clt-hr-assistantSkill
- commenting-contentSkill
- competitive-battlecard-builderSkill
- conditional-chat-reminderSkill
- conference-session-abstract-packSkill
- contradiction-flagSkill
- insight-briefSkill
- provenance-checkSkill
- research-retrieveSkill
- trend-compareSkill
- content-quality-auditorSkill
- copilot-agent-advisorSkill
- copilot-studio-adaptive-card-builderSkill
- copilot-studio-agent-testSkill
- copilot-studio-harness-pickerSkill
- copilot-studio-knowledge-readinessSkill
- copilot-studio-mcp-readinessSkill
- copilot-studio-topic-blueprintSkill
- cowork-plugin-engineerSkill
- cowork-use-case-one-pagerSkill
- create-copilot-adoption-dashboardSkill
- context-assembleSkill
- handoff-packetSkill
- inquiry-intakeSkill
- knowledge-retrieveSkill
- resolution-draftSkill
- doc-format-converterSkill
- bom-impactSkill
- ecn-draftSkill
- ecr-ingestSkill
- standards-checkSkill
- The first 60 shown.
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
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.

