Agent Skills

firecrawl-lead-research

researchfirecrawl31K installs

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.

Install

npx skills add https://github.com/firecrawl/firecrawl-workflows --skill firecrawl-lead-research
SKILL.md

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.

Related skills

researchmattpocock575KInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.paper-context-resolverlllllllama451KRigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing Renv-and-assets-bootstraplllllllama450KRigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.ai-research-explorelllllllama311KRigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow c

Search skills and MCP servers

Fuzzy search across 23,137 skills and servers