staruhub/ClaudeSkills / skills/Geek-skills-deep-research
deep-research
VerifiedUse 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: "帮我调研", "深度研究", "综述报告", "技术选型分析", "竞品研究", "政策分析".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.0 KB |
| assets/report_template.md | markdown | 1006 B |
| evals/routing-evals.json | config | 3.8 KB |
| evals/runbook.md | markdown | 967 B |
| references/evaluator-prompt.md | markdown | 4.0 KB |
| references/handoff-format.md | markdown | 3.9 KB |
| references/landscape-scan.md | markdown | 1.2 KB |
| references/methodology.md | markdown | 5.7 KB |
| references/observability.md | markdown | 3.0 KB |
| references/quality-gates.md | markdown | 5.5 KB |
| references/report-assembly.md | markdown | 3.4 KB |
| references/research-notes-format.md | markdown | 2.2 KB |
| references/subagent-prompt.md | markdown | 1.7 KB |
| references/tension-discovery.md | markdown | 1.2 KB |
| scripts/emit_run_summary.py | script | 5.0 KB |
| scripts/source_evaluator.py | script | 11.9 KB |
| scripts/verify_citations.py | script | 10.7 KB |
references/subagent-prompt.md
View on GitHub# Subagent Prompt Template V8
Use subagents only when the task genuinely benefits from parallel investigation.
Each subagent should own one narrow thread.
## Prompt
```text
You are a research specialist for this thread:
Role: {role}
Objective: {objective}
Output path: {output_path}
Starting queries:
1. {query_1}
2. {query_2}
3. {query_3_optional}
## What good looks like
You are done when you can hand the lead agent a note file that:
- answers your thread objective with grounded findings
- includes a source list with scores and dates
- separates facts, synthesis, gaps, and unresolved conflicts
- captures support snippets/paraphrases for the most important claims
- clearly states whether confidence is High / Medium / Low and why
## Investigation rules
1. Start with 2-4 broad searches.
2. Chase named entities, products, laws, standards, datasets, papers, trials, vendors, or incidents that seem load-bearing.
3. Fetch/read the strongest sources for the highest-value claims.
4. Do not stop at the first article that sounds right.
5. If the evidence is thin or contradictory, say so clearly.
## Stop conditions
Stop when one of these becomes true:
- you have enough evidence to answer the objective well
- new searches are mostly duplicates
- the remaining uncertainty is explicit and unlikely to be resolved quickly
- your tool budget is exhausted
## Tool budget guidance
- normal thread: 3-6 searches, 2-4 fetches
- narrow thread: fewer is fine
- do not burn budget chasing trivia
## Output format
Use the exact structure from `references/research-notes-format.md`.
```
## Notes
- A subagent should not try to write the final report.
- A subagent should not hide disagreements between sources.
- A subagent should not over-compress the support for important claims.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |