本文へ移動
cccskills
無料GitHub で公開

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 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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

/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.

SourceWhen to useHow (tool names vary by agent)
Web search (Google)Authoritative articles, docs, official statementsYour agent's web search (e.g. WebSearch in Claude Code)
/last30daysWhat people are actually saying right now — Reddit, X, YouTube, HN, web recencyThe last30days skill, if installed. Otherwise skip it and note the gap
Specific URLsWhen the user hands over starting URLsYour agent's URL fetch (e.g. WebFetch), or curl + defuddle
Browsable pages (auth-walled, JS-heavy)Pricing pages, product tours, profilesagent-browser CLI (any agent with a shell)
MemoryPrior research / decisions / context the user already capturedyour agent's memory, or grep ${MAKERSKILLS_MEMORY:-${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/memory}/
NotionIf the topic touches a known Notion workspaceDirect Notion API (key in $NOTION_API_KEY, see reference_notion_api.md)
Research archivePrior /deep-research runs that touched this topicgrep ${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

Run each chosen source. For each result, capture:

  • The source (URL or system)
  • 1–3 sentence summary of what was said
  • Date / recency
  • Confidence in the source (high/medium/low)

Don't synthesize yet — just collect.

Step 4 — Synthesize

  1. Group findings by theme or sub-question
  2. Contradiction check — flag anywhere sources disagree. Don't average them; surface the disagreement.
  3. Confidence: high (multiple independent sources agree), medium (one strong source or several weak), low (single anecdote or speculation)
  4. Gaps: what would change the answer? What's NOT in the corpus?

Step 5 — Output the brief

Use this template:

# Research: <question>

**Date:** <YYYY-MM-DD>
**Decision this informs:** <one line>
**Confidence overall:** high / medium / low

## TL;DR
<2–4 sentences with the answer>

## Key findings

### 1. <Finding>
<2–4 sentences>. Sources: [1], [3], [5]

### 2. <Finding>
...

## Contradictions / uncertainty
- <where sources disagree, with each side cited>

## Gaps
- <what's missing from the corpus>
- <what to research next to close the gap>

## Recommended next steps
1. <action>
2. <action>

## Sources
[1] <Title> — <URL or system> (<date>) — <confidence>
[2] ...

Step 6 — Archive

Archives live in ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/deep-research/archive/ (create the directory if missing). Never write archives inside the skill's own folder — skill installs and upgrades re-sync from source and wipe anything saved there. Migration: if this skill's folder contains an old references/research-archive/ with user entries, move those files into the archive directory first.

Write the brief to <archive dir>/<YYYY-MM-DD>-<slug>.md so it's grep-able forever. Slug = kebab-case of the topic.

Also append a one-line entry to <archive dir>/INDEX.md (create if missing):

- 2026-06-15 — [<topic>](./<filename>.md) — <one-line TL;DR>

Step 7 — Surface

After archiving:

  • Show the full brief in chat
  • Tell the user the archive path
  • Offer: "Push to Notion or save to a project's docs?"

Composes with

  • business-brainstorm — calls this skill during the market validation step
  • /domain — when research includes "is the .com available"
  • /last30days — one of the data sources

Notes on quality

  • Always cite. Every claim in the brief needs a source pointer.
  • Recency matters — note dates on each source. For fast-moving topics (AI, startups), de-weight sources >12 months old.
  • Don't trust a single source for high-stakes claims. Re-search until you have at least 2 independent corroborations or surface the uncertainty.
  • No padding. If the answer is one paragraph, return one paragraph. The template is a maximum, not a minimum.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8552026年10月9日 更新

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X."

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8552026年10月9日 更新

Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse."

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8552026年10月9日 更新

decide

無料

When you have a decision to make and want a structured workflow that picks the load-bearing questions, walks through them, reaches a call (or "wait"), and archives the rationale for future reference. Based on the 37signals Guide to Making Decisions (38 questions) plus house additions like Q39 opportunity cost ("what does saying yes displace?"). Triages to 6–8 relevant questions per decision instead of forcing the full set. Archives every decision to ~/.config/makerskills/decide/archive/ with a revisit date so you can check later whether the call was right. Triggers on "/decide," "help me decide," "should I [X]," "I need to make a decision about," "stuck on a decision," "deciding between," "go/no-go on," "what should I do about." This is both the decision-making workflow AND the decision log — making the decision is the act of logging it.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8552026年10月9日 更新

domain

無料

When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle availability. Built on Laura Roeder's "work backwards from availability" method. Combines Vercel CLI, whois, Domainr, Namecheap, and agent-browser, each for what it reliably does. Workflow: budget → brainstorm → availability check → whois cross-check → price → aftermarket sweep (plus liveness probe and drop-watch) → bucket → negotiate → trademark + socials → buy. Triggers on "/domain," "find a domain," "check domain availability," "brainstorm a domain," "what .com is available for X," "domain hunt," "name my project," "is X.com available," "aftermarket price on X.com," "trademark check for X."

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8552026年10月9日 更新

ingest

無料

When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into structured work. Extracts decisions, action items (yours vs theirs), bugs/feature requests, and facts worth keeping; files GitHub issues in the right repo, captures to the second-brain vault, and drafts (never sends) the reply. Triggers on "/ingest", "ingest this", "here's my call with X," "here's the transcript," "this is from [person]," "[person] asked me this," "from [person]:", a pasted transcript with speaker labels, or a forwarded client message that clearly expects processing. Person→project routing lives in a private config; unknown senders get asked about once, then remembered.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8552026年10月9日 更新

coreyhaines31 のスキルをすべて見る

このスキルの問題を報告する