agentleFS
minhnv0807minhnv0807/ai-business-skills/skills/en/33-b2b-lead-gen-global/SKILL.md

33-b2b-lead-gen-global

Skill644 starsChanged 6 months agoMITView on GitHub

Use when the user needs B2B pipeline work — ICP and account lists, prospecting, cold email and LinkedIn outbound sequences, lead scoring, MQL to SQL handoff, sales decks, objection handling, demo scripts, CRM pipeline hygiene, and RevOps reporting. Trigger on 'find leads', 'prospect list', 'cold email sequence', 'outbound campaign', 'lead scoring model', 'our pipeline is empty', 'sales deck for enterprise buyers'. Also use when the user has a strong product and no route to the companies that need it. Not for — consumer lifecycle email, see `14-email-marketing-global`; the offer being sold, see `31-offer-design-global`; positioning against rivals, see `58-positioning-global`; inbound content, see `36-content-brief-global`.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Very specific:

    Read .agents/product-marketing-context-global.md if available.

    line 31
  2. Distinctive:

    Only push to outreach when score is at least 60/100.

    line 77
  3. Distinctive:

    Avoid spam, exaggerated claims, and fake personalization.

    line 88
  4. Distinctive:

    Every lead should have:

    line 102

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

B2B Lead Gen (Global)

This skill connects marketing to sales: define ICP, find accounts and contacts, score leads, write outreach, create sales assets, and set MQL/SQL handoff. The goal is qualified pipeline, not a large email list.

Information gathering

Read .agents/product-marketing-context-global.md if available. Ask up to 4 questions: ICP, deal size/ACV, target market/region, and current outbound channels. Use CRM exports or existing lists as baseline when available. For deeper guidance, read references/b2b-lead-gen-playbook.md.

Pick the mode

User needsMode
"Find prospects"Prospecting
"Write outreach emails"Cold outreach
"Score leads"Lead scoring
"Handoff to sales"RevOps handoff
"Build a sales deck / objections"Sales enablement

Workflow

1. Define ICP

Clarify:

  • Firmographic: industry, size, revenue, region.
  • Trigger: funding, hiring, expansion, tool usage, regulation, churn signal.
  • Pain: problem with budget behind it.
  • Exclusion: who should not be targeted.

2. Map lead sources

SourceBest for
LinkedIn/Sales NavB2B role/title targeting
Apollo/Clay/ZoomInfoAccount and contact data
Google Maps/local directoriesLocal SMB
GitHub/job postsDevtool/SaaS intent
G2/Capterra/review sitesCompetitor/category demand
Website visitors/formsWarm intent

3. Score and prioritize

Use 100 points:

GroupPoints
ICP fit35
Intent trigger25
Pain/proof15
Contact quality15
Timing10

Only push to outreach when score is at least 60/100.

4. Write outbound sequence

Default 4-touch sequence:

  1. Email 1: pain + relevance + soft CTA.
  2. Email 2: proof/case + short question.
  3. Email 3: value asset or mini-audit.
  4. Breakup: permission to close the loop.

Avoid spam, exaggerated claims, and fake personalization.

5. Create sales enablement

For high-potential accounts, create:

  • Persona-specific one-pager.
  • Objection handling sheet.
  • Demo talk track.
  • Simple ROI calculator.
  • Proposal outline.

6. Handoff to sales/CRM

Every lead should have:

  • Source, score, trigger, pain, suggested opener.
  • Owner, next step, follow-up SLA.
  • Status: New, Working, Meeting Booked, SQL, Opportunity, Closed.

Output template

# B2B Lead Gen Plan — [Brand]

## 1. ICP
| Segment | Fit criteria | Pain | Exclusion |

## 2. Lead sources
| Source | Query/filter | Data needed | Owner |

## 3. Scoring model
| Signal | Points | Why it matters |

## 4. Prospect table
| Account | Contact | Trigger | Score | Suggested opener | Next step |

## 5. Outreach sequence
### Email 1
Subject:
Body:

### Follow-ups

## 6. Sales enablement assets
| Asset | Persona | Purpose | Draft notes |

## 7. CRM handoff
| Stage | Entry criteria | Owner | SLA |

Related skills

  • 09-customer-insight-global: persona, pain, JTBD.
  • 31-offer-design-global: B2B/high-ticket offer.
  • 14-email-marketing-global: nurture after capture.
  • 08-competitor-research-global: competitor triggers and alternative positioning.

Quality checklist

  • Lead list includes reasons to buy, not just emails.
  • Exclusion criteria are explicit.
  • Outreach has real relevance, not fake merge-field personalization.
  • Compliance: opt-out, no unlawful scraping or spam.
  • Sales handoff has owner and SLA.
  • Output has a clear 48-hour next action.

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.