CtrlK
BlogDocsLog inGet started
Tessl Logo

bug-triage

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

71

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-structured, highly actionable triage workflow with clear sequencing and validation gates. Its main weaknesses are mild redundancy with the description and a large inline report template that leaves no room for progressive disclosure via references.

Suggestions

Move the Step 5 report template into a references file (e.g. references/triage-report-template.md) and link to it, reducing SKILL.md length and improving progressive_disclosure.

Trim or remove the 'When to run' section since the same trigger guidance already appears in the frontmatter description.

Consider collapsing the severity/priority tables into a single compact reference if the definitions are also available in .claude/docs/coding-standards.md, to reduce duplicated inline content.

DimensionReasoningScore

Conciseness

The body is mostly efficient and concrete, but the 'When to run' section duplicates the frontmatter description and the ~60-line report template is inline, so it could be tightened rather than earning the 'every token earns its place' top anchor.

2 / 3

Actionability

Provides concrete globs, exact output paths, severity/priority tables, a full report template, and explicit verdicts — fully executable, copy-paste-ready guidance rather than vague direction.

3 / 3

Workflow Clarity

Six numbered steps with sub-steps, an explicit stop-if-no-bugs validation checkpoint, a write gate requiring approval, and COMPLETE/BLOCKED verdicts give a clear sequence with explicit validation and feedback branches.

3 / 3

Progressive Disclosure

Sections are well-organized, but there are no bundle files and no content split — the large inline report template is content that could live in a one-level reference, matching the 'could be better organized' anchor rather than the well-signaled-references anchor.

2 / 3

Total

10

/

12

Passed

Description

100%

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 strong, specific description that states concrete actions and an explicit run-condition trigger in third person. It clearly conveys both capability and when to invoke it with minimal fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Read all open bugs…re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report' — matching the multiple-specific-actions anchor rather than the partial-coverage anchor below.

3 / 3

Completeness

Explicitly answers both 'what' (the action list) and 'when' ('Run at sprint start or when the bug count grows enough to need re-prioritization'), so the equivalent trigger guidance is present and completeness is not capped at 2.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'bugs', 'priority vs. severity', 'sprint', 'triage report', 're-prioritization' — giving good trigger coverage rather than only a few relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (bug triage with sprint assignment) with distinct triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
Donchitos/Claude-Code-Game-Studios
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.