CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/defect-taxonomy-istqb

Pure-reference catalog of defect categorisation taxonomies. Covers the IEEE 1044-2009 anomaly classification (anomaly class, anomaly type, anomaly severity, root cause category), the ISTQB CTAL-TA root-cause taxonomy (requirements / design / implementation / interface / test-data / build-environment), and the Orthogonal Defect Classification (ODC) eight-attribute framework. Maps each taxonomy to a worked example showing how the same defect classifies under each. Use to categorise defects consistently across a team, drive root-cause analysis, and inform process-improvement decisions (where in the SDLC do we leak the most defects?).

76

Quality

95%

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

87%

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

A well-structured, information-dense reference catalog with actionable enum tables and a strong worked example. Its only weakness is workflow clarity: the classification process is not laid out as an explicit sequenced workflow with validation checkpoints.

Suggestions

Add a short numbered 'Classification workflow' (pick taxonomy -> populate enum fields at triage -> refine at closure -> optional metrics) with an explicit verification step so a reviewer can follow it end-to-end.

De-duplicate the closing References section against the inline citations, or convert it to a pure citation list to tighten token efficiency.

Consider an explicit 'Definition of done' / inter-rater check (e.g., the ODC 10-defect calibration mentioned in anti-patterns) as a validation checkpoint in the workflow.

DimensionReasoningScore

Conciseness

Dense, table-driven reference data (exact ODC attribute values, IEEE 1044 class/type enumerations) that Claude does not reliably hold, with mostly load-bearing prose; not below 3 despite minor redundancy between inline citations and the closing References section.

3 / 3

Actionability

Provides concrete, copy-ready guidance for an instruction skill: exact controlled-vocabulary enum tables and a fully worked classification of one defect under all three taxonomies, so a user can populate fields directly.

3 / 3

Workflow Clarity

The anti-patterns table gives corrective guidance, but the classification task is not presented as an explicit numbered sequence with validation checkpoints; not 1 because structure and corrective fixes are present, not 3 because no sequenced validate->fix->retry workflow is shown.

2 / 3

Progressive Disclosure

Well-organized into clear header sections with one-level-deep, clearly signaled sibling references ('Per severity-vs-priority-reference', 'Sibling references:') and no nested indirection; the three taxonomies are kept together to support the comparative worked example.

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 precise, third-person description that names the three taxonomies, lists concrete actions, and gives an explicit 'Use to' trigger clause. It cleanly satisfies specificity, completeness, and distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Covers the IEEE 1044-2009 anomaly classification', 'Maps each taxonomy to a worked example', 'categorise defects', 'drive root-cause analysis', 'inform process-improvement decisions') tied to named taxonomies, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Answers both 'what' (catalog of three named defect taxonomies with a worked example) and 'when' via an explicit 'Use to categorise defects... drive root-cause analysis... inform process-improvement decisions' trigger clause, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Good coverage of natural terms a test/QA lead would say — 'defect categorisation', 'root-cause analysis', 'ODC', 'ISTQB', 'anomaly classification', 'process-improvement' — rather than generic jargon; not below 3 because it spans the domain's common vocabulary.

3 / 3

Distinctiveness Conflict Risk

Highly specific niche anchored to IEEE 1044-2009, ISTQB CTAL-TA, and ODC; these named standards form distinct triggers unlikely to fire for an unrelated skill.

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