CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/test-data-patterns

Pure reference catalog of the cross-language object-construction patterns for test data - Test Data Builder (Pryce/Freeman), Factory (with traits and associations), Object Mother, Fixture composition (per-test / per-describe / shared), Snapshot (defers to `golden-file-conventions` for the operational details), and Production-Data Anonymisation. Distinct from the per-language tool skills (`faker-data` and the `synthetic-data-toolkit` umbrella covering FactoryBot / mimesis / Bogus) which document tool-specific configuration; this catalog is the architecture-tier reference for choosing **which pattern** before reaching for the tool. Use when choosing a test-data construction pattern for a new suite, or auditing an existing suite whose fixtures have drifted into shared mutable state.

64

Quality

80%

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

61%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 a well-structured, actionable reference catalog with concrete examples and clear navigation to sibling skills, but it carries some unnecessary prose padding and lacks any sequenced workflow (acceptable for a pure-reference skill, hence not penalised further).

Suggestions

Trim explanatory framing and the Fowler blockquote in Pattern 4 to one line; the trade-off is already captured in the flavour table.

Add a brief runnable cross-language Factory snippet (or link to synthetic-data-toolkit's factory-bot reference) so the Factory pattern is as executable as the Builder example.

Replace or condense the 'Why this is a pattern, not just a tool concern' paragraph into a single anti-pattern row to save tokens.

DimensionReasoningScore

Conciseness

The catalog is mostly efficient (anti-pattern tables, selection guide), but it pads prose with framing like 'Why this is a pattern, not just a tool concern' and extended blockquotes (Fowler) that restate concepts Claude already knows.

3 / 5

Actionability

It provides an executable TypeScript Builder example and concrete per-pattern 'When to use' criteria plus a pattern-selection guide; the Factory example is Ruby-cited rather than runnable cross-language, leaving minor gaps.

4 / 5

Workflow Clarity

There is no multi-step workflow (the skill declares itself 'pure reference, no execution steps'), and the pattern-selection guide is a decision table rather than a sequenced process; this 260-line catalog exceeds the simple-skill exception, so sequence/checkpoints are absent.

3 / 5

Progressive Disclosure

Content is well-organized into clearly-headed sections with one-level-deep, clearly-signaled hand-offs to sibling skills (e.g. 'Reach for that skill for the operational catalog'); no bundle files exist, and no references are nested beyond one level.

4 / 5

Total

14

/

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 specific, complete, and clearly differentiated, with explicit what/when guidance and concrete hand-off boundaries against sibling skills. Its only weakness is slightly jargon-heavy trigger phrasing that misses some lay synonyms.

DimensionReasoningScore

Specificity

Names six concrete object-construction patterns with their distinguishing attributes (e.g. 'Factory (with traits and associations)', 'Fixture composition (per-test / per-describe / shared)'), giving comprehensive coverage of the domain rather than vague abstraction.

5 / 5

Completeness

It explicitly states what it is ('Pure reference catalog of the cross-language object-construction patterns for test data') and provides an explicit 'Use when choosing a test-data construction pattern for a new suite, or auditing an existing suite...' trigger clause.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'test data', 'fixtures', 'shared mutable state', and 'auditing an existing suite' appear, but coverage leans on catalog jargon ('object-construction patterns') more than the full synonym set a user might say.

4 / 5

Distinctiveness Conflict Risk

It explicitly distinguishes itself from the per-language tool skills ('faker-data', 'synthetic-data-toolkit') and defers snapshot operations to 'golden-file-conventions', carving a clear architecture-tier niche with minimal overlap.

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: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents