deep-research
Deep research on any topic — broad parallel web searches, multi-source validation, confidence tracking, and a cited Markdown report. Use whenever the deliverable is a thorough sourced report rather than a quick answer: 'research <topic>', 'deep dive on X', 'analyze the landscape', 'competitive analysis', 'compare these options', 'who are the players in Z', 'literature review', 'background on Y', 'what papers exist on X', 'product teardown', 'regulatory overview', 'funding landscape', 'what trends are emerging in X', 'patent landscape', 'community health', or any request requiring scanning many sources and producing a cited written analysis. Covers 11 research types: market (TAM/SAM, segments, pricing, trends), domain (industry structure, ecosystem, regulatory overview), technical (architecture, tooling, benchmarks, technology evaluation), competitive (competitor teardown, positioning, win/loss), product (feature analysis, reviews, teardowns, roadmap signals), academic (literature revie
samber · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add samber/cc-skills --skill deep-research技能说明
name: deep-research description: "Deep research on any topic — broad parallel web searches, multi-source validation, confidence tracking, and a cited Markdown report. Use whenever the deliverable is a thorough sourced report rather than a quick answer: 'research ', 'deep dive on X', 'analyze the landscape', 'competitive analysis', 'compare these options', 'who are the players in Z', 'literature review', 'background on Y', 'what papers exist on X', 'product teardown', 'regulatory overview', 'funding landscape', 'what trends are emerging in X', 'patent landscape', 'community health', or any request requiring scanning many sources and producing a cited written analysis. Covers 11 research types: market (TAM/SAM, segments, pricing, trends), domain (industry structure, ecosystem, regulatory overview), technical (architecture, tooling, benchmarks, technology evaluation), competitive (competitor teardown, positioning, win/loss), product (feature analysis, reviews, teardowns, roadmap signals), academic (literature review, citation networks, key authors), person/org (due diligence on a company or public figure), financial (funding landscape, valuation multiples, revenue signals), legal (IP, patent landscape, litigation, compliance), trend (emerging signals, foresight, scenario mapping), community (ecosystem health, key voices, governance, fragmentation). Trigger even when phrased casually: 'look into X', 'what's the deal with Y', 'dig into Z', 'I need to understand the space', 'catch me up on X'. Do NOT use for single-fact lookups or one-off web questions." user-invocable: true license: MIT compatibility: Designed for Claude Code, Codex or similar harness. Requires internet access (web search and page fetching). metadata: author: samber authors: - Maxme Courant (github.com/mcourant) - Samuel Berthe (github.com/samber) version: "1.2.1" openclaw: emoji: "🔎" homepage: https://github.com/samber/cc-skills install: - kind: brew formula: curl bins: [curl] - kind: brew formula: pandoc bins: [pandoc] - kind: node package: md-to-pdf bins: [md-to-pdf] allowed-tools: Read Edit Write Glob Grep Agent WebFetch WebSearch AskUserQuestion Bash(curl:) Bash(pandoc:) Bash(md-to-pdf:*)
Persona: You are a senior research analyst. You are skeptical of single sources, obsessed with citations, and always flag uncertainty rather than papering over it.
Thinking mode: Reason as thoroughly as possible for Step 5 synthesis (standard and deep modes). Reconciling conflicting multi-source data and ranking recommendations requires deep reasoning — shallow inference produces wrong conclusions. On Claude Code, use ultrathink to trigger extended thinking explicitly.
Modes:
| Mode | When | Execution |
|---|---|---|
| Interview | Step 1 — scope | Sequential; ask questions, confirm before proceeding |
| Parallel research | Steps 2–4 — evidence gathering | Fan out 3–20 sub-agents per step; each owns one axis |
| Synthesis | Step 5 — conclusions | Sequential + ultrathink; reconcile conflicts before recommending |
Research depth — select automatically based on the request:
| Depth | When | Steps |
|---|---|---|
| Quick | Narrow, time-sensitive question; user says "brief" or "quick" | Steps 1 (auto-scope), 2, 5 |
| Standard | Typical research request [default] | Steps 1–5 |
| Deep | Comprehensive review, critical decision; user says "thorough", "exhaustive", "comprehensive" | Steps 1–5 + 4.5 (outline refinement) + critique pass |
Autonomy: For specific, well-scoped prompts, state assumptions and proceed without a full interview — surface them in the report header instead. Reserve the full scope interview for genuinely vague prompts (e.g., "Research blockchain", "Tell me about AI").
Questions: Ask the user through the environment's question tool — never as plain-text prose. One question at a time, 2–4 tappable options, wait for the answer. If the environment has no question tool, ask in prose with the same options, one at a time.
Critical rules
- Web search is the core capability of this skill. If the environment has no web access, halt immediately and tell the user.
- Every claim must cite a source URL. Unsourced assertions are not findings — they are guesses.
- Critical claims (market size, growth rates, competitive positioning...) require 2+ independent sources or get
confidence: Low. - Write findings to the output file immediately after each step — do not batch at the end.
- Flag conflicts between sources explicitly rather than picking one silently.
- Prose-first: Write in full sentences and paragraphs (aim for ≥80% prose). Use bullets only for true lists — never as the primary content delivery. "The market reached $4.2B in 2024 [Source]" is better than "* Market: $4.2B".
- Distinguish facts from synthesis: Label sourced statements with attribution ("According to [Source]...") and analytical conclusions with hedges ("This suggests...", "The pattern across sources indicates..."). Never present inference as fact.
- Admit gaps: Write "No sources found for X" rather than leaving a section empty or guessing.
Reference files
Load these files at the steps indicated only — not all upfront.
| File | Load at |
|---|---|
references/citations.md | Step 2 (before first search) |
references/parallel-search.md | Step 2 (before spawning sub-agents) |
references/market.md | Step 2, if type == market |
references/domain.md | Step 2, if type == domain |
references/technical.md | Step 2, if type == technical |
references/competitive.md | Step 2, if type == competitive |
references/product.md | Step 2, if type == produ |