deep-research
Use when the user needs multi-source research with citation tracking, evidence persistence, and structured report generation. Triggers on "deep research", "comprehensive analysis", "research report", "compare X vs Y", "analyze trends", or "state of the art". Not for simple lookups, debugging, or questions answerable with 1-2 searches.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/199-biotechnologies-claude-deep-research-skill)HTML
<a href="/listings/199-biotechnologies-claude-deep-research-skill"><img src="/api/listings/199-biotechnologies-claude-deep-research-skill/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
# Clone into Claude Code skills directory git clone https://github.com/199-biotechnologies/claude-deep-research-skill.git ~/.claude/skills/deep-research
No additional dependencies required for basic usage.
Optional: search-cli (multi-provider search)
For aggregated search across Brave, Serper, Exa, Jina, and Firecrawl:
brew tap 199-biotechnologies/tap && brew install search-cli search config set keys.brave YOUR_KEY # configure at least one provider
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 108 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: deep-research
- description: Use when the user needs multi-source research with citation tracking, evidence persistence, and structured report generation. Triggers on "deep research", "comprehensive analysis", "research report", "compare X vs Y", "analyze trends", or "state of the art". Not for simple lookups, debugging, or questions answerable with 1-2 searches.
- ---
- # Deep Research
- ## Core Purpose
- Deliver citation-tracked research reports through a structured pipeline with evidence persistence, source identity management, claim-level verification, and progressive context management.
- **Autonomy Principle:** Operate independently. Infer assumptions from context. Only stop for critical errors or incomprehensible queries. Surface high-materiality assumptions explicitly in the Introduction and Methodology rather than silently defaulting.
- ---
- ## Decision Tree
- ```
- Request Analysis
- +-- Simple lookup? --> STOP: Use WebSearch
- +-- Debugging? --> STOP: Use standard tools
- +-- Complex analysis needed? --> CONTINUE
- Mode Selection
- +-- Initial exploration --> quick (3 phases, 2-5 min)
- +-- Standard research --> standard (6 phases, 5-10 min) [DEFAULT]
- +-- Critical decision --> deep (8 phases, 10-20 min)
- +-- Comprehensive review --> ultradeep (8+ phases, 20-45 min)
- ```
- **Default assumptions:** Technical query = technical audience. Comparison = balanced perspective. Trend = recent 1-2 years.
- ---
- ## Workflow Overview
- | Phase | Name | Quick | Std | Deep | Ultra |
- |-------|------|-------|-----|------|-------|
- | 1 | SCOPE | Y | Y | Y | Y |
- | 2 | PLAN | - | Y | Y | Y |
- | 3 | RETRIEVE | Y | Y | Y | Y |
- | 4 | TRIANGULATE | - | Y | Y | Y |
- | 4.5 | OUTLINE REFINEMENT | - | Y | Y | Y |
- | 5 | SYNTHESIZE | - | Y | Y | Y |
- | 6 | CRITIQUE | - | - | Y | Y |
- | 7 | REFINE | - | - | Y | Y |
- | 8 | PACKAGE | Y | Y | Y | Y |
- **Note:** Phases 3-5 operate as an evidence loop per section (retrieve → evidence store → refine outline → draft → verify claims → delta-retrieve if needed), not as strict sequential gates.
- ---
- ## Execution
- **On invocation, load relevant reference files:**
- 1. **Phase 1-7:** Load [methodology.md](./reference/methodology.md) for detailed phase instructions
- 2. **Phase 8 (Report):** Load [report-assembly.md](./reference/report-assembly.md) for progressive generation
- 3. **HTML/PDF output:** Load [html-generation.md](./reference/html-generation.md)
- 4. **Quality checks:** Load [quality-gates.md](./reference/quality-gates.md)
- 5. **Long reports (>18K words):** Load [continuation.md](./reference/continuation.md)
- **Templates:**
- - Report structure: [report_template.md](./templates/report_template.md)
- - HTML styling: [mckinsey_report_template.html](./templates/mckinsey_report_template.html)
- **Scripts:**
- - `python scripts/validate_report.py --report [path]`
- - `python scripts/verify_citations.py --report [path]`
- - `python scripts/md_to_html.py [markdown_path]`
- ---
- ## Output Contract
- **Required sections:**
- - Executive Summary (200-400 words)
- - Introduction (scope, methodology, assumptions)
- - Main Analysis (4-8 findings, 600-2,000 words each, cited)
- - Synthesis & Insights (patterns, implications)
- - Limitations & Caveats
- - Recommendations
- - Bibliography (COMPLETE - every citation, no placeholders)
- - Methodology Appendix
- **Output files (all to `~/Documents/[Topic]_Research_[YYYYMMDD]/`):**
- - Markdown (primary source of truth)
- - `sources.jsonl` — stable source registry with canonical IDs
- - `evidence.jsonl` — append-only evidence store with quotes and locators
- - `claims.jsonl` — atomic claim ledger with support status
- - `run_manifest.json` — query, mode, assumptions, provider config
- - HTML (McKinsey style, auto-opened)
- - PDF (professional print, auto-opened)
- **Quality standards:**
- - 10+ sources, 3+ per major claim (cluster-independent, not just count)
- - All factual claims cited immediately [N] with evidence backing in `evidence.jsonl`
- - Claim-support verification mandatory: no unsupported factual claims pass delivery
- - No placeholders, no fabricated citations
- - Prose-first (>=80%), bullets sparingly
- ---
- ## When to Use / NOT Use
- **Use:** Comprehensive analysis, technology comparisons, state-of-the-art reviews, multi-perspective investigation, market analysis.
- **Do NOT use:** Simple lookups, debugging, 1-2 search answers, quick time-sensitive queries.
README.md · README · 119 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # Deep Research Skill for Claude Code
- Enterprise-grade research engine for Claude Code. Produces citation-backed reports with source credibility scoring, multi-provider search, and automated validation.
- ## Installation
- ```bash
- # Clone into Claude Code skills directory
- git clone https://github.com/199-biotechnologies/claude-deep-research-skill.git ~/.claude/skills/deep-research
- ```
- No additional dependencies required for basic usage.
- ### Optional: search-cli (multi-provider search)
- For aggregated search across Brave, Serper, Exa, Jina, and Firecrawl:
- ```bash
- brew tap 199-biotechnologies/tap && brew install search-cli
- search config set keys.brave YOUR_KEY # configure at least one provider
- ```
- ## Usage
- ```
- deep research on the current state of quantum computing
- ```
- ```
- deep research in ultradeep mode: compare PostgreSQL vs Supabase for our stack
- ```
- ## Research Modes
- | Mode | Phases | Duration | Best For |
- |------|--------|----------|----------|
- | Quick | 3 | 2-5 min | Initial exploration |
- | Standard | 6 | 5-10 min | Most research questions |
- | Deep | 8 | 10-20 min | Complex topics, critical decisions |
- | UltraDeep | 8+ | 20-45 min | Comprehensive reports, maximum rigor |
- ## Pipeline
- Scope → Plan → **Retrieve** (parallel search + agents) → Triangulate → Outline Refinement → Synthesize → Critique (with loop-back) → Refine → Package
- Key features:
- - **Step 0**: Retrieves current date before searches (prevents stale training-data year assumptions)
- - **Parallel retrieval**: 5-10 concurrent searches + 2-3 focused sub-agents returning structured evidence objects
- - **First Finish Search**: Adaptive quality thresholds by mode
- - **Critique loop-back**: Phase 6 can return to Phase 3 with delta-queries if critical gaps found
- - **Multi-persona red teaming**: Skeptical Practitioner, Adversarial Reviewer, Implementation Engineer (Deep/UltraDeep)
- - **Disk-persisted citations**: `sources.json` survives context compaction and continuation agents
- ## Output
- Reports saved to `~/Documents/[Topic]_Research_[Date]/`:
- - Markdown (primary source of truth)
- - HTML (McKinsey-style, auto-opened in browser)
- - PDF (professional print via WeasyPrint)
- Reports >18K words auto-continue via recursive agent spawning with context preservation.
- ## Quality Standards
- - 10+ sources, 3+ per major claim
- - Executive summary 200-400 words
- - Findings 600-2,000 words each, prose-first (>=80%)
- - Full bibliography with URLs, no placeholders
- - Automated validation: `validate_report.py` (9 checks) + `verify_citations.py` (DOI/URL/hallucination detection)
- - Validation loop: validate → fix → retry (max 3 cycles)
- ## Search Tools
- | Tool | Priority | Setup |
- |------|----------|-------|
- | search-cli | **Primary** — all searches go here first | `brew install search-cli` + API keys |
- | WebSearch | Fallback — if search-cli fails or rate-limited | None (built-in) |
- | Exa MCP | Optional — semantic/neural search alongside search-cli | MCP config |
- ## Architecture
- ```
- deep-research/
- ├── SKILL.md # Skill entry point (lean, ~100 lines)
- ├── reference/
- │ ├── methodology.md # 8-phase pipeline details
- │ ├── report-assembly.md # Progressive generation strategy
- │ ├── quality-gates.md # Validation standards
- │ ├── html-generation.md # McKinsey HTML conversion
- │ ├── continuation.md # Auto-continuation protocol
- │ └── weasyprint_guidelines.md # PDF generation
- ├── templates/
- │ ├── report_template.md # Report structure template
- │ └── mckinsey_report_template.html # HTML report template
- ├── scripts/
- │ ├── validate_report.py # 9-check structure validator
- │ ├── verify_citations.py # DOI/URL/hallucination checker
- │ ├── source_evaluator.py # Source credibility scoring
- │ ├── citation_manager.py # Citation tracking
- │ ├── md_to_html.py # Markdown to HTML converter
- │ ├── verify_html.py # HTML verification
- │ └── research_engine.py # Core orchestration engine
- └── tests/
- └── fixtures/ # Test report fixtures
- ```
- ## Version History
- | Version | Date | Changes |
- |---------|------|---------|
- | 2.3.1 | 2026-03-19 | Template/validator harmonization, structured evidence, critique loop-back, multi-persona red teaming |
- | 2.3 | 2026-03-19 | Contract harmonization, search-cli integration, dynamic year detection, disk-persisted citations, validation loops |
- | 2.2 | 2025-11-05 | Auto-continuation system for unlimited length |
- | 2.1 | 2025-11-05 | Progressive file assembly |
- | 1.0 | 2025-11-04 | Initial release |
- ## License
- MIT - modify as needed for your workflow.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.