Help us improve
Share bugs, ideas, or general feedback.
From Firecrawl Workflows
Produces rigorous, cited analytical reports on complex topics (scientific, technical, policy, market) with executive summary, multi-angle findings, contrarian views, and full sources. Not for quick lookups or recommendations.
npx claudepluginhub firecrawl/firecrawl-workflows --plugin firecrawl-workflowsHow this skill is triggered — by the user, by Claude, or both
Slash command
/firecrawl-workflows:firecrawl-deep-researchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this only for report-scale research: a rigorous, cited synthesis the user
Runs deep research on topics via web searches, data collection, source verification, synthesis, and structured reports saved to 02-research/. Use for reports, blogs, or exploring new domains beyond quick answers.
Multi-source deep research using firecrawl and exa MCPs to search, scrape, and synthesize cited reports with source attribution. Use for in-depth topic exploration.
Conducts deep research via parallel web searches, multi-source validation, and confidence tracking across 11 types like market, competitive, technical; outputs cited Markdown reports.
Share bugs, ideas, or general feedback.
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.
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:
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.
Use Firecrawl search and scrape through the CLI or equivalent tool surface. Match depth to the runtime the user chose during onboarding.
Avoid re-scraping URLs already returned with full content from a search-with-scrape result.
If appropriate, use sub-agents or equivalent parallel task runners by research angle:
Each researcher should return claims, source URLs, source quality notes, and uncertainty.
Default structure:
# 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]