Which Matt Pocock Skill Should You Install? Five by Task

Choose this when a repository needs a consistent tracker, label vocabulary, and domain context for related engineering Skills. The workflow inspects the project, confirms those choices, and drafts an Agent Skills block plus reference files. It is a scaffold for this Skill family, not a universal repository standard.

Because it writes configuration and supporting files, ask it to show the paths and diff first. Confirm the tracker is real, preserve existing instructions, and review the result before committing. A generated configuration does not prove that a CLI is authenticated or that a tracker label exists.

Choose triage when a maintainer needs to classify an incoming project issue, identify missing evidence, or prepare a verified issue for an agent. It recommends a category role and a state role with reasons; the maintainer still decides what happens next.

Tracker operations can change labels, close an issue, or post a comment or brief. Configure the actual tracker and label mapping first, inspect the exact target and text, and authorize each write deliberately. Do not treat a suggested classification as a confirmed diagnosis.

Choose TDD when the desired behavior is clear and the project has a usable test runner. The workflow agrees on public test seams, then moves through small red-green-refactor slices instead of writing a large test suite before implementation.

Tests only provide evidence for the behaviors and environments they cover. Check that the chosen seam reflects the user-visible contract, run relevant tests, and review the implementation diff; a passing suite does not prove that the requirement was understood correctly.

Choose this pair before a meaningful product, architecture, or implementation decision when hidden assumptions and decision branches need attention. grill-me is a small launcher; the separate grilling Skill contains the interview workflow. Installing only the launcher may leave the full interview unavailable.

The interview can be disproportionate for a small, reversible choice and cannot supply missing domain expertise or customer research. Set a decision scope and stopping point, answer from evidence you have, and treat recommendations as proposals to evaluate.

Choose handoff when unfinished work must move to another agent environment, workspace, or person. It creates a compact continuation document with decisions, evidence, unknowns, and a next action; it does not automatically move the repository or start another agent.

Open the file before sharing it. Confirm referenced artifacts are accessible, verify progress claims against current evidence, and remove credentials, private issue details, and personal data. A handoff document conveys context, not authority.

Usually not. Start with the current bottleneck, install one role, and check whether the agent discovers it and produces a reviewable artifact. Add another only when it owns a distinct step: repository setup, issue intake, behavior implementation, decision clarification, or session continuity.

This is a task-based shortlist, not a quality ranking or a claim that the five work together automatically. It summarizes pinned upstream revision c55ee460, checked September 23, 2026; upstream instructions may change, and SkillSignal has not independently run or security-audited these packages.

• Pick the task before picking the package.
• Check the current source, target agent, dependencies, and requested permissions.
• Review repository or tracker changes before they are applied.
• Keep only Skills with distinct triggers and outputs you can explain.