Skip to main content
skill Claude Code

research · mattpocock — Claude Code skill: what it does, how to install

Researches a question through primary sources and saves the findings as a Markdown file in the repository. Use it for API facts, documentation checks, and delegated reading.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add mattpocock/skills
/plugin install mattpocock-skills@mattpocock
Open on GitHub

What research does

research starts a background agent to investigate a question while you continue working in Claude Code. The agent checks primary material such as official documentation, source code, specifications, and first-party APIs. Each claim in the findings is cited back to its source.

The skill writes one Markdown file and follows the repository's existing convention for research notes. If the project has no convention, it chooses a sensible location and reports the path. Install it when research needs to remain in the repo with traceable evidence; skip it for a brief answer that does not need a file.

What it helps with

  • verify a fact against official documentation
  • collect API findings in a Markdown file
  • trace a claim to source code or a specification
  • delegate reading work to a background agent
  • keep research notes with source citations

Example prompts for the agent

  • "Research this API question and save the findings in the repository."
  • "Check the documentation for this issue and write a Markdown note with sources."
  • "Ask a background agent to review the specification and record confirmed facts."

How to install research

1Plugin marketplace

/plugin marketplace add mattpocock/skills
/plugin install mattpocock-skills@mattpocock

This installs the whole mattpocock-skills plugin with all its skills

2Skills CLI (Vercel)

npx skills add mattpocock/skills --skill research -a claude-code

3Manually: put the files in place

~/.claude/skills/research/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/research/

From the same set32

The whole set →
grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. Claude Code 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. Claude Code 1,163,035installs tdd Matt Pocock Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details. Claude Code 1,141,062installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. Claude Code 1,052,851installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. Claude Code 1,038,491installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. Claude Code 990,453installs prototype Matt Pocock Creates throwaway prototypes for checking state logic or exploring UI before committing the decision to the main codebase. Claude Code 986,201installs

Other versions of research

Similar

Questions about research

How do I install research in Claude Code?

Add the marketplace with /plugin marketplace add mattpocock/skills, then install the skill using /plugin install mattpocock-skills@mattpocock.

What does the research skill do?

It sends research work to a background agent, checks claims against primary sources, and writes one cited Markdown file in the repository.

Where does research save its findings?

It uses the repository's existing convention for research notes. If there is no convention, it selects a sensible location and reports the path.

Source text

SKILL.md · MIT
---
name: research
description: Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
---

Spin up a **background agent** to do the research, so you keep working while it reads.

Its job:

1. Investigate the question against **primary sources** (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.
2. Write the findings to a single Markdown file, citing each claim's source.
3. Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.

© Matt Pocock · MIT · mattpocock/skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor