Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器github未标认证来源可访问许可证需确认审计提醒

deep-research深入研究

Agent Skill

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

总安装

816

周安装

33

GitHub Stars

35

下载量

256
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/petekp/claude-code-setup --skill deep-research

简介

用于查找、检索和筛选相关信息。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

  • 适合根据关键词或任务场景快速定位候选结果。
  • 可结合来源仓库和原始 README 核验具体用法。
  • 安装前建议确认权限范围和维护状态。
  • deep-research 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Deep Research

Systematic methodology for conducting exhaustive, accurate research using all available tools. Prioritizes correctness over speed.

Core Principles

  1. Multiple sources required — Never rely on a single source for important claims
  2. Cross-reference everything — Verify facts appear consistently across independent sources
  3. Citation mandatory — Every claim must have a source; no unsourced assertions
  4. Acknowledge uncertainty — When sources conflict or are weak, say so explicitly
  5. Prefer primary sources — Official docs > blog posts > forum answers > AI-generated content

Available Research Tools

Use these tools in combination based on the research topic:

ToolBest ForLimitations
WebSearchCurrent events, recent information, broad topic discoveryResults may be outdated, SEO-influenced
WebFetchReading specific URLs, extracting detailed contentRequires known URL
Playwright browserInteractive sites, paywalled content (if logged in), complex navigationSlower, requires more tokens
Context7/MCP docsLibrary/framework documentationOnly indexed libraries
OpenAI docs MCPOpenAI API specificsOpenAI only
Grep/Glob/ReadCodebase research, finding implementationsLocal files only

Research Workflow

Phase 1: Scope Definition

Before researching, clarify:

  1. Core question — What specific question(s) need answering?
  2. Required depth — Surface overview or exhaustive deep-dive?
  3. Recency requirements — Is timeliness critical? (API versions, current events, etc.)
  4. Authoritative sources — What would count as a definitive answer?

Ask clarifying questions if scope is ambiguous. Use AskUserQuestion for structured choices when multiple research directions are possible.

Phase 2: Source Discovery

Cast a wide net to find relevant sources:

1. WebSearch with multiple query variations
   - Try 3-5 different phrasings of the core question
   - Include technical terms AND plain language
   - Search for "[topic] official documentation"
   - Search for "[topic] research paper" or "[topic] study"

2. Identify authoritative sources from results
   - Official documentation sites
   - Academic papers / research institutions
   - Industry standards bodies
   - Recognized experts in the field

3. Check specialized tools
   - Context7 for library/framework docs
   - OpenAI docs MCP for OpenAI-specific topics
   - GitHub/codebase for implementation details

Source discovery heuristics:

  • Government and academic domains (.gov,.edu,.ac.uk) tend toward accuracy
  • Official project documentation is authoritative for that project
  • Wikipedia is a starting point, not an endpoint — follow its citations
  • Stack Overflow answers need verification; check votes and dates
  • Be skeptical of content farms and SEO-optimized listicles

Phase 3: Deep Reading

For each promising source:

  1. Fetch full content — Use WebFetch or browser to get complete text
  2. Extract key claims — Note specific facts, figures, dates, quotes
  3. Note source metadata — Author, date, organization, potential biases
  4. Identify citations — What sources does this source cite?
  5. Flag conflicts — Does this contradict other sources?

Reading strategy for different source types:

Source TypeStrategy
DocumentationRead relevant sections fully; note version/date
Research paperAbstract, conclusion, methodology in that order
News articleCheck publication date, author credentials, cited sources
Blog postVerify claims independently; note author's expertise
Forum/Q&ACheck answer date, votes, accepted status; verify independently

Phase 4: Cross-Verification

For each major claim:

  1. Find 2+ independent sources — Sources that don't cite each other
  2. Check for conflicts — Note any disagreements between sources
  3. Prefer newer sources — For rapidly evolving topics
  4. Weight by authority — Primary sources > secondary > tertiary

