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 per-language data wrappers (`factory-bot-data` Ruby, `faker-data` JS, `mimesis-data` Python, `bogus-data` .NET) 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.

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.

The body is an actionable, well-structured reference catalog with clear selection guidance and good deferral discipline to sibling skills. Its only weakness is moderate verbosity from repeated tool lists and attribution prose that could be tightened.

Suggestions

Trim the embedded Fowler quotes and repeated per-language tool lists to reduce token overhead; the per-language mapping already lives in the description and in the per-language sibling skills.

Consider collapsing the 'Canonical source' attribution prose into a compact References pointer rather than restating it inline under each pattern.

Move the cross-language tooling roster (Ruby/Python/JS/.NET/Java equivalents) into a single consolidated table instead of repeating variants per section.

DimensionReasoningScore

Conciseness

The body is well-organized but carries tightening room: repeated per-language tool lists, embedded Fowler quotes, and 'Canonical source' attribution prose that pad tokens beyond what a lean reference needs, matching 'mostly efficient but could be tightened'.

2 / 3

Actionability

It provides a need-to-pattern selection table, per-pattern 'When to use' guidance, explicit hand-off routing, and complete runnable code examples (TypeScript builder, Ruby FactoryBot), giving copy-paste-ready and decision-ready guidance.

3 / 3

Workflow Clarity

For a single-decision catalog skill the path is unambiguous: selection guide routes the need to a pattern, anti-patterns guard the choice, and hand-off targets sequence where to go next, satisfying the simple-skill allowance for a clear single action.

3 / 3

Progressive Disclosure

All references are one level deep (external URLs and named sibling skills) with no nested drill-downs, the skill explicitly defers operational details to golden-file-conventions and per-language skills, and content is cleanly sectioned, matching the well-organized-sections allowance for skills with no bundle files.

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.

The description is specific, third-person, and answers both what and when with explicit triggers and strong sibling-skill disambiguation. It is dense but every clause carries signal, so it sits at the top of the scale across all four dimensions.

DimensionReasoningScore

Specificity

Names multiple concrete actions and a concrete catalog (Test Data Builder, Factory with traits and associations, Object Mother, Fixture composition, Snapshot, Production-Data Anonymisation) plus 'choosing' and 'auditing' actions, matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

It explicitly states what the skill is (an architecture-tier reference catalog for choosing which pattern) and when to use it via the explicit 'Use when...' clause, satisfying both the what and the when at the score-3 level.

3 / 3

Trigger Term Quality

The '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' clause supplies natural phrases a user would say, with strong coverage of test-data/fixtures vocabulary; not merely jargon.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche ('architecture-tier reference for choosing which pattern before reaching for the tool') and explicitly distinguishes it from named sibling skills (factory-bot-data, faker-data, mimesis-data, bogus-data, golden-file-conventions), making mis-triggering unlikely.

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