# Deep Research

When you want multi-source, multi-step research on a topic, competitor research before...

- Repository: https://github.com/coreyhaines31/makerskills (880 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add coreyhaines31/makerskills --skill deep-research -g -a claude-code -y`
Codex: `npx skills add coreyhaines31/makerskills --skill deep-research -g -a codex -y`
Cursor: `npx skills add coreyhaines31/makerskills --skill deep-research -g -a cursor -y`
Gemini CLI: `npx skills add coreyhaines31/makerskills --skill deep-research -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add coreyhaines31/makerskills`

## Description

When you want multi-source, multi-step research on a topic, competitor research before a sales call, market research for a new business idea, positioning angles, due diligence on a partnership or podcast guest, tech decision research (which DB, which auth), or any \"I need to actually understand X.\" Combines web search, URL fetch, agent-browser, last30days (Reddit/X/YouTube/HN/web recency), memory, and Notion. Outputs a structured brief with citations, contradictions, gaps, and recommended next steps. Archives every research run to ~/.config/makerskills/deep-research/archive/ so past work is searchable. Triggers on \"/deep-research,\" \"research X,\" \"investigate X,\" \"do a deep dive on X,\" \"look into X,\" \"what's actually happening with X,\" \"due diligence on X,\" \"validate this market.\" Differs from a one-shot web search: this is multi-pass with verification. Not for standing monitoring (radar) or pulling one post or video (social-fetch, watch-video).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /deep-research, Multi-source research with archive

Plans, executes, and synthesizes research from multiple sources. Archives the output so the corpus compounds.

## Step 1, Frame the question

Restate the research question in one tight sentence. If ambiguous, ask the user:
- What's the decision this research will inform?
- What's the minimum useful answer? (Saves over-researching.)
- Any sources to prioritize or avoid?

Output: `**Research question:** <one sentence>`

## Step 2, Plan the sources

Pick from this menu based on the question type. Note which sources you'll hit and why.

| Source | When to use | How (tool names vary by agent) |
|---|---|---|
| Web search (Google) | Authoritative articles, docs, official statements | Your agent's web search (e.g. `WebSearch` in Claude Code) |
| `/last30days` | What people are *actually saying* right now, Reddit, X, YouTube, HN, web recency | The `last30days` skill, if installed. Otherwise skip it and note the gap |
| Specific URLs | When the user hands over starting URLs | Your agent's URL fetch (e.g. `WebFetch`), or `curl` + `defuddle` |
| Browsable pages (auth-walled, JS-heavy) | Pricing pages, product tours, profiles | `agent-browser` CLI (any agent with a shell) |
| Memory | Prior research / decisions / context the user already captured | your agent's memory, or grep `${MAKERSKILLS_MEMORY:-${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/memory}/` |
| Notion | If the topic touches a known Notion workspace | Direct Notion API (key in `$NOTION_API_KEY`, see `reference_notion_api.md`) |
| Research archive | Prior `/deep-research` runs that touched this topic | grep `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/deep-research/archive/` |

Run discovery passes **in parallel** where possible. Sequential only when one source needs another's output (e.g., agent-browser a URL discovered by web search).

## Step 3, Execute discovery

The rest: https://github.com/coreyhaines31/makerskills/blob/HEAD/skills/deep-research/SKILL.md