CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/risk-matrix

Use for any question or task about risk-based testing or deciding what to test first when there is no time to test everything: a risk matrix or register with likelihood x impact scores for a release, a risk-storming session, calibrating ratings against real defects, or mapping each risk to the tests and monitors that cover it. Supports light and heavy methods (FMEA, Cost of Exposure).

Quality

93%

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%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, highly actionable skill: the full flow from methodology choice through coverage mapping is sequenced with explicit thresholds, a validation CI gate, and a feedback loop, while detailed material is properly offloaded to six real one-level-deep references. The only weaknesses are minor: a duplicated risk table in the worked example, a quoted Wikipedia definition, and a CI-gate script reference that points at a file missing from the bundle.

Suggestions

Remove the duplicated four-risk table in the worked example (or reference the Step 2 template instead of re-printing it) and trim the quoted Wikipedia definition of risk-based testing to reclaim tokens.

Ship scripts/build-risk-coverage.py referenced by the Step 8e CI gate (the scripts/ directory does not exist in the bundle), or state that the script must be authored locally, so the gate is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with almost no conceptual padding, but two spots could be trimmed: the quoted Wikipedia definition of risk-based testing (a concept Claude already knows) and the worked example re-printing the identical four-risk table from the Step 2 template. These are minor instances of over-explanation, fitting the level 4 anchor rather than the 'could be tightened' level 3 anchor.

4 / 5

Actionability

Guidance is overwhelmingly concrete and executable: a fully populated matrix template, an executable grep command for risk tags, a CI YAML gate, explicit verdict thresholds (score >= 15), and a category-to-test-type mapping. It falls short of copy-paste ready (level 5) because the CI gate invokes scripts/build-risk-coverage.py, which does not exist in the bundle (there is no scripts/ directory).

4 / 5

Workflow Clarity

Eight clearly sequenced step sections, an ordered 'How to use' summary, and an end-to-end worked example, with explicit validation checkpoints: the block-threshold verdict gates, the CI fail-gate (--fail-on-orphan-score 15), orphan-risk detection in Step 8c, and the post-incident cadence update as a feedback loop. The anti-patterns table acts as an error-mode checklist, matching the level 5 anchor.

5 / 5

Progressive Disclosure

The body is a clear overview with a task-to-guide routing table ('Going deeper (referenced guides)') linking six reference files that all exist in the bundle, are one level deep, and cross-link only flatly. Heavyweight FMEA / Cost-of-Exposure content is appropriately split into references/heavyweight-risk-scoring.md, and navigation is easy, matching the level 5 anchor.

5 / 5

Total

18

/

20

Passed

Description

100%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.

An exemplary description: it combines an explicit 'Use for...' trigger clause with concrete scenarios, a comprehensive list of the skill's artifacts and activities, named methodologies, and natural synonyms. It is specific, complete, and distinctive without any padding or over-claiming.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'a risk matrix or register with likelihood x impact scores for a release', 'a risk-storming session', 'calibrating ratings against real defects', 'mapping each risk to the tests and monitors that cover it' — and names both method families (FMEA, Cost of Exposure). No capability from the body is missing, so it exceeds the 'minor gaps' level 4 anchor.

5 / 5

Completeness

Both what and when are explicitly answered: an explicit 'Use for any question or task about...' trigger clause with concrete scenarios, followed by a full enumeration of what the skill produces. The trigger guidance is explicit with concrete phrases, matching the level 5 anchor exactly.

5 / 5

Trigger Term Quality

Natural user phrasings are comprehensively covered: 'risk-based testing', 'risk matrix', 'risk register', 'risk-storming', 'likelihood x impact', 'FMEA', 'deciding what to test first', 'no time to test everything'. Synonyms (matrix/register) are present and no common natural term is missing.

5 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (risk-based test prioritization) with distinct triggers such as 'risk matrix', 'risk-storming', and 'likelihood x impact' that do not collide with adjacent test-strategy or traceability skills. Conflict risk is minimal, fitting the level 5 anchor rather than the 'minor overlap risk' level 4 anchor.

5 / 5

Total

20

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page