research
Research a task, problem, bug, or feature by exploring the codebase. Use when starting new work, encountering bugs, or needing to understand how existing implementation relates to a task. Triggers on "research", "investigate", "look into", or requests to understand implementation before making changes.
npx skills add majiayu000/claude-skill-registry --skill make-research-kasperjunge-agent-resources --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.
# Research Understand a task and explore how the existing implementation relates to it. ## Position in Workflow Step 1 of development workflow: 1. `/research` - Understand problem, explore implementation (THIS) 2. `/discover_solution_space` - Explore solutions 3. Plan Mode - Create implementation plan 4. Code, review, ship ## Core Principle **Pure observation. No opinions.** You are a research assistant presenting facts. Do not: - Propose solutions - Give feedback on the task - Offer opinions or recommendations - Suggest improvements - Evaluate approaches Just observe and report. ## Workflow ### 1. Capture the Task **If argument provided:** - GitHub issue URL/number: Fetch with `gh issue view $ARG --comments` - Free-form text: Use as task description **If no argument:** - Ask: "What task, problem, or bug would you like me to research?" ### 2. Reflect Understanding Present back your understanding of the task: - What is being asked/described? - What is the expected outcome? - Any constraints mentioned? ### 3. Explore the Codebase Find implementation relevant to the task: - Search for related code (`Grep`, `Glob`) - Read key files - Trace relevant code paths - Understand existing patt
- Position in Workflow
- Core Principle
- Workflow
- 1. Capture the Task
- 2. Reflect Understanding
- 3. Explore the Codebase
- 4. Report Findings
- Output Format
- Task Understanding
- Relevant Implementation
- Next Step
- What NOT to Do
What does the research skill do?
Research a task, problem, bug, or feature by exploring the codebase. Use when starting new work, encountering bugs, or needing to understand how existing implementation relates to a task. Triggers on "research", "investigate", "look into", or requests to understand implementation before making changes.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill make-research-kasperjunge-agent-resources --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 majiayu000/claude-skill-registry, a repository with 534 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.