Skip to content
Content
Skill

/research-brief

Produce a structured research brief on any topic — TL;DR, cited key facts, notable quotes, suggested angles, open questions. 3-15 queries by depth, multi-source (WebSearch + WebFetch + Firecrawl/Exa MCP). Markdown for downstream skills. Use when: 'research X', 'gather facts on

From plugin
mikefluff-skills
1944 skills2 commands1 hook
Install
$ npx -y skills add Mikefluff/skills --skill research-brief --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/research-brief

Context preview

The summary Claude sees to decide when to auto-load this skill.

Produce a structured research brief on any topic — TL;DR, cited key facts, notable quotes, suggested angles, open questions. 3-15 queries by depth, multi-source (WebSearch + WebFetch + Firecrawl/Exa MCP). Markdown for downstream skills. Use when: 'research X', 'gather facts on

SKILL.md

research-brief.SKILL.md
name: research-brief
description: "Produce a structured research brief on any topic — TL;DR, cited key facts, notable quotes, suggested angles, open questions. 3-15 queries by depth, multi-source (WebSearch + WebFetch + Firecrawl/Exa MCP). Markdown for downstream skills. Use when: 'research X', 'gather facts on Y', 'brief me on Z', 'prepare research for a post / carousel / reel'."

license: MIT
allowed-tools:
  - Read
  - Write
  - Edit
  - WebSearch
  - WebFetch
  - Bash
  - Grep
  - Glob

<objective> Produce a 200-1000 word research brief on a topic, with cited facts, quotes, suggested narrative angles, and open questions. Save to a markdown file under `./generated/research/<topic-slug>.md` so downstream skills can ingest via `--research <path>`.

This skill does NOT:

  • write the final post / carousel / reel (that's `essay-write` / `viral-text` / `carousel-builder` / `reel-builder`)
  • run literature reviews requiring paywalled sources (Google Scholar, Pubmed — flag those as `out-of-reach` in the brief)
  • give real-time prices / stocks / API quotas (use a dedicated tool, not WebSearch)
  • replace primary-source domain research where the user already has expertise — the brief is a STARTING point, not a final word

Use when the user wants to gather context before writing, or wants a structured handoff to the downstream content skills. </objective>

ROLE

Read the topic → choose depth + sources → run search queries → extract facts with citations → synthesize into the canonical brief structure → save to `./generated/research/<slug>.md` → return the path so other skills can pick it up.

PIPELINE

1. **Clarify if topic is broad**. "AI" / "marketing" — ask once for a sharper angle ("AI for which audience / which use case?"). Otherwise proceed.

2. **Pick depth**:

  • `--depth quick`: 3-5 WebSearch queries, 200-400 word brief. ~1-2 min wall time.
  • `--depth standard` (default): 7-10 queries, WebFetch the top 3 results per cluster, 500-800 word brief. ~3-5 min.
  • `--depth deep`: 12-20 queries, includes Firecrawl/Exa MCP if available, 800-1500 word brief. ~5-10 min.

3. **Probe available sources** (see `references/mcp-probe.md`):

  • `WebSearch` — always available inside Claude Code.
  • `WebFetch` — always available.
  • `mcp__firecrawl__*` — present if the user has Firecrawl MCP installed. Best for deep-crawl scrape of a known site.
  • `mcp__exa__*` — present if Exa MCP installed. Best for neural/semantic search and finding non-obvious sources.
  • Gracefully degrade: if a tool isn't present, note "(skipped — Firecrawl MCP not configured)" in the Sources section.

4. **Run query batches** — see `references/methodology.md`:

  • Cluster A: foundational definitions (what is X, history, key actors). 2-4 queries.
  • Cluster B: recent developments / news (last 6-12 months). 2-4 queries.
  • Cluster C: contrarian / failure modes / criticism. 1-3 queries.
  • Cluster D: data + numbers + named studies. 2-4 queries.
  • Cluster E (deep only): primary sources, original papers, founder interviews. 2-5 queries.

5. **Extract**: for each result, pull facts with the source URL, distinguishing between:

  • **Verified facts** (≥2 corroborating sources OR a primary source)
  • **Single-source claims** (note as such — `[single-source]`)
  • **Quotes** (named attribution + URL + access date)
  • **Open questions** (claims that couldn't be verified — list them as research gaps, don't fabricate confirmations)

6. **Synthesize into canonical structure** (see `references/output-format.md`):

   # <Topic>

   _Brief generated: <date>. Sources used: <N>. Depth: <quick|standard|deep>._

   ## TL;DR
   <3-sentence summary>

   ## Key facts
   - <fact> [#1]
   - <fact> [#2]
   - ...

   ## Notable quotes
   > "<quote>" — <attribution>, <publication>, <date> [#N]

   ## Suggested angles
   1. <angle one> — for <audience/format>
   2. <angle two> — ...
   3. <angle three> — ...

   ## Open questions
   - <unresolved question that came up>
   - ...

   ## Out of reach / requires expertise
   - <flag for things the user should verify manually>

   ## Sources
   1. [<title>](<url>) — accessed <YYYY-MM-DD>
   2. ...

7. **Write to disk**: `./generated/research/<topic-slug>-<YYYYMMDD>.md`. Slug = `kebab-case-of-topic`, max 40 chars. If file exists, append timestamp.

8. **Return path + 1-line summary** on stdout: `Brief written to ./generated/research/...md (N sources, TL;DR: ...)`.

MODES

  • `research-brief <topic>` — default standard depth
  • `research-brief <topic> --depth quick|standard|deep` — control breadth
  • `research-brief <topic> --sources websearch,webfetch,firecrawl,exa` — restrict to specific tools (default: all available)
  • `research-brief <topic> --output <path>` — custom output path
  • `research-brief <topic> --format brief|outline|article-ready` — controls verbosity (200 / 500 / 1000+ words)
  • `research-brief <topic> --angles 3` — number of suggested narrative angles in the output (default 3)
  • `research-brief <topic> --lang en|ru|mixed` — write the brief in that language (sources can be any)
  • `research-brief <topic> --for carousel|reel|post|essay|landing` — bias the angles + structure toward a downstream format

REFERENCES (load on demand)

| File | When to load | |---|---| | [references/methodology.md](references/methodology.md) | Always at step 4 — cluster definitions + query patterns + de-dup rules | | [references/sources.md](references/sources.md) | Picking sources — what to trust, what to flag, primary vs. secondary, when to escalate to deep | | [references/output-format.md](references/output-format.md) | Step 6 — exact section structure, citation format, slug rules, multilingual handling | | [references/mcp-probe.md](references/mcp-probe.md) | Step 3 — how to detect Firecrawl/Exa MCP presence, what each adds, graceful fallback |

EXAMPLES

See [examples/before-after.md](examples/before-after.md) — 3 calibration runs: standard depth on a tech topic (p

Read more
Ships withmikefluff-skills

44 skills for Claude Code that make content — and refuse to let it read like a machine made it. Prose editing that strips the tells. Prompt engineering for 40+ image, video and music models, with optional one-command execution against the real APIs.

Get the whole plugin
Stats
19
Stars
1
Forks
Maintained
Maintenance
Python
Language
MIT
License
1mo ago
Last commit
3mo ago
Created

Repo: Mikefluff/skills

Other skills on mikefluff-skills.