Conflict resolution:

  • When sources disagree, report all positions with citations
  • Investigate why they disagree (different contexts, outdated info, different definitions)
  • If one source is clearly more authoritative, note that
  • Never silently pick one version

Phase 5: Synthesis & Output

Structure findings clearly:

## Research Summary: [Topic]

### Key Findings

1. **[Finding 1]**
   - [Specific fact with citation]
   - [Supporting evidence]
   - Confidence: High/Medium/Low
   - Sources: [1], [2]

2. **[Finding 2]**
   ...

### Conflicts & Uncertainties

- [Area of disagreement]: Source A claims X [1], while Source B claims Y [2]. [Analysis of why they differ]

### Source Quality Assessment

| # | Source | Type | Authority | Recency | Notes |
|---|--------|------|-----------|---------|-------|
| 1 | [URL] | Official docs | High | 2024-01 | Primary source |
| 2 | [URL] | Research paper | High | 2023-06 | Peer-reviewed |
| 3 | [URL] | Blog | Medium | 2024-03 | Author is [expert] |

### Gaps & Limitations

- [What couldn't be verified]
- [Areas needing more research]

### Citations

[1] [Full citation with URL]
[2] [Full citation with URL]
...

Confidence Levels

Assign confidence to each finding:

LevelCriteria
High3+ independent authoritative sources agree; no conflicts
Medium2 sources agree, or 1 highly authoritative source; minor conflicts
LowSingle source, or significant conflicts between sources
UncertainSources conflict significantly; unable to determine truth

Always state confidence explicitly. "I'm not sure" is a valid research finding.

Citation Format

Use inline citations with numbered references:

The API rate limit is 60 requests per minute [1], though this can be increased
for enterprise accounts [2].

---
[1] OpenAI API Documentation, "Rate Limits", https://platform.openai.com/docs/guides/rate-limits, accessed 2024-01-15
[2] OpenAI Enterprise FAQ, https://openai.com/enterprise, accessed 2024-01-15

Citation must include:

  • Source name/title
  • URL (if web source)
  • Access date (for web sources)
  • Publication date (if available)

Special Research Scenarios

Rapidly Evolving Topics (AI, crypto, etc.)

  • Prioritize sources from last 6 months
  • Check official changelogs and release notes
  • Note when information might be outdated
  • Consider using browser to check current state directly

Controversial Topics

  • Present multiple perspectives with citations for each
  • Identify the strongest arguments on each side
  • Note which sources might have biases and why
  • Don't pick sides unless evidence is overwhelming

Technical Implementation Questions

  • Check official documentation first (Context7, MCP servers)
  • Look for example code in GitHub
  • Verify against actual behavior if possible
  • Note version-specific differences

Comparative Research ("X vs Y")

  • Use same evaluation criteria for all options
  • Find sources that compare directly when possible
  • Check for bias (vendor-sponsored comparisons)
  • Note what each option is optimized for

Anti-Patterns to Avoid

Anti-PatternWhy It's BadInstead
Single sourceNo verificationAlways find 2+ sources
Uncited claimsUnverifiableEvery fact needs a source
Assuming first result is bestSEO!= accuracyEvaluate source quality
Ignoring conflictsHides uncertaintyReport all positions
Outdated sourcesInformation decayCheck publication dates
Trusting AI summariesMay hallucinateGo to primary sources
Stopping earlyIncomplete pictureResearch until diminishing returns

Completion Criteria

Research is complete when:

  1. Core question(s) answered with citations
  2. Key claims verified by 2+ independent sources
  3. Conflicts and uncertainties explicitly noted
  4. Source quality assessed for all citations
  5. Confidence levels assigned to findings
  6. Gaps and limitations documented

Reference Files

For detailed guidance on specific scenarios:

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.49%
按下载量换算86

Claude

29.72%
按下载量换算76

Cursor

19.66%
按下载量换算50

Gemini CLI

9.54%
按下载量换算24

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

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

来源信息

继续浏览同类 Skills