CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

traceability

Use when auditing the link between requirements and tests, before changing or deleting a requirement, when deciding whether a test is allowed to exist, or when asked "what verifies X" / "why does this test exist". Convention-based; the audit script is Babashka, ad-hoc searches use ripgrep.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, opinionated, instruction-only skill whose guidance (conventions, commands, commit formats) is concrete and executable, with clear sequencing and decision branches for the audit workflow. The main defect is that the referenced audit script is not shipped in the bundle, which weakens both actionability and the audit's validation story.

Suggestions

Ship `trace-audit.bb` in the skill's `scripts/` directory — the core audit workflow and its validation checkpoints currently depend on a file the bundle does not contain.

Add an explicit re-audit step after each remediation (e.g., "after writing the missing test or marking the spec superseded, re-run `scripts/trace-audit.bb` until clean") to close the feedback loop.

Trim rationale and anecdote tokens ("instead of archaeology", the 29k-LOC port anecdote) to squeeze out the last bits of token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and teaches only project-specific conventions Claude cannot infer (ID placement rules, commit-subject format, divergence marking), with concrete examples like `search: grep tree content (git_search_files)`. Not a 5 because a few rationale/anecdote tokens could be trimmed ("instead of archaeology", "a 29k-LOC port needed exactly 5 work-item IDs"); not a 3 because nothing explains concepts Claude already knows.

4 / 5

Actionability

Gives concrete, executable guidance: `rg -n 'REQ-SALE-003' specs/ src/ tests/`, the exact comment format `// REQ-SALE-003`, and the spec naming pattern `specs/REQ-<AREA>-<NNN>.md`. Not a 5 because the core instruction "Run `scripts/trace-audit.bb` (copy it to `scripts/` in the project)" depends on a script that is not present in the skill bundle.

4 / 5

Workflow Clarity

"Changing a requirement" is a clear numbered sequence with checkpoints (blast-radius search first, spec+tests in one commit, human-approved separate commit for deletions), and the audit section gives remediation branches for both failure modes plus when-to-run triggers. Not a 5 because there is no explicit re-run-the-audit loop after remediation, and the validation script itself is unshipped.

4 / 5

Progressive Disclosure

A ~65-line body organized into five clear sections with no nested references, appropriate for a single-file skill. Not a 5: the body exceeds the under-50-lines simple-skill threshold and its one external reference (`scripts/trace-audit.bb`) points to a file absent from the bundle.

4 / 5

Total

16

/

20

Passed

Description

87%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: it states a concrete capability, names the tooling, and gives four explicit, natural trigger phrases covering both directions of the audit. The only weakness is slightly incomplete keyword coverage (missing synonyms like "traceability" or "test coverage").

DimensionReasoningScore

Specificity

Lists several concrete situations and actions — "auditing the link between requirements and tests", "before changing or deleting a requirement", "deciding whether a test is allowed to exist" — plus concrete tooling ("the audit script is Babashka, ad-hoc searches use ripgrep"). It is not a 5 because it enumerates triggers rather than comprehensively listing what the skill does (e.g., running the audit, resolving orphan requirements/tests).

4 / 5

Completeness

Explicitly answers 'when' with four concrete trigger phrases ("Use when auditing... before changing or deleting a requirement... when deciding whether a test is allowed to exist, or when asked...") and answers 'what' (bidirectional requirement↔test auditing, convention-based, with named tooling). The 'when' is more explicit than the anchor-4 example where it "could be more explicit", so it is not a 4.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say — "what verifies X", "why does this test exist", "changing or deleting a requirement". Not a 5 because common synonyms such as "traceability", "test coverage", "specs", or "requirements coverage" are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (requirement-test traceability) with distinct triggers like "what verifies X" / "why does this test exist" that no generic skill would claim. Minimal conflict risk with other skills, matching the anchor-5 example's clear-niche pattern.

5 / 5

Total

18

/

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 possibly missing (scripts/trace-audit.bb)

Warning

Total

15

/

16

Passed

Repository

igouss/gitweb-rs

Path

.claude/skills/traceability/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.