CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-factory-patterns

This skill provides guidance for writing test factories in the Packmind codebase. It should be used when creating or updating factory functions in `**/test/*Factory.ts` files to ensure realistic test data with variety.

Quality

82%

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

81%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 well-structured, concrete, and efficient: executable good/bad code examples, an explicit numbered pattern, and reinforcing guidelines with no padding. The main gaps are the placeholder comments in the primary code example and mild duplication between the code comments and the Guidelines prose.

Suggestions

Make the primary code example copy-paste ready by completing the field list (remove '// ... other fields') and showing 3 fully realistic instances instead of 2 with '// Add 3-5 varied instances'.

Trim the Guidelines sections that restate the code comments verbatim (e.g., instance count and override placement) to reduce redundancy.

Consider moving the bad-example and extended guidelines into a references/ file if the skill grows, keeping SKILL.md as a lean pattern overview.

DimensionReasoningScore

Conciseness

The body is lean and code-driven with a tight Overview and good/bad contrast, but the Guidelines sections partially restate what the code examples and their comments already show ('Include 3-5 varied instances' vs the '// Add 3-5 varied instances' comment), so minor trimming is possible.

4 / 5

Actionability

Concrete, executable TypeScript examples for both good and bad patterns with the exact required imports are provided, but the good example contains placeholder ellipses ('// ... other fields with realistic values') and shows only 2 of the '3-5' instances, so it is not fully copy-paste ready — anchor 4 rather than 5.

4 / 5

Workflow Clarity

This is a simple, single-purpose pattern skill with an unambiguous enumerated workflow (define array of varied instances -> select with `randomIn()` -> spread partial overrides last), reinforced by the Guidelines and a contrasting bad example; it involves no destructive or batch operations, so no validation checkpoints are required.

5 / 5

Progressive Disclosure

A single-file skill with clearly organized sections and no external references — no bundle files exist, so nothing is misfiled. The body is ~95 lines, slightly beyond the 'under 50 lines' case that cleanly merits a 5, and the good/bad example gallery is borderline content that could live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

73%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 solid, well-scoped description with an explicit 'when' clause and concrete trigger file patterns. Its main weaknesses are the generic 'provides guidance for writing' framing of the 'what' and missed trigger synonyms like 'fixtures'.

Suggestions

Replace the generic 'provides guidance for writing test factories' with concrete actions, e.g. 'Creates and updates test factories that generate realistic, varied test data using `randomIn()` and partial overrides.'

Add trigger synonyms users might naturally say, such as 'fixtures', 'test data builders', or 'when writing tests that need realistic entity data'.

DimensionReasoningScore

Specificity

Names the domain ('writing test factories in the Packmind codebase') and one concrete goal ('ensure realistic test data with variety'), but only states 1-2 actions — 'provides guidance for writing' is not a list of several specific actions, so it sits at anchor 3 rather than 4.

3 / 5

Completeness

Both 'what' ('provides guidance for writing test factories... to ensure realistic test data with variety') and an explicit 'when' ('It should be used when creating or updating factory functions...') are present, but the 'what' is phrased generically as 'provides guidance' rather than concrete trigger-style actions, keeping it below anchor 5.

4 / 5

Trigger Term Quality

'creating or updating factory functions in `**/test/*Factory.ts` files' provides good natural trigger phrases a developer would say, but misses common synonyms such as 'fixtures' or 'test data builders' that users might use instead.

4 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to the Packmind codebase and a specific file glob (`**/test/*Factory.ts`), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

cteyton/packmind

Path

skills/skills/test-factory-patterns/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.