nsheaps/deep-research
plugins/deep-research/skills/deep-research/SKILL.md
Use this skill when investigating complex questions that require multiple sources, angles, or synthesis. The deep-research plugin provides a 3-agent research team: lead-researcher (orchestrator), sub-researcher (workers), and critical-reviewer (validator). Trigger when: - Investigation requires 3+ sources (docs, issues, source code, web) - You need to synthesize findings across multiple sources into a coherent report - Previous research findings need source-level verification - You're investigating behavior differences between documented and observed behavior - Competitive analysis or technology evaluations Do NOT trigger for: - Simple lookups ("what flag does X?") - Single-source answers - Basic codebase navigation (use Grep/Glob directly)
$ install --global
skillsauthnpx skillsauth add nsheaps/ai-mktpl deep-researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 4:08 PM26.4s1 file scanned
SKILL.md
- name:
- deep-research
- description:
- |
- Use this skill when investigating complex questions that require multiple sources, angles, or synthesis. The deep-research plugin provides a 3-agent research team:
- lead-researcher (orchestrator), sub-researcher (workers), and critical-reviewer (validator).
Deep Research -- 3-Agent Research System
A multi-agent research system for complex, evidence-based investigations.
Architecture
The deep-research plugin uses three specialized agents:
User Request
|
v
lead-researcher (orchestrator)
|-- Plans 5-10 search angles
|-- Dispatches sub-researchers (one per angle)
| |-- sub-researcher 1: Angle A (web + docs)
| |-- sub-researcher 2: Angle B (source code)
| |-- sub-researcher 3: Angle C (community)
| |-- ... (up to 10 angles)
|
|-- Collects findings from all sub-researchers
|-- Dispatches critical-reviewer to validate
|-- Addresses gaps from review
|-- Synthesizes final report
|
v
Report saved to .claude/tmp/research-<topic>.md
Agents
| Agent | Role | Tools | Restrictions | | --------------------- | ------------------------------------------------------------------------ | -------------------------------------------- | -------------------------------------------- | | lead-researcher | Orchestrator -- plans angles, dispatches workers, synthesizes report | Read, Write, Grep, Glob, Agent | No web search (delegates to sub-researchers) | | sub-researcher | Worker -- investigates one specific angle, writes findings to file | Read, Write, Grep, Glob, WebSearch, WebFetch | No Edit (shouldn't modify existing files) | | critical-reviewer | Validator -- challenges assumptions, identifies gaps, suggests follow-up | Read, Grep, Glob, WebSearch, WebFetch | No Edit, no Write (read-only reviewer) |
How to Invoke
For complex, multi-source investigations, spawn the lead-researcher agent:
Agent(lead-researcher, "Investigate how Claude Code spawns teammates -- check source code, official docs, GitHub issues, and community implementations. Save report to .claude/tmp/research-teammate-spawning.md")
The lead-researcher will autonomously:
- Plan research angles
- Dispatch sub-researchers for each angle
- Collect and cross-reference findings
- Run critical review
- Produce final report with confidence levels and citations
When to Use Deep Research vs Simple Lookups
| Situation | Use | | ------------------------------------------------ | --------------------------------------------------------- | | "What flag enables X?" | Direct answer -- no agent needed | | "How does X work internally?" | lead-researcher -- multi-source investigation | | "Compare X vs Y vs Z for our use case" | lead-researcher -- parallel sub-researchers per option | | "Find the file that does X" | Grep/Glob -- no agent needed | | "Why does X behave differently than documented?" | lead-researcher -- needs source + docs + issues | | "What's the best practice for X?" | Context7 or WebSearch -- single source usually sufficient |
Output Format
Reports are saved to .claude/tmp/research-<topic>.md with:
- Executive Summary: 2-3 sentence answer
- Methodology: Angles pursued, sources consulted
- Findings: Each finding with confidence level and citations
- Critical Review Notes: What was challenged, how addressed
- Open Questions: What remains unanswered
- Sources: Complete list of all references
Confidence Level Framework
| Level | Meaning | Evidence Required | | :-------------- | :------------------------------------------- | :-------------------------------------- | | Very High | Confirmed from source code or official specs | Primary source + verified | | High | Multiple independent sources agree | 3+ sources or official docs + community | | Medium-High | Strong evidence with some inference | 2 sources + logical reasoning | | Medium | Plausible with supporting evidence | 1 source + consistent behavior | | Low | Hypothesis based on limited evidence | Inference only |
Tips
- Save everything to files -- Context compaction destroys in-memory state. Files survive.
- The lead-researcher dispatches sub-researchers -- You don't need to manage them manually.
- Critical review catches gaps -- The critical-reviewer challenges weak evidence before the report is finalized.
- Confidence levels are mandatory -- Every finding needs one.
- Correct previous research openly -- Being wrong in early phases is expected and documented.
References
- Claude Code Agents documentation
- Claude Code Plugins documentation
Related Skills
nsheaps/claude-code
tools
VerifiedTrustedCommunity
Reference material for Claude Code internals — the on-disk layout under ~/.claude and project-scope .claude, the plugin cache, session-env propagation, and the full hook lifecycle. Auto-recall when working on Claude-Code-related tasks: writing or debugging hooks, authoring plugins, inspecting session state, troubleshooting why an env var is or isn't visible to a Bash tool call, or when paths under ~/.claude or ~/.claude/plugins/ come up.
3SKILL.mdUpdated May 6, 2026
nsheaps/github-app-token
development
VerifiedTrustedCommunity
Manage GitHub App installation tokens in Claude Code sessions. Use when tokens expire, auth errors occur in long-running sessions, or when setting up GitHub App credentials for agent teams. <example>my github token expired</example> <example>refresh the github app token</example> <example>check token status</example> <example>set up github app authentication for this session</example>
3SKILL.mdUpdated Apr 22, 2026
nsheaps/auto-config
tools
VerifiedTrustedCommunity
Auto-detect project formatting tools and configure edit-utils settings
3SKILL.mdUpdated Apr 22, 2026
nsheaps/op
tools
VerifiedTrustedCommunity
Use this skill when the user asks about 1Password, secrets management, retrieving credentials, using op CLI, service accounts, secret references, vault operations, or any task involving the 1Password CLI (op). Also use when needing to inject secrets into environment variables, read passwords or API keys from 1Password, or manage 1Password items from the command line.
3SKILL.mdUpdated Apr 22, 2026