deep-research
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 e
npx skills add staruhub/ClaudeSkills --skill Geek-skills-deep-research --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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-180
- What this skill should produce
- When NOT to use this skill
- Org-policy boundary
- Active context bundle
- Workflow
- P0 — Scope, route, and choose the lightest mode
- P0.5 — Optional modules (not mandatory by default)
- P1 — Plan the evidence work
- P2 — Investigate, extract, and write notes
- P3 — Build registry and verify evidence
- P4 — Synthesize the output
- P5 — Evaluate and gate
- P6 — Finalize, summarize, and learn
- Deterministic helpers
What does the deep-research skill do?
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 e
How do I install it?
Run `npx skills add staruhub/ClaudeSkills --skill Geek-skills-deep-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From staruhub/ClaudeSkills, a repository with 659 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.