CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/golden-file-conventions

Reference catalog for snapshot / golden file management - naming conventions, directory layout, when to add / update / remove a baseline, sanitization (timestamps, IDs, PII), per-OS / per-runtime variant strategy, and review workflow for snapshot diffs in PRs. Use when designing a snapshot-testing convention or auditing an existing one for drift.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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 reference catalog with clear workflows and navigation; the main weakness is mild verbosity in the terminology/background framing.

Suggestions

Trim the opening terminology note and ISTQB provenance to one line — the interchangeable-use clarification is useful, but the historical background is largely inferable and competes for context.

Tighten the 'When to use' intro ('A reference catalog for how to manage...') since the description already states this, avoiding repetition.

Consider moving the full sanitization-field table into a reference file so the main body can stay lean, given the skill is a pure reference catalog.

DimensionReasoningScore

Conciseness

Mostly efficient reference material with concrete tables and a decision tree, but the terminology note on 'practitioner-emergent terms' and ISTQB provenance plus some framing prose pads content Claude could largely infer.

2 / 3

Actionability

Provides executable specifics — adjacent `__snapshots__/` path layout, Jest `expect.any(Date)`/`expect.any(String)` matcher code, and the `--update-snapshots` command — copy-paste ready guidance.

3 / 3

Workflow Clarity

The 'Update vs. fix decision tree' and numbered 'Review workflow' section sequence the process with explicit checkpoints and error-recovery branches (intended/unintended/ambiguous diffs, severity tiers).

3 / 3

Progressive Disclosure

With no bundle files present, the body is well-organized into clearly-headed sections (naming, layout, sanitization, decision tree, anti-patterns, review) and a single-level References section, with no nested reference chains.

3 / 3

Total

11

/

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.

A strong description that states concrete capabilities, includes explicit 'Use when' triggers, and occupies a clear, low-conflict niche.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'naming conventions, directory layout, when to add / update / remove a baseline, sanitization (timestamps, IDs, PII), per-OS / per-runtime variant strategy, and review workflow' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (the catalog's coverage) and when via the 'Use when designing a snapshot-testing convention or auditing an existing one for drift' trigger clause.

3 / 3

Trigger Term Quality

Covers natural user terms — 'snapshot / golden file management', 'golden file', 'snapshot diffs in PRs', 'snapshot-testing convention' — that a developer would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The snapshot/golden-file niche with its own triggers (designing conventions, auditing drift) is distinct and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents