# Deep Research

Use this skill when the user wants an evidence-based research memo, literature review...

- Repository: https://github.com/staruhub/ClaudeSkills (731 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-08-13
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add staruhub/ClaudeSkills --skill deep-research -g -a claude-code -y`
Codex: `npx skills add staruhub/ClaudeSkills --skill deep-research -g -a codex -y`
Cursor: `npx skills add staruhub/ClaudeSkills --skill deep-research -g -a cursor -y`
Gemini CLI: `npx skills add staruhub/ClaudeSkills --skill deep-research -g -a gemini-cli -y`

## Description

Use this skill when the user wants an evidence-based research memo, literature review, market/policy/technical landscape, or a multi-source decision brief with citations, trade-offs, and a clear conclusion. Best for tasks that need synthesis across multiple external sources, iterative follow-up research, or a reusable written artifact. Do not use for quick factual lookups, single-source summaries, simple Q&A, summarizing one document the user already provided, plan-only requests where the user explicitly defers the actual research, or when the user wants a short answer with no need for cited evidence (a short but evidence-backed conclusion is still a brief memo, which this skill covers). Chinese trigger examples: "帮我调研", "深度研究", "综述报告", "技术选型分析", "竞品研究", "政策分析".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Deep Research V8.1

This skill is for **evidence-rich research outputs**, not for every question that happens to mention “analysis”.

The V8 shift is simple:
- **Single-agent first.** Start with one lead agent and only fan out when parallel work will clearly help.
- **Thin harness, fat skill.** Put reusable judgment and workflow here; keep deterministic checks in scripts.
- **Context organization over prompt stuffing.** Load the minimum active context bundle, then pull in references only when needed.
- **Eval and observability built in.** A good report is not enough; the run must also be diagnosable and improvable.

## What this skill should produce

Choose the lightest artifact that satisfies the task.

| Output type | Use when | Typical length | Required artifacts |
|---|---|---:|---|
| **Brief memo** | user wants a concise answer with evidence | 800-1800 words | `research-plan.md`, `registry.md`, `draft.md`, `run-summary.json` |
| **Full report** | user asks for comprehensive analysis / literature review / decision document | 2500-6000 words | all core artifacts + `evaluation.md` |
| **Delta update** | user says “continue”, “second round”, “what changed”, “deepen round 2” | 600-1800 words | prior round handoff (`references/handoff-format.md`) + new notes + delta draft |

If the user did **not** ask for a long report, default to **Brief memo**.

## When NOT to use this skill

Do **not** activate for:
- quick fact lookups or simple definitions
- summarizing a single provided article/PDF/page
- short comparisons the model can answer directly from 1-2 sources
- brainstorming without evidence requirements
- tasks where the user explicitly wants a short answer, not a report

If in doubt, ask yourself: **Does this task need a reusable evidence artifact and multi-source synthesis?** If not, do something simpler.

## Org-policy boundary

The rest: https://github.com/staruhub/ClaudeSkills/blob/HEAD/skills/Geek-skills-deep-research/SKILL.md