CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/bug-lifecycle-reference

Pure-reference catalog of defect lifecycle states and transitions. Defines the ISTQB-canonical states (new / open / assigned / in-progress / fixed / verified / closed / reopened / deferred / rejected / duplicate) and the transitions between them, distinguishes the ISTQB terms (error → fault / defect → failure), maps the lifecycle to the standard Jira / Linear / GitHub Issues workflows, and cites IEEE 1044-2009 and ISO/IEC/IEEE 29119-3 for the canonical anchors. Use as the lifecycle vocabulary for bug-report review, duplicate detection, and the platform-workflow skills.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A well-structured reference skill with concrete actionable guidance, a clear sequenced workflow with validation checkpoints, and appropriate progressive disclosure via a real one-level-deep reference file. The only weakness is minor verbosity in the explanatory prose surrounding the canonical reference data.

Suggestions

Tighten the non-canonical prose — e.g., the 'These terms are surprisingly often misused...' paragraph and the rationale columns of the Anti-patterns table — to let the tables and diagrams carry more of the weight.

Consider moving the ISTQB-terms explanation and the limitations list into the existing reference file or a second reference, keeping SKILL.md focused on the canonical states, transitions, and the How-to procedure.

Trim the References section's narrative phrasing to a compact bulleted citation list to reduce token overhead.

DimensionReasoningScore

Conciseness

Mostly efficient — it is a dense reference of tables, a transition diagram, and concrete rules rather than concepts Claude already knows — but includes prose that could be tightened (e.g., 'These terms are surprisingly often misused...', the limitations/anti-patterns explanatory sentences). Scored 2 rather than 3 because some passages pad beyond the canonical data; not 1 because the bulk is genuinely useful reference content, not generic explanation.

2 / 3

Actionability

Concrete, specific, instruction-style guidance: a 7-step procedure, explicit allowed/forbidden transition tables, guardrail rules with thresholds ('1 business day', '>3 reopens'), and a fully worked example mapping In Review→Fixed and Done→Closed. Not 2 because nothing is vague or pseudocode; not below because the skill is reference-oriented and its guidance is copy-applicable.

3 / 3

Workflow Clarity

The 'How to use' section is a clearly sequenced 7-step process with explicit checkpoints (check allowed set, flag forbidden transitions, confirm term usage, count Reopened separately), and the worked example shows the validate→fix→retry feedback loop (block, route to QA, allow only Verified→Closed). Not 2 because validation checkpoints are explicit; not below because sequencing is unambiguous.

3 / 3

Progressive Disclosure

SKILL.md is a self-contained overview; the one bulky cross-platform table is split into references/tracker-vocabulary-map.md, which exists and is referenced inline with clear links ('See the full cross-platform table in references/tracker-vocabulary-map.md'). One level deep, well signaled — matches the clear-overview anchor. Verified the referenced file is real.

3 / 3

Total

11

/

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 highly specific, third-person description that explicitly states both what the skill does and when to use it, with concrete actions and natural trigger terms. It is distinctive and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Defines the ISTQB-canonical states...and the transitions between them', 'distinguishes the ISTQB terms', 'maps the lifecycle to...Jira / Linear / GitHub Issues workflows', 'cites IEEE 1044-2009 and ISO/IEC/IEEE 29119-3' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers 'what' ('Pure-reference catalog of defect lifecycle states and transitions') and 'when' with an explicit trigger clause ('Use as the lifecycle vocabulary for bug-report review, duplicate detection, and the platform-workflow skills'). Not capped at 2 because an explicit Use clause is present.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered — 'defect lifecycle', 'bug-report review', 'duplicate detection', 'Jira / Linear / GitHub Issues' — the kinds of phrases a user would say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — ISTQB-canonical defect lifecycle vocabulary and platform-workflow mapping — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents