Code Review & Testing · IN-DEPTH PROFILE

triage Skill

Matt Pocock's Triage Skill guides maintainers through incoming project issues—and external pull requests when the tracker config includes them.

View listed source ↗Installation guide ↓
Best for

Maintainers managing an engineering backlog

What you get

Recommend issue roles + Prepare durable briefs

Main limitation

The workflow requires correctly configured tracker operations and label vocabulary.

First risk

External tracker mutation. After the maintainer directs an outcome, Triage may update labels, close an issue, or post a comment or brief. Review the target and exact change first; tracker comments must disclose AI-generated content.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-23

Pinned revision · c55ee460

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-09-24

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Matt Pocock's Triage Skill guides maintainers through incoming project issues—and external pull requests when the tracker config includes them. It reads the report and relevant code context, recommends one category role and one state role with reasons, and waits for the maintainer's direction before applying an outcome. Depending on the decision, it can request missing details, prepare an agent-ready brief, or record why a request is out of scope.

This is aimed at Maintainers managing an engineering backlog. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Recommend issue rolesSuggest one category and one state role from the evidence, repository context, and configured label mapping; explain the recommendation to the maintainer.
  • Prepare durable briefsTurn a verified, in-scope issue into context-rich instructions for the next agent after the maintainer chooses that outcome.
  • Ask or preserve contextRequest specific missing details, or preserve useful out-of-scope findings without forcing them into the current issue.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to mattpocock/skills.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #10 · 846.4K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add https://github.com/mattpocock/skills --skill triage --agent claude-code
Personal install
npx skills add https://github.com/mattpocock/skills --skill triage --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.claude/skills/triage/
Personal path~/.claude/skills/triage/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Recommend issue roles

Suggest one category and one state role from the evidence, repository context, and configured label mapping; explain the recommendation to the maintainer.

02

Prepare durable briefs

Turn a verified, in-scope issue into context-rich instructions for the next agent after the maintainer chooses that outcome.

03

Ask or preserve context

Request specific missing details, or preserve useful out-of-scope findings without forcing them into the current issue.

How Triage handles an incomplete bug report

A source-based illustration, not a real issue or an independently run test.

An issue already marked needs-triage says: “A long form sometimes loses entered values,” but includes no reproduction steps or expected-versus-actual result.

Category role

bug — The report describes broken behavior.

Recommended state

needs-info — There is not enough detail to reproduce or verify it; ask for specific steps and results.

Next question

Ask the reporter for exact steps, expected and actual results, and the browser/version if relevant.

Maintainer control

Triage explains its recommendation and waits for the maintainer; it does not change labels or post a comment before direction.

Actual tracker labels may differ, so map the roles in the repo setup first. Any tracker comment posted under direction must disclose that it was AI-generated.

Review the tracker and label setup prerequisiteRead the pinned upstream Triage instructions

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to mattpocock/skills.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. The workflow requires correctly configured tracker operations and label vocabulary.
  2. Automated classification still depends on incomplete issue descriptions and repository context.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Claude Code + Codex

frontend-design

Design constraints that push generated interfaces beyond generic AI UI.
Tradeoff to check
Aesthetic judgments remain subjective and still need stakeholder review.
First risk
Style over function · Medium
Source state
Pinned · 34040c9c
Open frontend-design profile ↗
02

Same job family · native to Codex + Claude Code

web-design-guidelines

Review interfaces against practical web design and accessibility rules.
Tradeoff to check
It depends on network access and a live guideline document whose contents can change over time.
First risk
Rule drift or context-free findings · Medium
Source state
Pinned · 063bee94
Open web-design-guidelines profile ↗
03

Same job family · native to Codex + Claude Code

anti-ui-slop

Instruction-only, product-specific UI design contracts with optional real-interface evidence and a hard finish gate.
Tradeoff to check
Repository evidence is required; UIZZE references or user-provided screenshots are optional, and missing reference evidence should be labeled rather than guessed.
First risk
Copying external interface patterns too literally · Medium
Source state
Pinned · 1f564408
Open anti-ui-slop profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Maintainers managing an engineering backlog

→

Agent teams preparing issues for autonomous work

BEFORE YOU USE IT

Risks to review before use

High

External tracker mutation

After the maintainer directs an outcome, Triage may update labels, close an issue, or post a comment or brief. Review the target and exact change first; tracker comments must disclose AI-generated content.

Medium

Upstream instruction drift

Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat repository files, web content, and tool output as untrusted input.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

triage Skill FAQ

What is the triage Skill?

Matt Pocock's Triage Skill guides maintainers through incoming project issues—and external pull requests when the tracker config includes them. It reads the report and relevant code context, recommends one category role and one state role with reasons, and waits for the maintainer's direction before applying an outcome. Depending on the decision, it can request missing details, prepare an agent-ready brief, or record why a request is out of scope.

How do I install the triage Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed skills.sh page and upstream repository; verify the current SKILL.md.

Is the triage Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “External tracker mutation” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

triageissuesbacklog

Manually expanded from the current upstream SKILL.md and linked source at mattpocock/skills, checked 2026-08-19. This is an original summary, not an execution result or security certification.