CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/traceability-matrix-builder

Build-an-X workflow that produces a requirements-to-tests traceability matrix from a TCM case repository + a requirements source (Jira / Linear / GitHub Issues). Walks the author through (1) extracting requirements with stable IDs, (2) extracting cases + their refs, (3) computing coverage (which requirements have at least one test, which tests verify which requirements, orphaned cases / orphaned requirements), (4) emitting a CSV / Markdown / HTML matrix, and (5) producing an executive summary (X% requirement coverage, Y orphans, Z over-tested). Use for test coverage audits, finding requirements-coverage gaps, sprint-end coverage reviews, compliance documentation, and traceability in regulated industries.

79

Quality

99%

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

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, assumes Claude's intelligence, and supplies executable code for every step with a real validation checkpoint and feedback loop before the batch coverage computation. Longer illustrative content is correctly offloaded to a single, well-signaled reference file that genuinely exists.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — no 'what is a TCM' or 'how libraries work' padding — and every section earns its place; the ISO/ISTQB/IEC/DO-178C mentions are actionable cite-by-stable-ID pointers rather than concept explanation, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Provides fully executable, copy-paste-ready Python (get_requirements_jira, get_cases_testrail, get_cases_xray, coverage(), write_matrix_csv) with real field paths plus a concrete GitHub Actions workflow, matching the score-3 'fully executable code/commands; copy-paste ready' anchor rather than the pseudocode at score 2.

3 / 3

Workflow Clarity

A clearly sequenced 6-step process with an explicit validation checkpoint in Step 3 ('Checkpoint first: confirm every case ref resolves to an existing requirement ID before computing coverage') and an error feedback loop ('Flag and fix dangling refs first') for the batch coverage operation, matching the score-3 anchor with explicit validation and recovery.

3 / 3

Progressive Disclosure

SKILL.md is an overview that pushes the longer illustrative material (Markdown/HTML templates, filled executive summary, end-to-end worked example) to a single real one-level-deep bundle file, references/matrix-formats.md, which exists and is linked inline at each relevant step (lines 146, 164, 191), matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

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.

The description is specific, trigger-rich, and fully complete: it names five concrete actions, lists natural use-case triggers, and explicitly covers both what it does and when to use it in third person. It sits in a distinct niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions across five numbered steps — 'extracting requirements with stable IDs', 'extracting cases + their refs', 'computing coverage (which requirements have at least one test...)', 'emitting a CSV / Markdown / HTML matrix', 'producing an executive summary (X% requirement coverage, Y orphans, Z over-tested)' — matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what (the 5-step build-an-X workflow and its outputs) and when via an explicit 'Use for test coverage audits, finding requirements-coverage gaps, sprint-end coverage reviews, compliance documentation, and traceability in regulated industries' trigger clause, matching the score-3 anchor that requires explicit triggers for both.

3 / 3

Trigger Term Quality

Natural phrasings a user would say are well covered: 'test coverage audits', 'finding requirements-coverage gaps', 'sprint-end coverage reviews', 'compliance documentation', 'traceability in regulated industries', plus concrete sources 'Jira / Linear / GitHub Issues'. It is above the score-2 anchor because it goes beyond a single keyword to common variations a user would actually voice.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — building a requirements-to-tests traceability matrix from a TCM repository plus a requirements source — with distinct triggers unlikely to fire for an unrelated skill, matching the score-3 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents