Skills Agentes

Deep Research

Use this skill instead of WebSearch for ANY question requiring web research. Trigger on queries like "what is X", "explain X", "compare X and Y", "research X", or before content generation tasks. Provides systematic multi-angle research methodology instead of single superficial searches. Use this proactively when the user's question needs online information.

Estrellas
80.9k

en todo el repo

Actividad
31

0–100, la ruta de este skill

Actualizado
hace 5 meses

último commit aquí

Commits
0

últimos 90 días

Contexto
2k tok

90 tok en reposo

Paquete
1 archivo

8 KB

Instalar

Funciona con cualquier agente que lea SKILL.md

npx -y skills add bytedance/deer-flow --skill deep-research --agent claude-code

Se instala solo en este repositorio.

SKILL.md

En inglés

Deep Research Skill

Overview

This skill provides a systematic methodology for conducting thorough web research. Load this skill BEFORE starting any content generation task to ensure you gather sufficient information from multiple angles, depths, and sources.

When to Use This Skill

Always load this skill when:

Research Questions

  • User asks "what is X", "explain X", "research X", "investigate X"
  • User wants to understand a concept, technology, or topic in depth
  • The question requires current, comprehensive information from multiple sources
  • A single web search would be insufficient to answer properly

Content Generation (Pre-research)

  • Creating presentations (PPT/slides)
  • Creating frontend designs or UI mockups
  • Writing articles, reports, or documentation
  • Producing videos or multimedia content
  • Any content that requires real-world information, examples, or current data

Core Principle

Never generate content based solely on general knowledge. The quality of your output directly depends on the quality and quantity of research conducted beforehand. A single search query is NEVER enough.

Research Methodology

Phase 1: Broad Exploration

Start with broad searches to understand the landscape:

  1. Initial Survey: Search for the main topic to understand the overall context
  2. Identify Dimensions: From initial results, identify key subtopics, themes, angles, or aspects that need deeper exploration
  3. Map the Territory: Note different perspectives, stakeholders, or viewpoints that exist

Example:

Topic: "AI in healthcare"
Initial searches:
- "AI healthcare applications 2024"
- "artificial intelligence medical diagnosis"
- "healthcare AI market trends"

Identified dimensions:
- Diagnostic AI (radiology, pathology)
- Treatment recommendation systems
- Administrative automation
- Patient monitoring
- Regulatory landscape
- Ethical considerations

Phase 2: Deep Dive

For each important dimension identified, conduct targeted research:

  1. Specific Queries: Search with precise keywords for each subtopic
  2. Multiple Phrasings: Try different keyword combinations and phrasings
  3. Fetch Full Content: Use web_fetch to read important sources in full, not just snippets
  4. Follow References: When sources mention other important resources, search for those too

Example:

Dimension: "Diagnostic AI in radiology"
Targeted searches:
- "AI radiology FDA approved systems"
- "chest X-ray AI detection accuracy"
- "radiology AI clinical trials results"

Then fetch and read:
- Key research papers or summaries
- Industry reports
- Real-world case studies

Phase 3: Diversity & Validation

Ensure comprehensive coverage by seeking diverse information types:

Information Type Purpose Example Searches
Facts & Data Concrete evidence "statistics", "data", "numbers", "market size"
Examples & Cases Real-world applications "case study", "example", "implementation"
Expert Opinions Authority perspectives "expert analysis", "interview", "commentary"
Trends & Predictions Future direction "trends 2024", "forecast", "future of"
Comparisons Context and alternatives "vs", "comparison", "alternatives"
Challenges & Criticisms Balanced view "challenges", "limitations", "criticism"

Phase 4: Synthesis Check

Before proceeding to content generation, verify:

  • Have I searched from at least 3-5 different angles?
  • Have I fetched and read the most important sources in full?
  • Do I have concrete data, examples, and expert perspectives?
  • Have I explored both positive aspects and challenges/limitations?
  • Is my information current and from authoritative sources?

If any answer is NO, continue researching before generating content.

Search Strategy Tips

Effective Query Patterns

# Be specific with context
❌ "AI trends"
✅ "enterprise AI adoption trends 2024"

# Include authoritative source hints
"[topic] research paper"
"[topic] McKinsey report"
"[topic] industry analysis"

# Search for specific content types
"[topic] case study"
"[topic] statistics"
"[topic] expert interview"

# Use temporal qualifiers — always use the ACTUAL current year from <current_date>
"[topic] 2026"   # ← replace with real current year, never hardcode a past year
"[topic] latest"
"[topic] recent developments"

Temporal Awareness

Always check <current_date> in your context before forming ANY search query.

<current_date> gives you the full date: year, month, day, and weekday (e.g. 2026-02-28, Saturday). Use the right level of precision depending on what the user is asking:

User intent Temporal precision needed Example query
"today / this morning / just released" Month + Day "tech news February 28 2026"
"this week" Week range "technology releases week of Feb 24 2026"
"recently / latest / new" Month "AI breakthroughs February 2026"
"this year / trends" Year "software trends 2026"

Rules:

  • When the user asks about "today" or "just released", use month + day + year in your search queries to get same-day results
  • Never drop to year-only when day-level precision is needed — "tech news 2026" will NOT surface today's news
  • Try multiple phrasings: numeric form (2026-02-28), written form (February 28 2026), and relative terms (today, this week) across different queries

❌ User asks "what's new in tech today" → searching "new technology 2026" → misses today's news ✅ User asks "what's new in tech today" → searching "new technology February 28 2026" + "tech news today Feb 28" → gets today's results

When to Use web_fetch

