mattpocock-skills
claudeMatt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
3 commands + 19 auto-trigger skills + self-evolving agent harness.
Plugin epic from marketplace epicsagas in epicsagas/epic-harness. Commands read from the repo's manifest — 9 days ago.
benchmarkExecutes Bare-vs-Epic A/B benchmarking, Ring 0 Guard 50 challenge, and full golden set evaluation for epic-harness. Orchestrates worker sessions, enforces strict workspace isolation, and synthesizes multi-dimensional comparison reports in TUI. Triggers: /benchmark, 'benchmark', 'a/b test', 'eval har
_criticHarnessX Critic (Tier 2.1) — adversarial review of evolved-skill proposals against trace evidence. Detects reward hacking and manifest/evidence contradictions. Out-of-band LLM counterpart to the in-loop deterministic critic in src/evolve/critic.rs.
_dispatchCore router. Always active. Auto-invokes matching skill before every response. Runs confusion protocol on high-risk ambiguity.
agent-introspectionLoop-breaking self-diagnosis. Use when 3+ consecutive failures occur, circular retries persist, or context overwhelms the session.
auditAudit phase. Parallel review: code quality + security + tests. Semantic dedup of cross-mode findings. Outputs PASS/WARN/FAIL per dimension. Validates spec coverage.
commitConventional Commits 1.0 generator. Stages relevant files, infers type(scope): description, never uses --no-verify.
contextWorking-state snapshot guidance. Restates task/files/decisions in one block so state survives context compaction. Compaction timing is the host's job.
council4-voice parallel deliberation (Architect · Skeptic · Pragmatist · Critic) for architecture, tech selection, or design decisions with no clear answer. Anti-anchoring: each voice gets independent context. Records decision in harness-mem.
debugSystematic root-cause isolation for test failures, runtime errors, or unexpected behavior. Narrow hypothesis → verify → fix.
discoverTrigger: vague/unfocused request or solution-without-problem. Also invoked via /discover command. Reframes goal before acting.
documentDocumentation generator for public APIs, functions, and modules. Use when exports, signatures, or new modules are added or changed.
evalQuality and performance evaluation with baseline comparison. Sub-modes: correctness, performance, quality, regression. Outputs PASS/WARN/FAIL per dimension. Use for pre-ship evaluation or regression checks.
evolveRing 3 evolution engine. Analyzes session observations, generates and improves evolved skills, shows metrics dashboard. Subcommands: status, history, rollback, reset. Use for post-session review and skill improvement.
goGo phase. Reads the approved SPEC file, maps Requirements to tasks (plan), executes via TDD (build), and integrates results verifying all Acceptance Criteria.
orbitState-persisted autonomous pipeline: spec → go → audit → eval → ship → evolve in one command. Auto-detects direct/council/interactive mode. Crash-recoverable via PIPELINE-*.json. Hands-off until PR.
orchestrateTrigger: active multi-agent run. Handles inbox reading, dep resolution, message formatting, handoffs. Also provides status dashboard and intervention control via internal modes.
perfPerformance optimizer for loops, DB queries, rendering, and batch operations. Catches N+1 queries, missing indexes, and unnecessary re-renders.
reflectOn-demand human self-assessment of AI usage quality. Scores 5 dimensions from session data. Not agent performance review.
secureSecurity review checklist with optional engagement scoping. Use when auth, DB, API, infra, or secrets code is touched.
shipShip phase. Runs isolated integration test in a fresh worktree, creates a PR with full spec + audit report in the body, watches CI, and auto-fixes failures.
simplifyCode simplification for high-complexity files. Targets deep nesting, copy-paste patterns, and god functions.
specSpec phase. Converts user requirements into a numbered Requirements + Acceptance Criteria document saved as SPEC-{timestamp}.md. Prompts /team suggestion when 3+ requirements are detected.
tddTest-Driven Development enforcer. Red→Green→Refactor cycle with no production code without a failing test first. Use for new features and bug fixes.
teamOrg-level agent team designer via `epic team` CLI (cross-project, append-merge). Subcommands: list, show, sync, link, unlink, history. Use when setting up agents, designing teams, or /spec yields 3+ requirements.
threat-modelThreat modeling and attack surface analysis. Use when assessing security boundaries, modeling threat actors, or generating threat scenarios.
triageAdversarial validation of vulnerability findings. Use when triaging security findings, validating vulnerabilities, or prioritizing remediation.
verifyPre-merge verification gate. Build, test, and lint must all pass before marking done or shipping.
vuln-scanSystematic vulnerability scan across injection, auth, data exposure, and dependencies — traced by reading code, not grepping for keywords. Use when scanning for vulnerabilities, reviewing security, or validating threat models.
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
6 skills
CMEM Pro for the Claude app - hooks stream tool use to cmem.ai and inject observations into new sessions and agents
3 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
AI memory system — mine projects and conversations into a searchable palace. 47 MCP tools, auto-save hooks, guided setup.
3 skills · 6 commands · 1 MCP server · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.