Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

deep-research深入研究

Agent Skill

deep-research 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

21,336

周安装

889

GitHub Stars

64,293

下载量

7,112
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:deep-research(深入研究)
来源仓库:https://github.com/bytedance/deer-flow
仓库路径:skills/deep-research
安装命令:
npx skills add https://github.com/bytedance/deer-flow --skill deep-research
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/bytedance/deer-flow --skill deep-research

简介

用于系统性开展深入网络研究工作。deep-research 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 应在任何内容生成任务前加载以确保信息充分。
  • 支持多角度、多层次、多来源的信息整理。
  • 安装方式:通过 npx 从 GitHub 仓库添加技能。
  • 注意:不适合仅用单次搜索即可回答的问题场景。

SKILL.md

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 TypePurposeExample Searches
Facts & DataConcrete evidence"statistics", "data", "numbers", "market size"
Examples & CasesReal-world applications"case study", "example", "implementation"
Expert OpinionsAuthority perspectives"expert analysis", "interview", "commentary"
Trends & PredictionsFuture direction"trends 2024", "forecast", "future of"
ComparisonsContext and alternatives"vs", "comparison", "alternatives"
Challenges & CriticismsBalanced 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 intentTemporal precision neededExample 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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.16%
按下载量换算2,714

Claude

28.23%
按下载量换算2,008

Cursor

21.27%
按下载量换算1,513

Gemini CLI

9.86%
按下载量换算701

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills