ask-matt
GitHub作为工程工作流路由器，根据用户意图匹配并推荐最合适的底层技能（如实现、测试、审查等），以最小化执行路径。
Trigger Scenarios
Install
npx skills add nodetool-ai/nodetool --skill ask-matt -g -y
SKILL.md
Frontmatter
{
"name": "ask-matt",
"description": "Choose an installed repository skill when the user asks which engineering workflow fits their task.",
"disable-model-invocation": true
}
Ask Matt
Recommend the smallest workflow that produces the user's requested result. Use the conversation and repository context before asking for missing information. Carry forward existing decisions and authorization. A sufficient spec needs no preliminary interview or tracker setup.
Choose a starting point
| Requested result | Skill |
|---|---|
| Resolve an unclear plan through discussion | grill-with-docs |
| Build from a spec or tickets | implement |
| Develop behavior test-first | tdd |
| Diagnose a bug or performance regression | diagnosing-bugs |
| Review a diff, branch, or PR | code-review |
| Remove unnecessary code or prose | unslop |
| Evaluate incoming issues or external PRs | triage |
| Write a spec from a discussion | to-spec |
| Split agreed work into dependent tickets | to-tickets |
| Map decisions across a large effort | wayfinder |
| Compare architecture improvements | improve-codebase-architecture |
| Design a module's interface or test boundary | codebase-design |
| Clarify domain terms or record a decision | domain-modeling |
| Answer a design question with runnable code | prototype |
| Investigate primary sources and save findings | research |
| Resolve an active merge or rebase | resolving-merge-conflicts |
| Prepare a procedure requiring human access | wizard |
| Configure tracker and domain-document conventions | setup-matt-pocock-skills |
Choose a NodeTool surface
Product work is routed by the document the user wants, not by the tool they named. Each of these loads the rest of what it needs.
| Requested result | Skill |
|---|---|
| A finished video, still set or campaign | storyboard-core, which picks the job skill |
| A workflow graph | nodetool-workflow-builder |
| A screen someone clicks | nodetool-app-builder |
| A repair on delivered footage | nodetool-video-post |
| JavaScript in the sandbox, or a Code node | nodetool-js-scripting |
| A layered image, mask or overlay | nodetool-sketch |
| A 3D model or scene | nodetool-3d-scene |
| A playable built-in game or asset pack | native-game |
| A new node type | nodetool-custom-node-developer |
| A run that is failing, on any surface | nodetool-troubleshooter |
| An integration over REST, tRPC, WebSocket or MCP | nodetool-api-reference |
| Retrieval over documents | nodetool-rag-indexing |
| A browser automation agent | nodetool-browser-agent |
| Provider keys and model selection | nodetool-model-provider-config |
| A server or worker to deploy | nodetool-deployment |
| Instructions that should persist across sessions | nodetool-skill-author |
Read the selected skill, not every entry. Load supporting references only when the task reaches the operation they describe.
Continue at the requested scope
For a recommendation request, name the skill and explain why in one or two sentences. For an action request, continue with the selected skill. Another phase is useful only when it resolves an actual remaining need.
Read PHASE-BOUNDARIES.md when context management or a handoff is needed. Tracker setup is needed only when a requested tracker operation's destination or conventions cannot be established from existing context.
Version History
- 85ff020 Current 2026-09-28 10:20
- 9b979bc 2026-09-22 23:25
