Built by John Tammi, Koukku.ai.

/call-matt

An unofficial orchestrator skill for Matt Pocock's agent skills.

⚠️ Not affiliated with or endorsed by Matt Pocock. This is a community-built router for his MIT-licensed skill toolkit. All credit for the underlying skills goes to @mattpocockuk — check out Total TypeScript, AI Hero, and mattpocock.com.

One router. Four agents.

Works with

Agent	Invoke	Install dir	Docs
Claude Code	`/call-matt`	`.claude/skills/` or `~/.claude/skills/`	below
Google Antigravity	`/call-matt` workflow or implicit	`.agents/skills/` + `.agents/workflows/`	antigravity/
OpenAI Codex	`$call-matt` or implicit	`~/.codex/skills/`	codex/
Hermes Agent	by name or implicit	`~/.hermes/skills/`	hermes/

Same router, same routing logic, same three-part answer everywhere — only invocation and install differ.

The problem

Matt's toolkit has 14+ excellent skills — /grill-with-docs, /tdd, /to-issues, /diagnose, /caveman and more. They're small and composable by design. But that means you have to know which one fits your current situation.

The fix

/call-matt is a meta-skill that acts as a router and strategic coach. Describe where you are ("I have a vague idea", "my backlog is chaos", "this bug makes no sense", "my context window is melting") and it:

Reads your situation in 1–3 punchy sentences
Picks the playbook — the exact skill (or sequence) to run right now, and why
Gives you the next action — triggers the skill or hands you the command

It knows the healthy lifecycle (grill → PRD → issues → prototype → tdd → improve-architecture) and will tell you when you're skipping a stage.

Install

# 1. Install Matt's actual skills (the things being routed to)
npx skills@latest add mattpocock/skills

# 2. Add this router
npx skills@latest add KoukkuAi/call-matt
# or copy skills/call-matt/ into .claude/skills/ (per project)
# or into ~/.claude/skills/ (available in every project)

# 3. In a new repo, run his setup first
/setup-matt-pocock-skills

Usage

/call-matt I have a rough idea for a CLI tool but no real plan yet

Read: You're at step zero — an idea without resolved decisions. Building now means rebuilding later.
The Playbook: /grill-with-docs. It interviews you until the plan holds up, and writes the decisions into CONTEXT.md so every future session benefits.
Next Action: Run /grill-with-docs and bring your one-paragraph pitch. Expect to get grilled.

What it routes to

Situation	Skill
Vague idea or plan	`/grill-with-docs` · `/grill-me`
Plan → roadmap	`/to-prd` → `/to-issues`
Messy backlog	`/triage`
Design uncertainty	`/prototype`
Building / fixing	`/tdd`
Mystery bug	`/diagnose`
Ball of mud	`/improve-codebase-architecture`
Lost in code	`/zoom-out`
Bloated context	`/handoff` · `/caveman`
New skill needed	`/write-a-skill`

Repository structure

call-matt/
├── src/SKILL.base.md        ← single source of truth
├── scripts/build.py         ← generates all four ports below
├── skills/call-matt/        ← Claude Code
├── antigravity/             ← Google Antigravity (skill + workflow)
├── codex/                   ← OpenAI Codex
└── hermes/                  ← Hermes Agent

Development

Don't edit the generated SKILL.md files directly. Edit src/SKILL.base.md (shared content) or the per-agent config in scripts/build.py, then regenerate:

python3 scripts/build.py

The script validates every generated file (frontmatter, all 18 routed skills present, 12 routing rules, no agent leftovers) and fails loudly if anything is off.

A note on identity

This router deliberately does not impersonate Matt Pocock. It coaches in the spirit of the engineering values his skills document — small steps, fast feedback, no fluff — but it never speaks as him or claims his endorsement.

License

MIT — see LICENSE. The skills it routes to live in mattpocock/skills, also MIT.