CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-evidence-storage

Use when changing test evidence collection, publication, paths, retention, or scratch-directory cleanup.

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/test-evidence-storage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 an exceptionally concrete internal engineering contract: every rule names its owning file, function, or regression test, and it wastes no tokens on concepts Claude already knows. Its weaknesses are structural — monolithic multi-rule bullets instead of a tightened, split-out layout — and the absence of any sequenced workflow, though as a constraints/ownership skill it has less need for one.

Suggestions

Split the dense multi-clause bullets into shorter single-rule statements (or a bullet list per rule) so each invariant is individually scannable.

Move the long regression-test inventories and the test.evidence config-key ownership rules into a separate reference file (e.g., references/evidence-config.md) and link to it from SKILL.md, improving progressive disclosure.

For the few genuinely procedural flows (e.g., publishing evidence to the orphan branch, media attach with token failure), present a short numbered sequence with an explicit validation checkpoint so workflow clarity does not depend on implicit checkpoints.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific invariants, owners, and test names that Claude could not know, with no padding or explanations of generic concepts, matching 'Efficient; minor instances of over-explanation that could be trimmed'. It is not a 5 because many bullets are extremely long run-on sentences packing multiple rules together, which could be tightened into shorter scannable statements.

4 / 5

Actionability

Guidance is fully concrete: exact functions and files (publishRunEvidence in internal/pipeline/steps/evidence_publish.go, paths.ResolveEvidenceRoot, RunManager.pinRunEvidenceDir), exact commands and rules (os.Remove, never RemoveAll; no runtime.GOOS branch; fail-closed upload errors), and named regression tests per behavior. Per the rubric's code-vs-instruction note, the absence of code is not penalized because the instruction-only guidance is directly actionable.

5 / 5

Workflow Clarity

The content presents invariants and ownership rules rather than a sequenced procedure; sections like 'Regressions:' and fail-closed error handling act as implicit checkpoints, but no explicit step sequence or validate-fix-retry loop is given. It is not a 4 because the anchor requires a clear sequence with most checkpoints present, and not a 2 because the mechanisms described (collect, publish, attach, render, cleanup) are each coherently defined with their failure modes.

3 / 5

Progressive Disclosure

There are two clear section headers ("Test Evidence Stays Out of the Code Branch", "no-mistakes Owns Its Own Scratch") and no nested references, but roughly 60 lines of dense monolithic bullets inline config-key ownership rules, rendering-surface rules, and long regression-test lists that could live in separate reference files. It is not a 4 because content that clearly belongs in separate files is inlined and the huge single-paragraph bullets make navigation hard; it is not a 2 because real section structure and consistent per-topic organization do exist.

3 / 5

Total

15

/

20

Passed

Description

51%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 has an explicit, well-targeted 'Use when' trigger clause with natural, distinctive keywords for a narrow internal subsystem, so conflict risk is minimal. However, it entirely omits what the skill does, leaving a reader to infer its capabilities, which caps both completeness and specificity low.

Suggestions

Add a brief 'what' clause before the trigger, e.g., 'Documents the rules for test evidence collection and storage: where evidence is written, how it is published to the evidence branch, and scratch-directory cleanup. Use when changing...'.

State 1-2 concrete capabilities or behaviors the skill governs (e.g., 'evidence stays out of the pushed branch; scratch lives under the app root, never the shared temp dir') so the specificity score reflects the skill's actual scope.

Include a couple of natural synonym triggers such as 'evidence directory' or 'evidence branch' to broaden trigger-term coverage without adding vagueness.

DimensionReasoningScore

Specificity

The description names the domain areas ("test evidence collection, publication, paths, retention, or scratch-directory cleanup") but states no actions the skill performs, matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because that anchor requires 1-2 concrete actions to be explicitly stated, and none are.

2 / 5

Completeness

Only the 'when' is present ("Use when changing...") with no statement of what the skill does, which matches the anchor 'only when is present without what'. It is not a 3 because that anchor requires a clear 'what', which is entirely absent.

2 / 5

Trigger Term Quality

Phrases like "test evidence", "retention", "publication", and "scratch-directory cleanup" are natural terms a developer would use when requesting these changes, giving good keyword coverage. It is not a 5 because common variations and synonyms (e.g., 'evidence directory', 'artifacts', 'logs') are missing, and not a 3 since coverage goes beyond a single relevant keyword.

4 / 5

Distinctiveness Conflict Risk

"Test evidence collection, publication, paths, retention, or scratch-directory cleanup" carves out a clear niche with distinct triggers, making it unlikely to fire for unrelated skills. It is not a 4 because there is no meaningful overlap risk with closely related skills — the trigger set is narrowly scoped to this exact subsystem.

5 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

kunchenguid/no-mistakes

Path

.agents/skills/test-evidence-storage/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.