firecrawl-deep-research — Claude Code skill: cited research reports
Turns a hard topic into a cited analytical report: it gathers sources from the open web with Firecrawl, works several angles and links the evidence.
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-deep-research -a claude-codeWhat firecrawl-deep-research does
This skill handles research at report scale. It searches and scrapes pages through Firecrawl, then writes a document with an executive summary, key findings, a detailed analysis, contrarian views, open questions and a source list crediting each URL with a one-line note.
Before starting it asks one short question: how long should the task run? The answer sets the tier. A few minutes buys 3-5 queries and 5-10 sources. Around 10-15 minutes buys 5-10 queries from different angles and 15-25 sources. With no limit it runs 10+ queries and 25+ sources, pulling in primary material and opposing views. Collection can be split across sub-agents by angle: overview, technical detail, market context, risks, official docs. Each one reports claims, URLs, source quality and what it could not confirm.
A required FIRECRAWL_API_KEY for hosted requests is the first thing to sort out. The other trap is scope. When the evidence base is published papers, this skill is the wrong door and hands the job to firecrawl-research-papers, which queries the paper index covering PubMed, bioRxiv, medRxiv and arXiv. Passing categories: ["research"] to Firecrawl search does not reach that index, it only narrows ordinary web results to research sites. Worth checking where you expect the facts to come from.
What it helps with
- gather sources across several angles without losing the links
- surface contrarian views and open questions in a topic
- write a formal report instead of a top-N list
- trace each claim back to the source it came from
- mark what is still uncertain before anyone acts on it
Example prompts for the agent
- Run a deep research report on EU rules for open-source models, take as long as you need
- I need a cited analysis of data-centre power demand, with contrarian views, about 15 minutes
- Research the inference chip market properly and give me a markdown report
How to install firecrawl-deep-research
1Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-deep-research -a claude-code2Manually: put the files in place
~/.claude/skills/firecrawl-deep-research/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/firecrawl-deep-research/
1Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-deep-research -a codex2Manually: put the files in place
.agents/skills/firecrawl-deep-research/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-deep-research -a cursor2Manually: put the files in place
.cursor/skills/firecrawl-deep-research/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install firecrawl/firecrawl-workflows firecrawl-deep-research2Manually: put the files in place
.github/skills/firecrawl-deep-research/SKILL.md1Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-deep-research -a gemini-cli2Platform CLI
gemini skills install https://github.com/firecrawl/firecrawl-workflows --path skills/firecrawl-deep-researchManually: put the files in place
.devin/skills/firecrawl-deep-research/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-deep-research -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about firecrawl-deep-research
How to install firecrawl-deep-research in Claude Code
Run npx skills add firecrawl/firecrawl-workflows --skill firecrawl-deep-research -a claude-code. The skill file lands at ~/.claude/skills/firecrawl-deep-research/SKILL.md.
What does firecrawl-deep-research do?
It collects evidence from the open web through Firecrawl and writes a cited report: summary, findings, analysis, contrarian views and the full source list.
What do I need for it to work?
A FIRECRAWL_API_KEY for Firecrawl requests, and it is a required field. Search and scraping both go through that service.
Source text
SKILL.md · ISC
---
name: firecrawl-deep-research
description: |
Produce an intensive, cited analytical report: executive summary, multi-angle
findings, contrarian views, open questions, and full sources. Use only when the
user needs rigorous synthesis of a complex topic (scientific, technical, policy,
or market-analytical) that cannot be answered with a short search, and wants
a formal written report, not a recommendation list.
Do not use for product picks, top-N lists, quick lookups, or routine "find out
about X" tasks. If the request does not clearly need this kind of report, do
not use this skill.
Do not use for a literature review over published papers. This skill collects
evidence from the open web. A request for the literature on a biomedical,
clinical, life-science, or other scientific topic — papers, studies, trials,
preprints — belongs to firecrawl-research-papers, which queries Firecrawl's
paper index (PubMed, bioRxiv, medRxiv, arXiv) instead of searching websites.
license: ISC
metadata:
author: firecrawl
version: "0.1.0"
homepage: https://www.firecrawl.dev
source: https://github.com/firecrawl/firecrawl-workflows
inputs:
- name: FIRECRAWL_API_KEY
description: Firecrawl API key for hosted Firecrawl requests.
required: true
---
# Firecrawl Deep Research
Use this only for report-scale research: a rigorous, cited synthesis the user
explicitly wants delivered as a formal written report. If the request is a
product pick, a top-N list, a quick lookup, or anything answerable with a short
search, stop; do not use this skill, let the request be handled the standard
way.
This skill gathers its evidence from the open web. If the evidence base is the
published literature — a literature review, or a biomedical, clinical, or other
scientific topic where the answer lives in papers — use
[firecrawl-research-papers](../firecrawl-research-papers/SKILL.md) instead; it
queries Firecrawl's paper index rather than searching websites.
## Onboarding Interview
Infer the topic and output format from context. Before starting, unless already specified, always ask one short question to define the scope:
> "How long do you want this research task to run?"
Map the answer to a depth tier in the Collection Plan below:
- A few minutes → Quick
- ~10-15 minutes → Thorough
- Longer / no limit → Exhaustive
If the topic itself is unclear, you may ask at most 1-2 additional concise
questions (topic, or a critical angle/source constraint). Otherwise proceed once
the runtime is set.
## Firecrawl Collection Plan
Use Firecrawl search and scrape through the CLI or equivalent tool surface. Match
depth to the runtime the user chose during onboarding.
- Quick (~a few minutes): search 3-5 queries and scrape 5-10 high-quality sources.
- Thorough (~10-15 minutes): search 5-10 queries from different angles and scrape 15-25 sources.
- Exhaustive (longer): search 10+ queries and scrape 25+ sources, including primary sources, research papers, expert views, and contrarian sources.
Avoid re-scraping URLs already returned with full content from a search-with-scrape result.
### When Published Papers Are The Evidence
Search and scrape reach web pages. They do not query Firecrawl's research paper
index, which holds paper abstracts with full text reachable per paper — largely
biomedical and life-science literature from PubMed, bioRxiv, and medRxiv, plus
arXiv preprints in CS, physics, and math.
Hand off to [firecrawl-research-papers](../firecrawl-research-papers/SKILL.md)
when the report's evidence base is the published literature — a biomedical,
clinical, drug, gene, disease, epidemiology, or public-health topic, or any
request phrased as a literature review, systematic review, or survey of studies.
That skill uses `firecrawl_research_*` (MCP) / `firecrawl research` (CLI) to
search abstracts, expand to related papers, and verify claims inside a paper
body — none of which plain search and scrape can do.
If the report needs both — the literature *and* market, policy, or news context —
run the paper work through that skill and keep the web collection above for the
rest, then synthesize here.
Note that passing `categories: ["research"]` to Firecrawl search does not query
the paper index either. It filters an ordinary web search to research-affiliated
websites — the list includes PubMed, bioRxiv, medRxiv, arXiv, and publisher
sites — and returns their web pages, not the paper records behind them.
## Parallel Work
If appropriate, use sub-agents or equivalent parallel task runners by research angle:
- overview and definitions
- technical or implementation details
- market and industry context
- contrarian views, risks, and limitations
- primary sources and official docs
Each researcher should return claims, source URLs, source quality notes, and uncertainty.
## Final Deliverable
Default structure:
```markdown
# Deep Research: [Topic]
## Executive Summary
[2-3 paragraphs]
## Key Findings
[Numbered findings with source links]
## Detailed Analysis
[Themes, evidence, and synthesis]
## Contrarian Views And Risks
[Counterarguments, limitations, failure modes]
## Open Questions
[What remains uncertain]
## Sources
[Every URL used with a one-line note]
## Rerun Inputs
workflow: firecrawl-deep-research
topic: [topic]
depth: [quick/thorough/exhaustive]
output: [markdown/json/brief]
```
## Quality Bar
- Cite sources for factual claims.
- Prefer primary sources when available.
- Flag uncertainty and conflicting evidence.
- Synthesize instead of listing scrape summaries.
© firecrawl · ISC · firecrawl/firecrawl-workflows