Use web_fetch to read full content when:

  • A search result looks highly relevant and authoritative
  • You need detailed information beyond the snippet
  • The source contains data, case studies, or expert analysis
  • You want to understand the full context of a finding

Iterative Refinement

Research is iterative. After initial searches:

  1. Review what you've learned
  2. Identify gaps in your understanding
  3. Formulate new, more targeted queries
  4. Repeat until you have comprehensive coverage

Quality Bar

Your research is sufficient when you can confidently answer:

  • What are the key facts and data points?
  • What are 2-3 concrete real-world examples?
  • What do experts say about this topic?
  • What are the current trends and future directions?
  • What are the challenges or limitations?
  • What makes this topic relevant or important now?

Common Mistakes to Avoid

  • ❌ Stopping after 1-2 searches
  • ❌ Relying on search snippets without reading full sources
  • ❌ Searching only one aspect of a multi-faceted topic
  • ❌ Ignoring contradicting viewpoints or challenges
  • ❌ Using outdated information when current data exists
  • ❌ Starting content generation before research is complete

Output

After completing research, you should have:

  1. A comprehensive understanding of the topic from multiple angles
  2. Specific facts, data points, and statistics
  3. Real-world examples and case studies
  4. Expert perspectives and authoritative sources
  5. Current trends and relevant context

Only then proceed to content generation, using the gathered information to create high-quality, well-informed content.

Reproducido de bytedance/deer-flow bajo licencia MIT. Leer esta página en markdown.

Archivos

1 archivo en el paquete. Solo se lee SKILL.md al activarse — las referencias se cargan si el skill decide que las necesita.

Detalles

Creador
bytedance
Categoría
Investigación
Licencia
MIT
Recursos incluidos
Solo SKILL.md
Código fuente
Ver SKILL.md

Etiquetas

Más de bytedance/deer-flow

Este repo incluye 27 skills. Si instalas uno, normalmente ya tienes los demás.

Evaluate and carry out non-trivial software-system changes from first principles. Use when assessing RFCs, issues, designs, features, refactors, migrations, dependency changes, or proposed fields, events, APIs, modules, and services whose need, consumers, system fit, validation, or rollback require scrutiny. Read the actual system, identify the concrete problem and named semantic consumers, choose the smallest sufficient solution, reject pseudo-requirements and speculative abstractions, and require evidence proportional to risk. Do not use for mechanical edits, source-code explanation, or a dedicated review of an already-complete diff.

Costo de contexto al activarse
2.5k tok
Tamaño del paquete
1 archivo
Última actualización
el mes pasado
herramientas desarrollo

Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.

Costo de contexto al activarse
1.4k tok
Tamaño del paquete
13 archivos
Última actualización
el mes pasado
herramientas desarrollo

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Costo de contexto al activarse
9.2k tok
Tamaño del paquete
20 archivos
Última actualización
el mes pasado
herramientas desarrollo

End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke test deployment", "verify installation", "test service availability", "end-to-end test", or similar.

Costo de contexto al activarse
2.5k tok
Tamaño del paquete
12 archivos
Última actualización
hace 2 meses
devops infraestructura

Use when a DeerFlow maintainer needs comment-only GitHub issue or PR handling: resolve issue/PR scopes with gh, analyze issues, post or draft issue comments, perform PR review comments, review PR or issue batches, compare competing PRs that target the same issue, give fix strategy, risk classification, and validation guidance. Intended for maintainers and trusted local agents, not general contributors.

Costo de contexto al activarse
5.4k tok
Tamaño del paquete
1 archivo
Última actualización
hace 2 meses
herramientas desarrollo

Ensure async-path backend code that could block the asyncio event loop is protected by a teeth-verified runtime anchor in tests/blocking_io/. Use when changing backend Python under app/, packages/harness/deerflow/, or scripts/, when running a blocking-IO triage round over the whole repo, or when a reviewer/CI asks for blocking-IO coverage. Runs a deterministic scan (changed-lines or full-repo), routes each candidate, drafts/extends an anchor, and proves it fails when the blocking IO regresses.

Costo de contexto al activarse
1.7k tok
Tamaño del paquete
4 archivos
Última actualización
hace 2 meses
herramientas desarrollo

Skills relacionados

Use this skill when the user wants a systematic literature review, survey, or synthesis across multiple academic papers on a topic. Also covers annotated bibliographies and cross-paper comparisons. Searches arXiv and outputs reports in APA, IEEE, or BibTeX format. Not for single-paper tasks — use academic-paper-review for reviewing one paper.

Costo de contexto al activarse
4.3k tok
Tamaño del paquete
7 archivos
Última actualización
hace 4 meses
investigacion

Use this skill when the user requests to review, analyze, critique, or summarize academic papers, research articles, preprints, or scientific publications. Supports comprehensive structured reviews covering methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation. Trigger on queries involving paper URLs, uploaded PDFs, arXiv links, or requests like "review this paper", "analyze this research", "summarize this study", or "write a peer review".

Costo de contexto al activarse
3k tok
Tamaño del paquete
1 archivo
Última actualización
hace 4 meses
documentos

Ensure async-path backend code that could block the asyncio event loop is protected by a teeth-verified runtime anchor in tests/blocking_io/. Use when changing backend Python under app/, packages/harness/deerflow/, or scripts/, when running a blocking-IO triage round over the whole repo, or when a reviewer/CI asks for blocking-IO coverage. Runs a deterministic scan (changed-lines or full-repo), routes each candidate, drafts/extends an anchor, and proves it fails when the blocking IO regresses.

Costo de contexto al activarse
1.7k tok
Tamaño del paquete
4 archivos
Última actualización
hace 2 meses
herramientas desarrollo