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.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add mattpocock/skills/researchCompatible with
Supported agents
| 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:
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionresearchExecute the skills CLI command in your project's root directory to begin installation:
epx add mattpocock/skills/researchFetches research from mattpocock/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/research
Restart Cursor to activate research. Access via /researchin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
ask-matt
mattpocock/skills · engineering · same repo
to-spec
mattpocock/skills · engineering · same repo
triage
mattpocock/skills · engineering · same repo
write-a-prd
mattpocock/skills · Productivity · same repo
writing-great-skills
mattpocock/skills · productivity · same repo
zoom-out
mattpocock/skills · code · same repo
research reduced setup friction for our internal harness; good balance of opinion and flexibility.
research has been reliable in day-to-day use. Documentation quality is above average for community skills.
research is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: research is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: research is focused, and the summary matches what you get after install.
I recommend research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: research is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added research from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
research fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
research has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 43