Pesquisa aprofundada e citada com Firecrawl

O que esta skill faz

Esta skill atende pesquisas científicas, técnicas, regulatórias ou de mercado que exigem coleta e síntese rigorosas. Antes de começar, define o tempo disponível e converte essa resposta em profundidade quick, thorough ou exhaustive.

Quando usar

• Produzir um relatório técnico aprofundado
• Sintetizar um tema científico complexo
• Analisar uma questão de políticas públicas
• Construir uma análise formal de mercado
• Apresentar visões contrárias e lacunas

Como usar

1. Defina o tema e o formato esperado do relatório
2. Informe quanto tempo a pesquisa pode consumir
3. Esclareça ângulos ou restrições de fontes se necessário
4. Configure FIRECRAWL_API_KEY
5. Colete, confronte e cite as fontes no relatório

O que revisar antes de instalar

• Não deve ser usada para consultas rápidas ou listas de produtos
• Requer FIRECRAWL_API_KEY
• O tempo escolhido limita a profundidade da coleta
• As fontes ainda precisam ser avaliadas criticamente

SKILL.md

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

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

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