CtrlK
BlogDocsLog inGet started
Tessl Logo

triage

让 issues 和 external PRs 通过一组 triage roles 状态机——分类、验证、必要时 grilling,并写出 agent-ready briefs。

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/engineering/triage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, highly actionable, well-sequenced triage workflow with strong validation checkpoints, held back only by dangling bundle references that promise supporting material not present on disk.

Suggestions

Add the referenced AGENT-BRIEF.md and OUT-OF-SCOPE.md files (or relocate them into a references/ bundle directory) so the inline links resolve.

If those materials are intentionally deferred, note in the Reference docs section that they are populated by /setup-matt-pocock-skills to avoid implying broken links.

DimensionReasoningScore

Conciseness

The body is dense and instruction-focused with no padding or explanation of concepts Claude already knows; every section (roles, states, buckets, the 5-step process, templates) earns its place despite the inherent complexity.

3 / 3

Actionability

It provides concrete, copy-paste-ready guidance — canonical role names, specific discovery buckets, an exact disclaimer string, a needs-info template, and explicit /grilling and /domain-modeling invocations — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

The 5-step triage process is clearly sequenced (Gather, Recommend, Verify, Grill, Apply) with explicit validation checkpoints (step 3 verify-the-claim feedback, step 1 redundancy/prior-rejection checks) and conflict-handling escalation.

3 / 3

Progressive Disclosure

References to AGENT-BRIEF.md and OUT-OF-SCOPE.md are well-signaled and one level deep, but neither file exists in any bundle directory, so the disclosure pointers are broken rather than functional.

2 / 3

Total

11

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive about its triage domain and concrete actions, but omits an explicit 'when to use' trigger clause and relies on somewhat specialized jargon rather than natural user phrasing.

Suggestions

Append an explicit 'Use when...' clause stating when a maintainer should invoke the skill (e.g., 'Use when triaging issues or external PRs, or when maintaining asks what needs attention').

Soften the state-machine jargon with natural trigger terms a user would actually say, such as 'triage issues', 'review PRs', or 'what needs my attention'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — '分类、验证、必要时 grilling' (categorize, verify, grill) and '并写出 agent-ready briefs' (write agent-ready briefs) — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly states what the skill does (triage issues/PRs through a roles state machine, categorize/verify/grill, write briefs) but has no 'Use when...' or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant domain terms ('issues', 'external PRs', 'triage', 'briefs') a maintainer would say, but leans on jargon ('triage roles 状态机') and misses common natural-language variations, fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The niche is clearly defined — issue/external-PR triage via a roles state machine producing agent-ready briefs — making it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
vinvcn/mattpocock-skills-zh-CN
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.