Skip to main content
skill CX Codex

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

The research Claude Code skill traces library and API behavior to primary sources, or investigates why code took its current shape. It activates for lookups and questions about the history of a setting or constant.

MIT 1,000 installs ★ 10 updated 2026-10-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add pwguler/skills --skill research -a claude-code
Open on GitHub

What research does

The skill checks claims about a library, service, or standard against sources maintained by its owner. For questions about code history, it follows commits, pull requests, tickets, documents, and messages tied to the decision. Each claim in the resulting note gets a citation.

It writes a Markdown note to the requested path. If none is given, it uses a location where similar notes live, or picks one and reports it. Failed searches are recorded as gaps. Reading goes to a subagent when requested, when a draft spec triggers AFK decisions, or when the material is over about 2,000 lines or includes images.

What it helps with

  • verify API behavior against its owner’s documentation
  • trace a code setting to the decision behind it
  • write research notes with a source for every claim
  • delegate reading of a large specification

Example prompts for the agent

  • Check how this API behaves and cite a primary source for every claim.
  • Trace the Git history behind this constant and save a Markdown note at docs/research.md.
  • Give a subagent this specification to read, then return a note with citations.

How to install research

1Skills CLI (Vercel)

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

2Manually: put the files in place

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

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

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about research

How do I install research in Claude Code?

Run npx skills add pwguler/skills --skill research -a claude-code. The skill file is at ~/.claude/skills/research/SKILL.md.

What does research do?

It checks library and API behavior against primary sources, or investigates the history behind code decisions. It returns a Markdown note with citations attached to each claim.

How does research choose sources?

For behavior, it uses vendor documentation, source code, specifications, or a live endpoint. For decision history, it looks at commits, pull requests, tickets, documents, and messages.

Source text

SKILL.md · MIT
---
name: research
description: Find out what is true about a library, service, or standard from the owner of the facts. Or find out from its history why code has its shape. Write the answer down with a citation for each claim. Read this skill when the user asks why code, a constant, or a setting has its current form. Use it when the user asks to look something up, or to check how an API or tool really behaves. Use it also to give reading to a subagent while other work continues.
---

Do research in this session. A subagent reads instead in three cases. The user asks to give the reading to a subagent. A draft spec launches its AFK decisions. Or the payload is too large for the session: over about 2,000 lines, or images. [Guard the context window](references/guard-the-context-window.md) tells how. The subagent returns the note, not the payload.

1. Sort the question. A question about how a library, service, or standard behaves goes to its owner, in step 2. A question about why our code has its shape goes to its history, in step 3.
2. Read the owner of the fact: the vendor documentation, the source code, the specification, or a live endpoint response. A blog post, a forum answer, or a summary only points you to the owner. It is never the citation.
3. Read the history as [why.md](references/why.md) says. First pin the code. Then read each source that why.md lists. Name every source that the session cannot reach.
4. Return one Markdown note, with the source after each claim. Write the note to the path that the caller asked for. When the caller gave no path, use the place where the repo keeps similar notes. When there is no such place, choose a location, and name it in the reply.

Rules:

- A citation points at the owner. For behavior, that is the vendor, the source, the spec, or the live endpoint. For intent, it is the commit, PR, ticket, doc, or message that holds the decision.
- Never invent a citation. A search that finds nothing is an answer. Write it in the note as a gap.

© pwguler · MIT · pwguler/skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

research by other authors comes first.

research Matt Pocock 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. CX Codex +1 711,295installs research Weizhena This skill does preliminary research on a topic and drafts an outline: a list of items to study plus the fields to capture for each. Useful before an academic review or a tech comparison. CX Codex +1 798installs research daveebbelaar This Claude Code skill researches a macOS app idea before development. It sends parallel subagents to compare products, user feedback, features, and macOS APIs. CX Codex +1 1,000installs research Alireza Rezvani research is a Claude Code skill that routes research requests to specialist skills or runs a general search workflow. It shows the routing choice and lets the user override it. CX Codex +1 348installs research JuliusBrussee Gathers verified facts from docs and RFCs into a durable §R research log with sources, preventing agents from hallucinating external APIs. CX Codex +1 810installs context7-auto-research davila7 The context7-auto-research skill retrieves current library and framework references through the Context7 API. Use it when a Claude Code answer needs documentation for React, Next.js, Prisma, or another library. CX Codex +1 709installs software-research-assistant sammcj software-research-assistant — a subagent that digs into how to actually implement a library, framework, SDK, or API: pulls code examples, version facts, compatibility, and current best practices from live sources. CX Codex ★ 173repo stars github-deep-research bytedance github-deep-research runs multi-round research on any GitHub repository and writes a structured markdown report with a timeline, metrics and Mermaid diagrams. CX Codex +1 2,900installs firecrawl-deep-research firecrawl firecrawl-deep-research — a skill for Claude Code, Codex, Cursor, GitHub Copilot, and Gemini CLI that pulls evidence from the open web and delivers a structured analytical report with an executive summary, findings, and full sources. CX Codex +1 36,200installs tavily-research tavily-ai tavily-research — a skill for Claude Code and other platforms that gathers and weighs info from multiple sources. It triggers when performing in-depth analysis of markets, tech, or trends. CX Codex +1 25,100installs deep-research 199-biotechnologies deep-research — a skill for Claude Code, Codex, Cursor and other agents that runs a multi-phase research pipeline and produces a fully cited report with per-claim verification. CX Codex +1 10,500installs

From the same set15

The whole set →
write-skill write-skill — a Claude Code skill that creates and edits agent documents with behavioral verification. Activated when writing system prompts, CLAUDE.md, AGENTS.md, or repeating agent corrections. CX Codex +1 1,000installs parallel This Claude Code skill runs independent tasks through subagents in parallel. It activates only when asked to parallelize work, compare attempts, or split a job into parts. CX Codex +1 1,000installs core-interview core-interview — a skill for Claude Code that runs an interview loop through decision trees until every branch is settled. CX Codex +1 1,000installs debug debug is a Claude Code and Cursor skill that traces bug root causes step by step and verifies regression tests. CX Codex +1 1,000installs verify verify — a skill for Claude Code checks claims about completed or fixed work against fresh command output. It runs before a commit or PR, after changes, and before reporting that work is done or tested. CX Codex +1 1,000installs land land is a Claude Code skill that finishes a development branch through merge, PR, keep, or discard. It runs after implementation is complete. CX Codex +1 1,000installs drill A skill for Claude Code interviews the user about a plan or design until its decisions are settled. It runs for new features, unresolved designs, or a request to “drill this.” CX Codex +1 1,000installs implement implement — a skill for Claude Code and Codex that executes settled plans in thin test-driven slices. Runs when prompted to build code from a spec or slice plan. CX Codex +1 1,000installs

Project sponsors

Companies that keep this analytics open