deep-research
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 WebSearch, WebFetch, 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
npx skills add coreyhaines31/makerskills --skill deep-research --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /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 | Tool | |---|---|---| | Web search (Google) | Authoritative articles, docs, official statements | `WebSearch` | | `/last30days` | What people are *actually saying* right now — Reddit, X, YouTube, HN, web recency | `Skill({skill: "last30days", args: "<topic>"})` | | Specific URLs | When the user hands over starting URLs | `WebFetch` | | Browsable pages (auth-walled, JS-heavy) | Pricing pages, product tours, profiles | `agent-browser` via the `compound-engineering:agent-browser` skill | | Memory | Prior research / decisions / context the user already captured | grep `~/.claude/memor
- Step 1 — Frame the question
- Step 2 — Plan the sources
- Step 3 — Execute discovery
- Step 4 — Synthesize
- Step 5 — Output the brief
- Step 6 — Archive
- Step 7 — Surface
- Composes with
- Notes on quality
What does the deep-research skill do?
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 WebSearch, WebFetch, 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
How do I install it?
Run `npx skills add coreyhaines31/makerskills --skill deep-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From coreyhaines31/makerskills, a repository with 500 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.