CtrlK
BlogDocsLog inGet started
Tessl Logo

triage

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

60

Quality

71%

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

77%Weight 40%Scale 1-5

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

A well-structured, action-oriented instruction skill with an exemplary five-step workflow, explicit verification checkpoints, and useful templates. Its critical weakness is that both referenced bundle files (AGENT-BRIEF.md, OUT-OF-SCOPE.md) are missing from the skill directory, breaking navigation and leaving the core agent-brief output format undefined.

Suggestions

Add the referenced bundle files AGENT-BRIEF.md and OUT-OF-SCOPE.md to the skill directory (e.g. under references/) — the skill's primary output (agent briefs) and the out-of-scope knowledge-base workflow currently depend on files that do not exist.

Alternatively, inline a minimal brief-format skeleton in SKILL.md and keep only extended guidance in the reference files, so the skill remains usable if a reference is unavailable.

Consolidate the PR-specific interpretation notes (currently repeated in the intro, the Roles section, and the discovery section) into one clearly marked block to trim redundant tokens.

DimensionReasoningScore

Conciseness

The body is dense and procedural — the verbatim disclaimer, role lists, and needs-info template each earn their tokens, with no explanations of concepts Claude already knows. Not 5 because PR-specific interpretation is repeated in three places ("PR 是带附加代码的 issue", the roles restatement, and the discovery notes) and could be consolidated.

4 / 5

Actionability

Concrete, executable guidance throughout: exact disclaimer text, a copy-paste needs-info template, specific step 4 ("调用两次 Skill 工具,分别指定 grilling 和 domain-modeling"), and example invocation phrases. Not 5 because "查询 issue tracker" and "使用项目 domain glossary 探索 codebase" leave the exact mechanism unspecified.

4 / 5

Workflow Clarity

The five-step sequence (Gather context → Recommend → Verify → Grill → Apply outcome) has explicit validation and checkpoints: "等待指示", step 3 "Verify the claim" with a confirmed/failed/insufficient feedback loop routed to needs-info, "确认你即将做什么…然后执行" before overrides, anomaly-transition flagging, and a resuming-a-previous-session recovery loop. This matches the 5 anchor (explicit validation steps, error-recovery feedback, structured handling of complexity).

5 / 5

Progressive Disclosure

References are clearly signaled and one level deep ([AGENT-BRIEF.md](AGENT-BRIEF.md), [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md), plus inline at point of use), but the referenced files do not exist in the bundle — no references/, scripts/, or assets/ directories are present, so the links are broken and the agent-brief format the skill depends on is unavailable. Not 4 because missing bundle files are more than a minor organization gap; not 2 because the SKILL.md itself is well-structured with clearly marked reference points.

3 / 5

Total

16

/

20

Passed

Description

66%Weight 40%Scale 1-5

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

A specific, well-scoped description with concrete actions and recognizable trigger nouns (issues, PRs, triage, briefs). Its main weakness is the complete absence of any "when to use" guidance, which caps completeness, and limited synonym coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the maintainer asks to triage, label, categorize, or groom issues or external PRs, or wants agent-ready briefs written."

Broaden natural keyword coverage with synonyms such as "tickets", "labels", "pull requests", and "issue tracker" so the description matches how users actually phrase the request.

Mention the key outcome states (needs-info, ready-for-agent, wontfix/closing issues) so the "what" coverage is comprehensive at the top score.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "分类、验证、必要时 grilling,并写出 agent-ready briefs" (categorize, verify, grill, write agent-ready briefs) — covering the core triage loop. It falls short of 5 because notable capabilities (state transitions like needs-info/wontfix, closing issues, labeling) are omitted.

4 / 5

Completeness

The "what" is clear (drive issues/PRs through a triage roles state machine to agent-ready briefs), but there is no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3. Not 2 because the "what" half is concrete, not vague.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "issues", "external PRs", "triage", "agent-ready briefs". Not 5 because common variations and synonyms ("ticket", "label", "pull request" spelled out, "issue tracker") are missing.

4 / 5

Distinctiveness Conflict Risk

The "triage roles 状态机" framing plus "agent-ready briefs" carves a distinct niche unlikely to fire for unrelated skills. Not 5 because bare "issues/PRs" wording could still overlap with general issue-management or PR-review skills.

4 / 5

Total

15

/

20

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.

Validation — 15 / 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.