CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/traceability-matrix-builder

Use for any question or task about a traceability matrix or requirements test coverage, including building one from a list of requirements and tests, finding requirements without tests, and proof for an auditor. Builds a requirements-to-tests matrix from a test case repository and Jira, Linear or GitHub Issues, with orphaned cases and requirements and a coverage summary.

Quality

88%

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

81%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, actionable workflow with an explicit validation checkpoint and appropriate offloading of bulk templates to a single reference file. Weaknesses are minor: duplicated standards citations, undefined platform-helper functions in code examples, and one dangling reference path.

Suggestions

Merge the standards citations in the Overview and the References section into one place to remove duplication and save tokens.

Define or stub the helper functions (jira_search, list_testrail_cases, get_issue_links) or explicitly state where their implementations come from, so the extraction examples are fully executable.

Fix the dangling references/testrail.md path in the Step 2 code comment — that file is not in this bundle — by pointing to the actual source of the list_cases pattern.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (tables for definitions, anti-patterns, and limitations; minimal prose around code), but the References section repeats standards already cited in the Overview and a few sentences could be tightened. Fits the efficient-with-minor-trimming anchor, not the every-token-earns-its-place anchor.

4 / 5

Actionability

Mostly executable guidance: coverage() and write_matrix_csv() are copy-paste ready and the GitHub Actions YAML is complete, but the extraction functions depend on undefined helpers (jira_search, list_testrail_cases, get_issue_links). Matches the mostly-executable/minor-gaps anchor, not the fully copy-paste anchor.

4 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit validation checkpoint in Step 3 ('Checkpoint first: confirm every case ref resolves... Flag and fix dangling refs first'), healthy-value thresholds in the Definitions table, and anti-pattern guidance for error avoidance — explicit validation for a batch operation. Not 4 because checkpoints are explicit and well-motivated rather than mostly present.

5 / 5

Progressive Disclosure

Good structure: the bulk format templates and worked example are correctly split into the real references/matrix-formats.md, one level deep and clearly linked. However, a code comment cites references/testrail.md, which does not exist in this bundle, a minor organization gap that keeps it below the clear-well-signaled-references anchor.

4 / 5

Total

17

/

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.

A strong description with an explicit trigger clause, concrete actions, named integrations, and clear outputs. The only weakness is slightly incomplete synonym coverage of natural trigger phrases.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (building a matrix from requirements and tests, finding requirements without tests, producing auditor proof) plus named sources (test case repository, Jira, Linear, GitHub Issues) and outputs (orphaned cases, coverage summary), matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

Explicitly answers 'when' via the 'Use for any question or task about a traceability matrix or requirements test coverage...' trigger clause and 'what' via 'Builds a requirements-to-tests matrix from a test case repository and Jira, Linear or GitHub Issues' with outputs; not 4 because the when-clause is explicit with concrete triggers rather than merely present.

5 / 5

Trigger Term Quality

Strong natural phrases ('traceability matrix', 'requirements test coverage', 'requirements without tests', 'proof for an auditor') but a few common synonyms such as 'coverage matrix' or 'map requirements to test cases' are missing, fitting the good-coverage-with-gaps anchor rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The traceability-matrix / requirements-coverage niche with distinct triggers (orphaned cases, auditor proof) is unlikely to fire for unrelated skills; not 4 because there is no meaningful overlap with a closely related skill's triggers.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page