deep-research
Run a disciplined, multi-source research investigation for a high-stakes question or decision — fan-out web search across many channels, parallel sub-agents, source triangulation (each claim backed by ≥3 independent sources), an adversarial review pass, and every source saved to its own file with verbatim quotes for reuse. Use when a low-quality answer is expensive: strategy work, comparing N products/methods/markets, validating a hypothesis with external data, or mapping how a field works. NOT for quick fact-checks (answer directly), structured 12-dimension competitor scoring (use competitive-teardown), or fast topic overviews where the decision risk is low (use the research router instead).
- License 许可
- MIT
- 最近更新
- 2026-07-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- deep-research
- description
- Run a disciplined, multi-source research investigation for a high-stakes question or decision — fan-out web search across many channels, parallel sub-agents, source triangulation (each claim backed by ≥3 independent sources), an adversarial review pass, and every source saved to its own file with verbatim quotes for reuse. Use when a low-quality answer is expensive: strategy work, comparing N products/methods/markets, validating a hypothesis with external data, or mapping how a field works. NOT for quick fact-checks (answer directly), structured 12-dimension competitor scoring (use competitive-teardown), or fast topic overviews where the decision risk is low (use the research router instead).
02 资源文件 1
- 参考文档references/full-catalog.md980 B
03 SKILL.md 正文
Deep Research — Disciplined Meta-Research
Turn "research this topic" into an auditable, reusable investigation instead of a one-shot wall of text. The output is a folder you can return to in a month: every claim traces to a specific source file, the plan documents why each choice was made, and a refresh protocol lets you update it later without re-running everything.
This is the heavy, methodical end of research. It is not a fast overview — it is the workflow you reach for when getting the answer wrong costs more than the tokens spent getting it right.
How it differs from a quick research router
A router-style research skill (keyword-classify → delegate → short sequential search → markdown brief) is optimal when you need an answer fast and the decision risk is low. deep-research is the opposite trade: it pays for rigor. Use it when the answer feeds a strategy, an irreversible decision, a published artifact, or a hypothesis you need to actually test — situations where a shallow fallback would be a liability.
Concretely, deep-research adds what a fast overview does not: falsifiable hypotheses up front, parallel sub-agent fan-out across many channels, triangulation with explicit source-type diversity, a mandatory adversarial pass, per-source files with verbatim quotes, and a refresh_targets.md for delta-updates later.
The pipeline (9 phases)
Depth scales with the task — shallow runs the core phases inline; medium/deep add capability discovery, verification, and refresh targets.
| # | Phase | What it does |
|---|---|---|
| 1 | Reframe | Rewrite the question, fix the underlying decision, state 2–4 falsifiable hypotheses |
| 2 | Genre & blocks | Pick the report genre (qa / explainer / decision / landscape / validation / custom) and its building blocks |
| 3 | Plan | Write plan.md: scope, structure, sourcing strategy, opposition queries, risk register, stop-criteria |
| 3.5 | Capability discovery | Audit available API keys/channels in the environment; map subtopics to sources; fall back to HTML where needed |
| 4 | Search (loop) | Dispatch sources → launch sub-agents in parallel → fetch & dedup → save each to sources/NN.md; re-evaluate between rounds |
| 5 | Score & triangulate | Rate every source on Credibility / Recency / Bias; require ≥3 independent, differently-typed sources per thesis |
| 6 | Synthesize + adversarial | Assemble the report from blocks, run 4 self-critique questions, add steel-manned counter-arguments |
| 6.5 | Verify | Lightweight citation check before closing |
| 7 | Refresh targets | Extract entities / numbers / hypotheses into refresh_targets.md — the entry point for future updates |
Core mechanisms
These are what separate a documented investigation from a confident guess:
- Triangulation. Every thesis must be backed by ≥3 independent sources of different types (primary / academic / industry / discussion). A claim with fewer is flagged "insufficient evidence," not stated as fact.
- Source-grounding. Each source becomes its own
sources/NN_slug.mdwith metadata, verbatim quotes, and scores. No dangling claim — every assertion links back to a specific file. An empty fetch produces an empty claim, never a fabricated citation. - Adversarial pass. Phase 6 always runs the strongest available reasoning: 4 self-critique questions plus an active search for counter-arguments and disconfirming evidence.
- Falsifiable hypotheses. Phase 1 commits to 2–4 hypotheses; Phases 5–6 explicitly confirm or refute each against the evidence, or mark it under-determined.
- Parallel sub-agents. Phase 4 launches search sub-agents concurrently (cheap models for broad web sweeps, stronger ones for reasoning-heavy subtopics) — never one-at-a-time.
- Refresh protocol. Phase 7 emits
refresh_targets.md; anupdate <slug>run produces a delta (new entrants, entity changes, refreshed numbers, adversarial triggers) instead of replaying the whole investigation. - Atomic findings. Reusable theses in
findings/FN.mdplus asources.csvindex — research compounds across questions instead of starting from zero each time.
Output structure
<root>/<slug>/
├── plan.md # scope, sourcing strategy, risk register, changelog
├── sources.csv # index of every source with scores
├── sources/
│ ├── 01_<slug>.md # one file = one source (metadata + verbatim quotes)
│ └── ...
├── findings/ # atomic, reusable theses (larger investigations)
│ └── F1_<short>.md
├── refresh_targets.md # what to watch on update (medium/deep)
├── diffs/
│ └── YYYY-MM-DD_delta.md # delta from an `update <slug>` run
└── YYYY-MM-DD_<genre>.md # final report
When to use
- A low-quality answer is expensive: strategy, business plan, report, or article groundwork.
- Comparing N institutions, products, methodologies, or markets and you need defensible reasoning.
- Validating a hypothesis or a decision against external data.
- Meta-research: "understand how X works," "map the landscape of Y," answering a connected series of questions.
Anti-Patterns
- Don't skip the existing-work check. Before searching, see whether the answer is already in the project or in a prior research folder — you risk re-researching something you already have.
- Don't skip reframing, even when the request "seems clear." The decision behind the question usually changes the search.
- Don't output to chat only. Always persist sources and the report to files — the reuse value is in the folder, not the transcript.
- Don't fabricate citations. If a fetch returns nothing, the claim is empty — never invent a plausible URL. Bind every claim to a saved verbatim quote.
- Don't build conclusions on a thin corpus. Too few sources, or sources that all share one type, means triangulation hasn't happened — say so rather than overstating confidence.
- Don't skip the adversarial pass on medium/deep investigations. Confirmation-only research is the failure mode this skill exists to prevent.
- Don't run sub-agents sequentially. Fan-out in parallel; serial search wastes the wall-clock advantage.
- Don't collapse
sources/into one file. Per-source files are what make findings searchable and reusable across investigations. - Don't pick the heaviest model for everything. Match model to subtask — cheap for broad sweeps, strong for synthesis and the adversarial pass.
Cross-References
- research router — for fast topic overviews where decision risk is low;
deep-researchis the heavyweight alternative when rigor matters more than speed. - competitive-teardown — for comparing N competitors on a structured 12-dimension matrix.
- litreview / dossier / patent — domain specialists when the investigation is narrowly academic, person/company-focused, or patent-focused.
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.