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.

74

Quality

93%

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

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

The body is well-structured with executable code, a validation checkpoint, and clean one-level-deep progressive disclosure via a real reference file. It is a strong, actionable skill body with only minor conciseness tightening possible.

DimensionReasoningScore

Conciseness

Mostly efficient: uses code blocks, tables, and a tight overview without explaining concepts Claude already knows. A few prose passages (e.g. the Overview regulatory citations) could be trimmed slightly but every section earns its place.

4 / 5

Actionability

Fully executable, copy-paste-ready Python (get_requirements_jira, get_cases_testrail, get_cases_xray, coverage(), write_matrix_csv) plus a concrete GitHub Actions YAML covering the common platform cases.

5 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit validation checkpoint in Step 3 ('Checkpoint first: confirm every case ref resolves to an existing requirement ID') and a feedback loop (flag and fix dangling refs before computing coverage), satisfying the batch-operation validation requirement.

5 / 5

Progressive Disclosure

Inline CSV writer and executive-summary skeleton stay in SKILL.md while the longer Markdown/HTML templates, filled summary mockup, and worked example are split into the one-level-deep, clearly-linked references/matrix-formats.md (verified to exist).

5 / 5

Total

19

/

20

Passed

Description

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

The description is concrete, comprehensive, and clearly distinguishes the skill's niche, with explicit 'what' and 'when' guidance. It is among the strongest reference examples, with only minor room to expand natural trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions comprehensively: extracting requirements with stable IDs, extracting cases + refs, computing coverage (orphaned cases/requirements, over-tested), emitting CSV/Markdown/HTML matrix, and producing an executive summary with X%/Y/Z metrics.

5 / 5

Completeness

Explicitly answers both 'what' (produces a traceability matrix via five numbered steps) and 'when' with a concrete 'Use for ...' clause listing several trigger scenarios.

5 / 5

Trigger Term Quality

Strong natural trigger phrases ('test coverage audits', 'finding requirements-coverage gaps', 'sprint-end coverage reviews', 'compliance documentation', 'traceability in regulated industries'), but a few common synonyms (e.g. 'test matrix', 'requirements coverage report') and file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

'requirements-to-tests traceability matrix from a TCM case repository' is a clear niche with distinct triggers; 'traceability matrix' is specific terminology with minimal overlap risk against other skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents