본문으로 건너뛰기
cccskills
무료GitHub에 공개

firecrawl-deep-research

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 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 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:

# 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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

firecrawl

무료

Any live-web task via the Firecrawl CLI — including ordinary web research: searching the web, reading or extracting pages, gathering sources, discovering site URLs, bulk extraction, downloading a site, change alerts, or pages needing clicks/login — web only; local files route to firecrawl-parse. For US legal or regulatory questions use gov; for papers use firecrawl-research-index; for library, API, error, or bug questions use firecrawl-developer-index.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

firecrawl/skills1312026년 10월 19일 업데이트

Autonomously navigate websites and extract structured data across pages. Use when the task requires navigation or no suitable ready-made workflow or data provider covers it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

firecrawl/skills1312026년 10월 19일 업데이트

Find a direct path to structured data through ready-made workflows, data APIs, and indexes. Follow the search skill to discover and inspect tools, then the scrape skill to execute them.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

firecrawl/skills1312026년 10월 19일 업데이트

Find the published business contacts of companies with Firecrawl, whether the user names them or describes them by type and place: press and media, sales, partnerships and support inboxes, shared business phone numbers and official contact forms, taken from the companies' own websites. Use when the user asks how to contact a company or wants published business emails, phone numbers or press, sales, support or partnership contacts, since contact pages change and an address must come from the page, not memory. Not for named people's details (use firecrawl-lead-research) or finding people to reach out to (use firecrawl-lead-gen).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

firecrawl/skills1312026년 10월 19일 업데이트

Extract structured company lists with Firecrawl from any page or site that lists companies: accelerator batches, VC portfolios, member and sponsor lists, marketplaces and app directories, YC, Crunchbase, Product Hunt or G2. Use when the user wants those companies as a CSV, JSON, CRM-ready list or research table, even without an explicit request to scrape.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

firecrawl/skills1312026년 10월 19일 업데이트

Monitor competitor pricing, features, changelogs, dashboards, and product changes with Firecrawl. Use for recurring competitive intelligence, pricing tier extraction, feature change tracking, or structured competitor alerts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

firecrawl/skills1312026년 10월 19일 업데이트

firecrawl의 스킬 모두 보기

이 스킬의 문제 신고