deep-researcher
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources. Uses file-based research tracking, parallel investigation threads, and context-efficient patterns for deep investigations. ALL MEDICAL CITATIONS FROM PUBMED MCP ONLY.
What this skill does
# Deep Researcher v2.0
Comprehensive research methodology with file-based tracking, parallel execution, and context management for investigations requiring 5+ sources.
**CRITICAL: All medical evidence and citations must come from PubMed MCP. No exceptions.**
---
## Research Modes
**Quick Research** (1-4 sources): Work in-context, no file structure needed.
**Deep Research** (5+ sources): Use file-based tracking below.
---
## Research Sources (STRICT POLICY)
### ALLOWED for Medical Citations
| Source | Tool | Use Case |
|--------|------|----------|
| **PubMed MCP** | `pubmed_search_articles`, `pubmed_fetch_contents`, `pubmed_article_connections` | ALL medical evidence, trials, mechanisms |
| **Official Guidelines** | `web_fetch` to ACC/ESC/ADA/AHA URLs only | Guideline recommendations |
| **AstraDB RAG** | Knowledge pipeline | Textbook references, pre-loaded guidelines |
### NOT ALLOWED for Medical Citations
| Source | Why Excluded | Allowed Use |
|--------|--------------|-------------|
| ~~OpenAlex~~ | Quality variable | **REMOVED** |
| ~~Perplexity~~ | Not peer-reviewed | Trend discovery only, NEVER cite |
| ~~General web search~~ | Unreliable | Topic discovery only, NEVER cite |
| ~~News articles~~ | Not primary evidence | Background context only |
### PubMed Quality Filters
**Prefer (Tier 1):**
- Randomized Controlled Trials (RCTs)
- Meta-analyses and Systematic Reviews
- Guidelines from ACC/ESC/ADA/AHA
**Accept (Tier 2):**
- Large observational studies from Q1 journals
- Cohort studies with >1000 patients
- Registry data from established registries
**Use Cautiously (Tier 3):**
- Case series (only if no better evidence)
- Expert consensus statements
- Narrative reviews (as background, not primary evidence)
**Reject:**
- Case reports (except for rare conditions)
- Letters to editor
- Preprints without peer review
- Animal studies (unless specifically about mechanisms)
---
## Deep Research Workflow
### Progress Tracking
Create this checklist and update after each step:
```
Deep Research Progress:
- [ ] Step 1: Initialize research project
- [ ] Step 2: Define scope and plan
- [ ] Step 3: Execute research threads (parallel when possible)
- [ ] Step 4: Validate and cross-reference
- [ ] Step 5: Synthesize from files
- [ ] Step 6: Generate final report
```
---
## Step 1: Initialize Research Project
For research requiring 5+ sources, create a project structure:
```bash
mkdir -p ~/research_{topic}/sources
mkdir -p ~/research_{topic}/threads
```
**Project Structure:**
```
~/research_{topic}/
├── plan.md # Research questions, scope, thread assignments
├── progress.md # Living checklist, updated throughout
├── sources/
│ └── pubmed.md # PubMed search results and abstracts
├── threads/
│ ├── thread_1.md # Independent research thread
│ ├── thread_2.md # Another thread
│ └── ...
├── validation.md # Cross-reference and credibility check
├── synthesis.md # Cross-thread analysis
└── report.md # Final deliverable
```
**Why file-based?** Context windows fill up. Writing findings to files lets you:
- Continue researching without context pressure
- Synthesize from persistent storage, not memory
- Produce larger, more comprehensive reports
- Resume if interrupted
---
## Step 2: Define Scope and Research Plan
Write `plan.md` with:
```markdown
# Research Plan: {Topic}
## Primary Question
[The main thing we're trying to answer]
## Scope
- Include: [what's in scope]
- Exclude: [what's explicitly out]
- Depth: [overview | detailed | exhaustive]
- Deliverable: [report type and length]
## Research Threads
### Thread 1: {Subtopic A}
- Questions to answer: ...
- PubMed search strategy: [MeSH terms, filters]
- Expected study types: RCTs, meta-analyses, etc.
- Can run parallel? Yes/No
### Thread 2: {Subtopic B}
- Questions to answer: ...
- PubMed search strategy: ...
- Can run parallel? Yes/No
[Continue for 2-5 threads]
## Thread Dependencies
- Thread 3 depends on Thread 1 findings
- Threads 1, 2, 4 can run in parallel
## Synthesis Strategy
How will threads combine into final answer?
```
**Planning Guidelines:**
| Research Type | Threads | Pattern |
|--------------|---------|---------|
| Simple fact-finding | 1-2 | Sequential |
| Drug comparison | 1 per drug (max 5) | Parallel |
| Complex investigation | 3-5 thematic | Mixed |
| Literature review | By time period or theme | Sequential |
---
## Step 3: Execute Research Threads
### PubMed Search Strategy
For each thread, use structured PubMed queries:
```python
# Example search for SGLT2 CV outcomes
pubmed_search_articles(
queryTerm="SGLT2 inhibitor cardiovascular outcomes randomized controlled trial",
maxResults=20,
sortBy="relevance"
)
# Then fetch full details for top results
pubmed_fetch_contents(pmids=["PMID1", "PMID2", ...])
# Find related articles for key papers
pubmed_article_connections(
sourcePmid="key_paper_pmid",
relationshipType="pubmed_similar_articles"
)
```
### Parallel Execution Pattern
For independent threads, execute PubMed searches in parallel (multiple tool calls in one turn), then write each to its thread file.
**Example: Comparing SGLT2 Inhibitors**
```
Thread 1: Empagliflozin → pubmed_search "empagliflozin cardiovascular RCT" → threads/empagliflozin.md
Thread 2: Dapagliflozin → pubmed_search "dapagliflozin cardiovascular RCT" → threads/dapagliflozin.md
Thread 3: Canagliflozin → pubmed_search "canagliflozin cardiovascular RCT" → threads/canagliflozin.md
```
Execute all three searches, then write findings to respective files.
### Sequential Execution Pattern
For dependent threads, complete each fully before starting the next.
### Thread File Format
Each `threads/thread_N.md` should contain:
```markdown
# Thread: {Subtopic}
## PubMed Searches Executed
1. Query: [exact query] → [N results] → Top PMIDs: [list]
2. Query: [exact query] → [N results] → Top PMIDs: [list]
## Key Findings
### Finding 1: [Title]
- PMID: [number]
- Citation: [Authors, Journal, Year]
- Study type: RCT / Meta-analysis / Cohort / etc.
- Population: [N patients, characteristics]
- Key result: [HR/OR with 95% CI, p-value]
- Quality: High / Medium / Low [+ brief justification]
### Finding 2: [Title]
- PMID: [number]
...
## Contradictions Found
- PMID X says [claim], PMID Y says [different claim]
- Potential explanation: [patient population, endpoints, timing, etc.]
## Gaps Identified
- No RCT data on [specific question]
- Limited evidence in [patient subgroup]
## Thread Summary
[2-3 sentence synthesis of this thread's findings with key PMIDs cited]
```
### Context Offloading
**After every 5-7 tool calls:**
1. Write current findings to appropriate file
2. Update `progress.md` with status
3. Continue with fresh context
**Trigger for offload:**
- Context feeling "full" (responses slowing, losing track)
- Switching between threads
- Before any synthesis step
---
## Step 4: Validate and Cross-Reference
Read all thread files, then create `validation.md`:
```markdown
# Validation Report
## Facts Requiring Cross-Reference
| Claim | Thread Source | PMID | Verification Status | Confidence |
|-------|--------------|------|---------------------|------------|
| SGLT2i reduces HF hospitalization | Thread 1 | 12345678 | Confirmed by PMIDs 23456789, 34567890 | High |
| Benefit extends to HFpEF | Thread 2 | 45678901 | Conflicting: PMID 56789012 shows null | Investigate |
## Contradictions Analysis
### Contradiction 1: [Description]
- Position A: PMID [X], [study name], found [result]
- Position B: PMID [Y], [study name], found [result]
- Resolution: [Population difference / endpoint difference / timing / unresolved]
## Source Quality Assessment
| PMID | Study | Type | N | Quality | Notes |
|------|-------|------|---|---------|-------|
| 12345678 | EMPA-REG | RCT | 7,020 | High | Industry-funded but well-designed |
| 23456789 | Meta-analysis | MA | 45,000 | High | Published in Lancet |
## ValidRelated in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.