mcpbeat

Firecrawl Lead Research

firecrawl/firecrawl-lead-research

Produce pre-meeting lead intelligence briefs with Firecrawl. Use when the user needs company research, person research, recent news, talking points, pain points, or outreach preparation before a sales call, partnership meeting, investor conversation, or customer interview.

579 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
110
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/firecrawl/firecrawl-workflows --skill firecrawl-lead-research

The instruction itself

6 sections, as written by the author

Firecrawl Lead Research

Use this to create a concise, actionable pre-meeting brief.

Onboarding Interview

Infer the company, person, meeting context, and desired brief depth from context. If the company is clear, proceed immediately.

Ask at most 1-3 concise questions only if blocked, such as the company/person to research or the meeting context.

Firecrawl Collection Plan

Use Firecrawl search and scrape to gather:

  • company website, about, product, pricing, careers, team, and customer pages
  • recent news, funding, launches, hiring, partnerships, and press
  • public person profiles, talks, posts, interviews, and role/background
  • relevant industry context and likely business challenges

Parallel Work

If appropriate, use sub-agents or equivalent parallel task runners:

  • Company Profile researcher
  • Recent News and Activity researcher
  • Person researcher
  • Industry/Pain Point researcher

Each researcher should return source URLs and only evidence-backed claims.

Final Deliverable

# Lead Brief: [Company]

## Company Overview
[What they do, stage/size signals, products, customers]

## Recent Activity
[News, launches, funding, hiring, partnerships]

## Key People
[Relevant people and public background]

## Talking Points
[5-7 specific conversation starters]

## Likely Pain Points
[Evidence-backed hypotheses]

## Outreach Angle
[Suggested positioning or next step]

## Sources
[URLs used]

## Rerun Inputs
workflow: firecrawl-lead-research
company: [name/url]
person: [optional]
context: [meeting context]

Quality Bar

  • Keep it concise and useful before a meeting.
  • Do not fabricate personal details.
  • Clearly separate facts from inferred pain points.

How to use it

Copy the folder

Take firecrawl/firecrawl-lead-research from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.