ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
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.
Claude Code
$ npx -y skills add mattpocock/skills --skill research --agent claude-code
Codex
$ npx skills add mattpocock/skills --skill research -a codex -y
Cursor
$ npx skills add mattpocock/skills --skill research -a cursor -y
Gemini CLI
$ npx skills add mattpocock/skills --skill research -a gemini-cli -y
GitHub Copilot
$ npx skills add mattpocock/skills --skill research -a github-copilot -y
OpenCode
$ npx skills add mattpocock/skills --skill research -a opencode -y
Windsurf
$ npx skills add mattpocock/skills --skill research -a windsurf -y
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. Start it with a fresh context window.
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.
My agent skills that I use every day to do real engineering - not vibe coding. Developing real applications is hard. Approaches like GSD, BMAD, and Spec-Kit try to help by owning the process.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this…
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening…
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something…
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or…
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit…