AGENT SKILL

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.

License 许可
ISC
所属仓库
Davshiv20/dotfiles
最近更新
2026-11-11
Stars
★ 0
Forks
0

01 前言 Front Matter

name
firecrawl-deep-research
inputs
[ { "name": "FIRECRAWL_API_KEY", "required": true, "description": "Firecrawl API key for hosted Firecrawl requests." } ]
license
ISC
metadata
{ "author": "firecrawl", "source": "https://github.com/firecrawl/firecrawl-workflows", "version": "0.1.0", "homepage": "https://www.firecrawl.dev" }
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.

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

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.

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.

04 同仓库更多 Skills

Davshiv20
Davshiv20/dotfiles

firecrawl-workflows

Run outcome-focused Firecrawl workflows that produce deliverables such as research reports, SEO audits, QA reports, lead lists, knowledge bases, website design systems, and other structured web-data artifacts. Use when the user wants Firecrawl to complete a business, marketing, product, or creative workflow rather than merely scrape a page or integrate API calls into code.

★ 0
Davshiv20
Davshiv20/dotfiles

firecrawl-website-design-clone

Extract any website's design system into an agent-ready DESIGN.md using Firecrawl scrape evidence. Use when the user wants colors, fonts, spacing, components, layout patterns, or brand/UI guidance from a website so AI agents can create new websites, clone a look, or build pages inspired by that design.

★ 0
Davshiv20
Davshiv20/dotfiles

firecrawl-shop

Research products across the web with Firecrawl and produce a shopping recommendation or cart-ready summary. Use when the user wants to compare products, find the best option, evaluate reviews, respect budget/preferences, or shop with a saved browser session.

★ 0
Davshiv20
Davshiv20/dotfiles

firecrawl-seo-audit

Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and heading review, sitemap/site-structure analysis, keyword opportunities, competitor SERP comparison, or prioritized search optimization recommendations.

★ 0
Davshiv20
Davshiv20/dotfiles

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.

★ 0
Davshiv20
Davshiv20/dotfiles

firecrawl-qa

QA test a live website with Firecrawl browser and scrape evidence. Use when the user wants exploratory QA, form testing, navigation/link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.

★ 0