
firecrawl-research-papers
Find and synthesize research papers, whitepapers, PDFs, technical reports, and academic sources with Firecrawl Research, using semantic paper search, related-paper expansion, and in-body verification. Use when the user wants a literature review, paper summary, research landscape, or sourced synthesis from PDFs and scholarly/industry publications.
Firecrawl API key for hosted Firecrawl Research, CLI, MCP, or equivalent tool requests.
Firecrawl Research Papers
Use this to create a sourced literature review.
Onboarding Interview
Infer the topic, source constraints, target count, and output format from context. If the topic is clear, proceed immediately.
Ask at most 1-3 concise questions only if blocked, such as the topic, target paper count, or required venue/date/method constraints.
Firecrawl Collection Plan
Use Firecrawl Research through the CLI, MCP, or equivalent Firecrawl tool
surface as the primary path for paper discovery and verification. Fall back to
general Firecrawl search and scrape for whitepapers, technical reports,
research blogs, leaderboards, or facts outside the paper corpus.
Core tools:
- MCP:
firecrawl_research_search_papers(query, k?)
CLI:firecrawl research search-papers <query> [--k <number>]
Semantic search over paper abstracts. Start here for most paper-finding
queries, and retry with alternate framing when results are thin or too
narrow. - MCP:
firecrawl_research_related_papers(seed_ids, intent, mode?, k?)
CLI:firecrawl research related-papers <seedIds...> --intent <intent> [--mode <similar|citers|references>] [--k <number>]
Expand from strong seed papers into similar work, citing papers, or
references. Use this to find the relevant paper family, not just the first
matching result. - MCP:
firecrawl_research_inspect_paper(id)
CLI:firecrawl research inspect-paper <id>
Fetch canonical metadata for a candidate paper: title, abstract, authors,
categories, source ids, and dates. - MCP:
firecrawl_research_read_paper(id, question)
CLI:firecrawl research read-paper <id> --question <question>
Verify a specific claim or constraint inside one paper, such as method,
reported score, benchmark, affiliation, comparison, or limitation. - MCP:
firecrawl_search(query)/firecrawl_scrape(url)
CLI:firecrawl search <query>/firecrawl scrape <url>
Use for web-only context: benchmark leaderboards, rankings, reports,
whitepapers, research blogs, and source pages outside the paper index.
Match the approach to the query:
- Single named paper: run one paper search, then inspect or read the paper if
metadata or body verification is needed. - Paper by description, method, or topic family: search for strong anchors,
then expand with related papers and keep close neighbors. - Enumeration queries, such as papers that do a task or benchmark a method:
search multiple framings, expand several strong anchors, and re-seed from
newly found relevant papers. - Papers that use or exhibit a property: start from the defining paper or
strongest anchor, expand via similar, citers, or references, and use
read-paper to verify the property. - Superlatives and leaderboards: use general web search or scrape to find the
ranking, then map top entries back to papers with paper search. - Author, organization, venue, date, or methodology constraints: verify with
inspect-paper metadata or read-paper before keeping a candidate.
Target source types:
- academic papers from arXiv, university sites, ACM/IEEE pages where accessible
- industry reports and whitepapers
- company research blogs
- technical articles and conference summaries
Principles:
- When in doubt, include the relevant paper family rather than only the single
best result. - Use related-paper expansion to avoid stopping at one strong hit.
- Use read-paper to verify load-bearing constraints, not to summarize every
candidate. - Drop only clearly off-topic papers.
Parallel Work
If appropriate, use sub-agents or equivalent parallel task runners:
- Academic Papers researcher
- Industry Reports researcher
- Technical Articles researcher
- Synthesis and citation reviewer
Final Deliverable
# Literature Review: [Topic]
## Abstract
[2-3 paragraph summary]
## Key Papers
[Title, authors, source URL, key findings, methodology, relevance]
## Themes And Consensus
[What sources agree on]
## Open Questions And Debates
[Disagreements and unresolved questions]
## Emerging Trends
[Recent developments]
## Sources
[Organized by paper/report/article]
## Rerun Inputs
workflow: firecrawl-research-papers
topic: [topic]
target_count: [number]
output: [markdown/brief]
Quality Bar
- Every major claim should trace to a source.
- Note inaccessible or failed PDFs.
- Distinguish peer-reviewed work from blogs and vendor reports.
You Might Also Like
Related Skills

summarize
Summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files.
steipete
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
obra
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
anthropics
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
anthropics
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
anthropics