CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/risk-matrix

Produces the per-feature / per-release risk-matrix artifact itself: a structured intake (feature, category, impact 1-5 by likelihood 1-5, score), mitigations with owners and due dates, supporting both lightweight (impact by likelihood) and heavyweight (FMEA / Cost of Exposure) methods per RBT canon, output as a Markdown / spreadsheet the team reviews each sprint. Use when building the matrix artifact; to facilitate the live risk-storming meeting use risk-storming-facilitator, to calibrate scores across raters use risk-matrix-calibration, and to map the resulting risks onto test coverage use risk-coverage-mapper.

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

100%

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

The body is lean, highly actionable, and well-structured: a ready-to-use matrix template, concrete scoring thresholds, and a worked example drive a clear multi-step workflow with the heavyweight detail appropriately offloaded to a single one-level-deep reference. Little to improve on the content side.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with minimal preamble; aside from a brief RBT blockquote that frames purpose, every section (structure template, heatmap, verdict, categories, test-type map, cadence, storage, anti-patterns) earns its place. Not the verbose 'explains concepts Claude knows' anchor, so it sits at the lean/efficient level.

3 / 3

Actionability

Provides a copy-paste-ready markdown matrix template, concrete scoring rules (impact x likelihood 1-5, block threshold 15+), a category taxonomy, a risk-class-to-test-type table, a cadence table, a storage layout, and a full worked checkout example - fully executable guidance rather than abstract direction.

3 / 3

Workflow Clarity

A clearly sequenced 7-step process with a 'How to use' summary, explicit tiered verdict thresholds (Critical >=15, High 9-14), a cadence table, and a worked example walking every step. This is authoring guidance rather than a destructive/batch operation, so the missing-validate-feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

SKILL.md is an overview and the heavyweight FMEA/Cost-of-Exposure detail is split into a single one-level-deep, clearly-signaled reference (references/heavyweight-risk-scoring.md, verified present) described with its contents. Sections are well-organized, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

12

Passed

Description

85%

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

The description is specific, complete with an explicit 'Use when' trigger, and well-differentiated from sibling skills. Its weakest point is trigger-term quality, which leans on the skill's own jargon ('matrix artifact') rather than the natural phrasings a user would say when they need it.

Suggestions

Broaden the 'Use when' clause with natural user phrasings such as 'risk assessment', 'risk register', or 'prioritize tests by risk' rather than repeating 'matrix artifact'.

Lead with the most common user-recognizable terms before the specialized intake/scoring detail so the trigger surfaces faster.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person ("Produces the per-feature / per-release risk-matrix artifact itself: a structured intake ... mitigations with owners and due dates ... output as a Markdown / spreadsheet"), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what (produces the matrix artifact with intake, mitigations, formats) and when via an explicit "Use when building the matrix artifact" clause, satisfying the 'clearly answers both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

The only trigger is "Use when building the matrix artifact," which repeats the skill's own jargon rather than the natural terms a user would say (e.g., "risk assessment," "risk register," "prioritize tests"); some relevant keywords but missing common variations.

2 / 3

Distinctiveness Conflict Risk

The artifact niche is narrow and the description explicitly distinguishes three siblings ("use risk-storming-facilitator ... risk-matrix-calibration ... risk-coverage-mapper"), giving it a clear niche unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

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