MCPInstall

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.

Installs
72
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/drshailesh88/integrated_content_os --skill deep-researcher
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads deep-researcher automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

SourceToolUse Case
PubMed MCPpubmed_search_articles, pubmed_fetch_contents, pubmed_article_connectionsALL medical evidence, trials, mechanisms
Official Guidelinesweb_fetch to ACC/ESC/ADA/AHA URLs onlyGuideline recommendations
AstraDB RAGKnowledge pipelineTextbook references, pre-loaded guidelines

NOT ALLOWED for Medical Citations

SourceWhy ExcludedAllowed Use
OpenAlexQuality variableREMOVED
PerplexityNot peer-reviewedTrend discovery only, NEVER cite
General web searchUnreliableTopic discovery only, NEVER cite
News articlesNot primary evidenceBackground 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:

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:

# 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 TypeThreadsPattern
Simple fact-finding1-2Sequential
Drug comparison1 per drug (max 5)Parallel
Complex investigation3-5 thematicMixed
Literature reviewBy time period or themeSequential

Step 3: Execute Research Threads

PubMed Search Strategy

For each thread, use structured PubMed queries:

# 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:

# 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:

# 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 |

## Validated Knowledge Base
[List of facts we're confident in, with PMIDs]

1. **SGLT2 inhibitors reduce CV death in T2DM with established CVD** (PMID: 12345678, 23456789)
2. **Benefit on HF hospitalization is consistent across the class** (PMID: 34567890, 45678901)
3. ...

Step 5: Synthesize from Files

Critical: Read from files, not memory.

# Read all thread files
cat ~/research_{topic}/threads/*.md

# Read validation
cat ~/research_{topic}/validation.md

Write synthesis.md:

# Synthesis: {Topic}

## Cross-Thread Patterns
[What themes emerge across multiple threads?]

## Key Insights
1. [Insight that required combining multiple threads]
2. [Insight that wasn't obvious in any single thread]
3. ...

## The Answer
[Direct response to the primary research question, with PMID citations]

## Evidence Strength Assessment
- **Strong evidence (multiple RCTs):** [claims]
- **Moderate evidence (single RCT or consistent observational):** [claims]
- **Limited evidence (observational only):** [claims]
- **Expert opinion / guideline extrapolation:** [claims]

## Remaining Gaps
[What we still don't know and would need to investigate further]

Step 6: Generate Final Report

Write report.md using the synthesis:

# {Title}

## Executive Summary
[3-5 sentences: question, key finding, main conclusion with strongest PMID]

## Research Question and Scope
[From plan.md]

## Methodology
- Database: PubMed via NCBI MCP
- Search date: [date]
- Total articles screened: [N]
- Articles included: [N]
- Study types: [breakdown]

## Findings

### {Theme 1}
[Narrative synthesis with inline PMID citations]

### {Theme 2}
...

## Analysis
[Patterns, implications, connections]

## Conclusions
1. [Primary conclusion with evidence level]
2. [Secondary conclusions]

## Clinical Implications
[If applicable: what this means for practice]

## Limitations
- [Search limitations]
- [Evidence gaps]
- [Potential biases]

## References
[Full reference list with PMIDs and DOIs]

1. Author A, Author B, et al. Title. Journal. Year;Vol:Pages. PMID: XXXXXXXX. DOI: XX.XXXX/XXXXX
2. ...

Parallel Research Patterns

Pattern A: Drug/Entity Comparison

Use when: Comparing 2-5 similar entities (drugs, devices, techniques)

User: "Compare CV outcomes of GLP-1 agonists"
→ Thread per drug (semaglutide, tirzepatide, liraglutide)
→ All threads parallel (same PubMed structure)
→ Comparison matrix synthesis

Pattern B: Pro/Con Analysis

Use when: Topic has debate or controversy

User: "Analyze the evidence on aggressive LDL lowering"
→ Thread 1: Evidence FOR aggressive targets (PubMed: LDL <55 outcomes)
→ Thread 2: Evidence AGAINST/concerns (PubMed: LDL lowering adverse effects)
→ Thread 3: Current guidelines (fetch ACC/ESC guideline URLs)
→ Threads 1-2 parallel, Thread 3 after

Pattern C: Evidence + Guidelines

Use when: Need both primary evidence and clinical guidance

User: "What's the evidence on TAVR durability?"
→ Thread 1: Trial data (PubMed: TAVR long-term outcomes RCT)
→ Thread 2: Registry data (PubMed: TAVR registry durability)
→ Thread 3: Guidelines (fetch ACC/ESC valve guidelines)
→ All parallel

Pattern D: Historical Evolution

Use when: Understanding how evidence has evolved

User: "How has heart failure treatment evolved?"
→ Thread 1: Pre-neurohormonal era (PubMed: heart failure treatment 1980-1990)
→ Thread 2: ACE/ARB/BB era (PubMed: heart failure ACE inhibitor landmark)
→ Thread 3: Modern era ARNI/SGLT2 (PubMed: heart failure SGLT2 ARNI)
→ Sequential (each builds context for next)

Quality Checkpoints

After Step 2 (Planning)

  • Research question is specific and answerable
  • PubMed search strategies are defined for each thread
  • Threads are independent where marked parallel
  • Expected study types are specified

After Step 3 (Execution)

  • Each thread has 3+ credible PubMed sources
  • Key claims have specific data (HR, CI, p-value)
  • All citations have PMIDs
  • Gaps and contradictions are documented
  • Thread summaries are written

After Step 4 (Validation)

  • Key facts cross-referenced across threads
  • Contradictions analyzed with potential explanations
  • Source quality assessed for each major citation
  • Validated knowledge base compiled

After Step 5 (Synthesis)

  • Cross-thread patterns identified
  • Primary question directly answered
  • Evidence strength honestly assessed
  • Insights go beyond any single thread

Before Delivery

  • Report structure matches user's requested format
  • All claims have PMID citations
  • Executive summary is truly executive (skimmable)
  • Reference list is complete with DOIs

Common Research Pitfalls

PitfallSymptomFix
Context overflowLosing track of earlier findingsWrite to files every 5-7 tool calls
Confirmation biasAll sources agree suspiciouslySearch for contradicting evidence explicitly
Recency biasOnly 2023-2024 sourcesInclude landmark trials regardless of date
Source homogeneityAll RCTs, no guidelinesAdd guideline thread for clinical context
Scope creepResearch expanding endlesslyReturn to plan.md, enforce boundaries
Premature synthesisConcluding before validationComplete Step 4 before Step 5
Memory-based synthesisCiting from recallRead files explicitly during Step 5
Non-PubMed citationsCiting Perplexity/webDelete and replace with PubMed source

Example: Full Research Session

User: "Research the current evidence on colchicine for cardiovascular prevention"

Step 1: Initialize

mkdir -p ~/research_colchicine_cv/sources
mkdir -p ~/research_colchicine_cv/threads

Step 2: Plan (write to plan.md)

  • Primary question: What's the evidence for colchicine in CV prevention?
  • Thread 1: Major RCTs (COLCOT, LoDoCo2, CLEAR SYNERGY)
    • PubMed: "colchicine cardiovascular randomized controlled trial"
  • Thread 2: Mechanisms and anti-inflammatory hypothesis
    • PubMed: "colchicine inflammation atherosclerosis mechanism"
  • Thread 3: Guidelines and clinical adoption
    • Fetch: ACC/ESC guideline URLs for stable CAD
  • Thread 4: Safety and practical considerations
    • PubMed: "colchicine adverse effects cardiovascular"
  • Threads 1, 2, 4 parallel; Thread 3 after 1 completes

Step 3: Execute

# Parallel searches
pubmed_search_articles(queryTerm="colchicine cardiovascular randomized controlled trial", maxResults=15)
pubmed_search_articles(queryTerm="colchicine inflammation atherosclerosis mechanism", maxResults=10)
pubmed_search_articles(queryTerm="colchicine adverse effects cardiovascular", maxResults=10)

# Fetch top results
pubmed_fetch_contents(pmids=["31733140", "32865377", "37634428"])  # COLCOT, LoDoCo2, CLEAR

# Write to thread files

Step 4: Validate

  • Read all thread files
  • Cross-reference mortality data across trials
  • Note: CLEAR SYNERGY neutral vs positive COLCOT/LoDoCo2
  • Analyze: Patient population differences (post-ACS vs chronic CAD)
  • Write validation.md

Step 5: Synthesize

  • Read from files
  • Pattern: Inflammation hypothesis supported, but patient selection matters
  • Insight: Post-ACS (COLCOT) benefit clear; chronic stable CAD (CLEAR) less certain
  • Write synthesis.md

Step 6: Report

  • Structured report with evidence summary
  • Clear recommendation by patient type
  • All PMIDs cited
  • Complete reference list

Integration with Other Skills

This skill provides research foundation for:

  • cardiology-editorial → Use research output for trial analysis
  • cardiology-newsletter-writer → Research before writing
  • youtube-script-master → Research for script evidence base
  • x-post-creator-skill → Research before tweet generation

Workflow:

  1. User requests content on topic
  2. Run deep-researcher first (this skill)
  3. Pass validated findings to writing skill
  4. Writing skill cites PMIDs from research output

When NOT to Use This Skill

  • Simple factual questions (use PubMed MCP directly)
  • Trend discovery (use Perplexity, but don't cite)
  • Non-medical topics (this skill is optimized for PubMed)
  • Quick content needs (use writing skill directly with inline research)

Use this skill when you need:

  • 5+ sources synthesized
  • Complex multi-faceted questions
  • Rigorous evidence assessment
  • Comprehensive literature coverage

FAQ

What does the deep-researcher skill do?

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.

How do I install deep-researcher?

Run npx skills add https://github.com/drshailesh88/integrated_content_os --skill deep-researcher in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/deep-researcher/ (personal) or .claude/skills/deep-researcher/ (project).

Which AI agents can use deep-researcher?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is deep-researcher safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains deep-researcher?

It is published by drshailesh88 in drshailesh88/integrated_content_os. It has 72 recorded installs.

More from drshailesh88/integrated_content_os

View all →

social-media-trends-research

drshailesh88/integrated_content_os

Programmatic social media and marketing research using free tools: pytrends (Google Trends), yars (Reddit without API keys), and Perplexity MCP (Twitter/TikTok/Web). Use when finding trending topics in a niche, tracking keyword velocity and volume, monitoring Reddit discussions, discovering what's going viral, or researching content opportunities before writing. Zero-cost research stack with built-in rate limiting. Complements content-marketing-social-listening skill with executable code.

Marketing & SEO708 installs

medical-newsletter-writer

drshailesh88/integrated_content_os

Open the skill to read its SKILL.md instructions.

Docs & Writing73 installs

academic-chapter-writer

drshailesh88/integrated_content_os

Open the skill to read its SKILL.md instructions.

Docs & Writing59 installs

viral-content-predictor

drshailesh88/integrated_content_os

Open the skill to read its SKILL.md instructions.

52 installs

youtube-script-master

drshailesh88/integrated_content_os

Unified YouTube script creation for cardiology channels in Hinglish. Uses the COMPLETE research-engine pipeline (channel scraping, comment analysis, narrative monitoring, gap finding, view prediction) combined with RAG + PubMed for evidence. Data-driven topic selection, 15-30 min educational videos with 6-point voice check.

influencer-analyzer

drshailesh88/integrated_content_os

Open the skill to read its SKILL.md instructions.

49 installs

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。