firecrawl-research-index
Find the papers that answer a research query in Firecrawl's research paper index — a corpus of paper abstracts whose largest share is biomedical and life-science literature (PubMed, bioRxiv, medRxiv), alongside arXiv preprints in CS, physics, and math — using semantic search, semantic and structural…
Install / Use
npx skills add firecrawl/cli --skill firecrawl-research-indexInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Education & ResearchSupported Platforms
Tags
Our assessment of firecrawl-research-index
firecrawl-research-index scores 81/100 on our quality scale, 374th of 421 Education & Research skills we index.
Its SKILL.md is 9.5 KB long, split into 6 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 639 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so firecrawl-research-index is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
firecrawl-research-index compared with similar skills
All 4 of these similar skills score higher than firecrawl-research-index; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| firecrawl-research-index (this skill)by firecrawl | 81 | 639 | 55d ago | SKILL.md |
| last30days-skillby mvanhorn | 100 | 68.8k | today | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
Frequently asked questions
- How do I install firecrawl-research-index?
- Run
npx skills add firecrawl/cli --skill firecrawl-research-index. The install tabs above show the steps for each supported agent. - Which AI agents does firecrawl-research-index work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is firecrawl-research-index safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is firecrawl-research-index still maintained?
- The repository was last updated about 2 months ago, so firecrawl-research-index is actively maintained.
Skill content
View source on GitHubname: firecrawl-research-index
description: Find the papers that answer a research query in Firecrawl's research paper index — a corpus of paper abstracts whose largest share is biomedical and life-science literature (PubMed, bioRxiv, medRxiv), alongside arXiv preprints in CS, physics, and math — using semantic search, semantic and structural expansion, and in-body verification. Use this skill for literature-finding and paper-retrieval tasks of any kind, including clinical, biomedical, drug, gene, disease, and other life-science questions, whether the answer is a single paper or a full multi-paper set. The index is reached only through the firecrawl_research_* MCP tools or the firecrawl research CLI subcommands. Calling firecrawl_search with its categories option set to ["research"] is a different feature — it filters ordinary web search to research-affiliated websites (the list includes PubMed, bioRxiv, medRxiv, arXiv, and publisher sites) and returns page results from them, without querying the paper records in this index.
Firecrawl Research Index
Find the research papers that answer a research query. Some questions have a single answer; many have several — and when in doubt, lean toward returning the fuller relevant set (most relevant first) rather than narrowing to one. A reader is better served seeing the neighboring methods and papers than having them silently dropped.
What is in the index
Paper abstracts, with full text reachable per paper. The largest share of the corpus is biomedical and life-science literature — PubMed journal articles plus bioRxiv and medRxiv preprints — so clinical, drug, gene, disease, epidemiology, and public-health questions are in scope. arXiv preprints cover computer science, physics, and mathematics. Coverage outside those sources is thinner: a paper that exists only behind a publisher paywall or in a niche venue may not be indexed, and the general web tools below are the fallback when it isn't.
There is no fixed recipe. Read the query, decide what kind it is, and choose the approach below. Some queries need a single search; others need heavy structural/semantic expansion. Don't run machinery a query doesn't call for.
The tools, and what each is uniquely good at
-
MCP:
firecrawl_research_search_papers(query, k?)CLI:firecrawl research search-papers <query> [--k <number>]Semantic (HyDE) search over abstracts. The natural first move for almost any query. If results look thin or all-alike, re-run with a different framing (sibling domain, rival method, dataset/benchmark name) rather than giving up. -
MCP:
firecrawl_research_related_papers(seed_ids, intent, mode?, k?)CLI:firecrawl research related-papers <seedIds...> --intent <intent> [--mode <similar|citers|references>] [--k <number>]Semantic and structural expansion, ranked to yourintent. This reaches papers semantic search cannot, and it's how you turn one good hit into the rest of a set.mode=similar→ niche siblings;citers→ who uses/builds on the seeds;references→ what they build on / compare against. -
MCP:
firecrawl_research_inspect_paper(id)CLI:firecrawl research inspect-paper <id>Canonical metadata for one paper: title, abstract, authors, categories, source ids, and dates. Use it aftersearch_papersorrelated_paperswhen you need the complete citation/metadata for a candidate, or when you have an id from elsewhere and need to confirm what paper it resolves to. This does not read the paper body; useread_paperfor specific full-text questions. -
MCP:
firecrawl_research_read_paper(id, question)CLI:firecrawl research read-paper <id> --question <question>In-body passages of one paper, to verify a load-bearing constraint (a method actually used, a score actually reported, an affiliation, what a paper compares to). Use it to settle a specific doubt, not on everything. -
MCP:
firecrawl_search(query, categories: ["research"])CLI:firecrawl search <query> --categories researchNot this index. This is a website filter: it restricts a normal web search to a short list of research-affiliated domains — the list does includepubmed.ncbi.nlm.nih.gov,biorxiv.org,medrxiv.org, andarxiv.orgalongside publisher sites — and returns page results in aresearchgroup besideweb, each withurl,title,description(the matched passage),position, andcategory: "research"— web results carry nocategory, so that is the field to key on when merging. So it reaches those sites' web pages; what it does not do is query their paper records in this index — no semantic search over abstracts, no citation-graph or related-paper expansion, no canonical paper metadata, and no in-body passages. The results are ordinary web results. Use it when you are already running a web search and want those sites weighed in the same call. For anything that is actually a paper-finding task, usefirecrawl_research_search_papersand its siblings above. -
MCP:
firecrawl_search(query)/firecrawl_scrape(url)CLI:firecrawl search <query>/firecrawl scrape <url>General web search and page fetch, for facts that don't live in paper abstracts: benchmark leaderboards, rankings, "who scores best / is largest / is most used." Find the ranking on the web, then map the top entries back to papers withsearch_papers. Reach for these only when the corpus can't answer the question on its own.
Match the approach to the query
- Single named paper ("the Qwen3 report") → one
search_papers, done. This is the only case that truly wants exactly one paper. - Paper by description / by method or technique ("the paper that introduced X", "training-free N-gram detection of AI text") → find the best match, then assume there's a family: expand with
related_papersand include the closely-related methods/papers too. Even when one paper is the exact literal match, surface and keep its neighbors — don't narrow to the single best hit and reason the rest out. Only treat it as one-answer if the query names a specific paper. - Enumeration / method-family ("papers that do X", "alternatives to Adam", "benchmarks for Y") → the answer is a set, and this is where
related_papersearns its keep: expand several strong anchors withmode=similar, re-seed from new strong hits. One search is never enough here. - Exhibiting ("papers that use / exhibit property P") → the relevant papers apply P but their abstracts may not describe it. Go from P's defining paper outward via
citers/references, and useread_paperto confirm a candidate actually uses P. - Superlative / leaderboard ("best on benchmark X", "largest", "most popular") → the ranking lives on leaderboards / the web, not in any single abstract. Use
firecrawl_search/firecrawl_scrapeto find the benchmark's leaderboard or rankings, read off the top models/papers, thensearch_paperseach to get its paper. As a fallback, search the benchmark andread_papercandidates for reported numbers. The hardest kind — cast wide. - Org / author filtered ("from <org>", "by <author>") → topical match isn't enough; verify the affiliation/authorship (metadata or
read_paper) before keeping a paper. - Compare-against ("what does paper X benchmark against / build on") → the answer is inside paper X:
read_paper(X, ...)orrelated_papers([X], ..., mode="references").
Principles
- Two different features share the word "research." The paper index is
firecrawl_research_*/firecrawl research. Thecategories: ["research"]option onfirecrawl_searchis a website filter — it does point web search at PubMed, bioRxiv, medRxiv, arXiv, and publisher sites, but what comes back is their web pages, not paper records. If a task is about finding papers, the tools in this skill are the ones that read the corpus; reaching forcategories: ["research"]will quietly answer a different question. - Query shape and subject field are separate. A clinical-trial question and a machine-learning question take the same shapes above; what differs is only which source the hits come from. Don't send a biomedical or life-science query to the open web on the assumption the corpus is arXiv-only — PubMed, bioRxiv, and medRxiv are the largest part of what
search_papersreads. - When in doubt, include. For any topic / method / comparison question, return the relevant family, not just the single best match — err toward keeping a plausibly-relevant paper rather than dropping it. The neighboring methods are part of a good answer; don't reason close work out just because one paper is the most exact match.
- Follow the literature, and keep what you find. The seminal source, the competing methods, the close neighbors are usually a hop away — use
related_papers, and include them, not just the first hit. Stopping at one good result is the most common way to leave the reader with half an answer. - Verify to exclude, not to gatekeep. Use
read_paperto rule a paper out when a hard constraint clearly fails (wrong org/author, doesn't actually report the score). When a paper is plausibly relevant, lean toward keeping it rather than demanding proof. - Only drop the clearly off-topic. Don't pad with papers you're confident are unrelated — but that's a high bar; most plausibly-relevant work should make the cut.
See also
- firecrawl-build-search — building the paper index into an app instead of querying it here
Related Skills
last30days-skill
68.8kAI agent skill that researches any topic across Reddit, X, YouTube, HN, Polymarket, and the web - then synthesizes a grounded summary
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
