deep-research

Produces source-backed research summaries with recommendations, confidence levels, and cited references.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/Boulea7/ohmyclaude --skill deep-research-boulea7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-research
Source: https://github.com/Boulea7/ohmyclaude/tree/main/src/ohmyclaude/templates/skills/deep-research
Command: npx skills add https://github.com/Boulea7/ohmyclaude --skill deep-research-boulea7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Investigating a technical topic or comparing external options often leads to scattered notes, unverified claims, and decisions made on single sources. This Skill structures the investigation into sub-questions, prioritizes authoritative references, and delivers a decision-ready summary with explicit confidence levels. ## Core Features & Use Cases - Structured Research Workflow: Restates the research question, breaks it into sub-questions, and gathers evidence from official docs, primary repositories, and release notes. - Source-Backed Output: Delivers a summary, findings per sub-question, a recommendation, a confidence rating, and a source list. - Evidence Guardrails: Separates facts from inference, flags single-source claims, and prefers recent sources for fast-moving topics. - Use Case: Before adopting a new framework, ask for a comparison of two options; receive a concise recommendation backed by primary documentation with stated limitations. ## Quick Start Ask the assistant to research and compare two technical options for your project and deliver a source-backed recommendation with confidence and limitations.

Frequently Asked Questions about deep-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research a technical topic before implementation?▼

Restate the research question and the decision it informs, break it into sub-questions, then gather evidence from official docs, primary repositories, and release notes. Finish with a concise recommendation that includes confidence and limitations.

How to compare two technical options with sources?▼

Compare agreement, disagreement, and missing evidence across authoritative references for each option. Deliver findings per sub-question with a recommendation, a confidence rating, and a full source list.

What sources should technical research rely on?▼

Prefer official documentation, primary repositories, release notes, and authoritative references over blog posts or forums. For fast-moving topics, prioritize the most recent sources available.

How do I handle claims supported by only one source?▼

Flag single-source claims explicitly in the output rather than presenting them as established facts. The guardrails require separating facts from inference so readers can weigh evidence strength.

When is a structured research workflow not needed?▼

Skip it for trivial lookups answerable from a single official doc page or when no decision depends on the outcome. The workflow is designed for investigations that inform implementation choices.