ask-matt
Helps your agent choose the best tool or workflow for a situation. It acts as a router for the available tools.
What it does
This agent helps you choose the best tool (skill) for what you need to do. It acts like a guide, asking about your task and suggesting which path to take.
When to use it
- ✓When you don't know which command to use.
- ✓When starting a new project and needing guidance.
- ✓When you want to understand the available options for your task.
Example of what to ask your AI
“I need to organize my ideas for a new app, which tool should I use?”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
It asks questions about your needs and, based on your answers, indicates which 'skill' (tool) is most suitable. It's like a receptionist directing you to the right department.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill ask-mattOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/ask-matt/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Ask Matt
When to Use
Use when this workflow matches the user request: Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Source: mattpocock/skills (MIT).
You don't remember every skill, so ask.
A flow is a path through the skills. Most paths run along one main flow, and two on-ramps merge onto it. Everything else is standalone.
The main flow: idea → ship
The route most work travels. You have an idea and want it built.
/grill-with-docs— sharpen the idea by interview. Start here when you have a codebase: it's stateful, retaining what it learns inCONTEXT.mdand ADRs. (No codebase? Use/grill-me— see Standalone.)- Branch — can you settle every question in conversation? If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by
/handoffin both directions (see Crossing sessions):/handoffout, then open a fresh session against that file,/prototypeto answer the question with throwaway code,/handoffback what you learned, and reference it from the original idea thread.
- Branch — is this a multi-session build?
- Yes →
/to-prd(turn the thread into a PRD) →/to-issues(split the PRD into independently-grabbable issues). Because the issues are independent, clear context between each one: start a fresh session per issue and kick off/implementby passing it the PRD and the single issue to work on. - No →
/implementright here, in the same context window.
- Yes →
Context hygiene
Keep steps 1–3 in one unbroken context window — don't compact or clear until after /to-issues — so the grilling, PRD, and issues all build on the same thinking. Each /implement then starts fresh, working from the issue.
The limit on this is the smart zone: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before /to-issues, don't push on degraded — /handoff and continue in a fresh thread.
On-ramps
A starting situation that generates work, then merges onto the main flow.
Bugs and requests piling up →
/triage. It moves issues through triage roles and produces agent-ready issues, which/implementlater picks up.Triage is only for issues you didn't create — bug reports, incoming feature requests, anything that arrives raw. Issues that
/to-issuesproduced are already agent-ready, so don't triage them.
Codebase health
Not feature work — upkeep.
/improve-codebase-architecture— run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces deepening opportunities; picking one generates an idea you can take into the main flow at/grill-with-docs.
Crossing sessions
/handoff— when a thread is full or you need to branch off (e.g. into a/prototypesession), this compacts the conversation into a markdown file. You don't continue in place — you open a new session and reference that file to carry the context across. It's the bridge between context windows, in either direction. Use it when you want a fresh session but need the current conversation preserved./compact(built-in) — stay in the same conversation, letting the earlier turns be summarized. Use it at intentional breaks between phases, when you don't mind losing the verbatim history. Don't compact mid-phase — the agent can lose its way./handoffforks;/compactcontinues.
Standalone
Off the main flow entirely.
/grill-me— the same relentless interview as/grill-with-docs, but for when you have no codebase. Stateless: it saves nothing locally, builds noCONTEXT.md. Reach for it to sharpen any plan or design that doesn't live in a repo./teach— learn a concept over multiple sessions, using the current directory as a stateful workspace./writing-great-skills— reference for writing and editing skills well.
Precondition
/setup-matt-pocock-skills — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.
Example
User request:
…
FAQ
What is a 'skill'?
A 'skill' is like a specific application or tool that the AI agent can use to perform a task.
What is a 'flow'?
A 'flow' is a sequence of 'skills' that work together to complete a larger task, like turning an idea into a final product.
What happens if I don't have a codebase?
If you don't have a codebase, the agent can use a tool called '/grill-me' to help you organize your ideas without saving anything locally.
Details
Original description by the author
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Popularity
- GitHub stars
- 48k
- Ranking position
- #2209
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
agent-architecture-audit
Makes your agent check if everything is working correctly. It finds and fixes problems in AI systems, ensuring they perform as expected.
affaan-m/ECC
agent-eval
Helps your agent compare different AI coding tools. It measures which one is faster, cheaper, and more reliable for specific tasks.
affaan-m/ECC
agent-harness-construction
Makes your agent better understand how to perform tasks. It optimizes the tools and instructions the agent uses to increase its chances of success.
affaan-m/ECC