CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/factory-bot-data

Authors Ruby FactoryBot factories with traits, associations, sequences, and the three build strategies (build / create / build_stubbed); integrates with RSpec / Minitest test suites; pairs with Faker for randomized field values. Use when the project is Ruby / Rails and needs structured fixture creation with referential integrity.

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 high-quality, action-dense skill body with executable code, a clear sequenced workflow, and well-structured one-level-deep references. The main weakness is mild verbosity from repeated inline README attributions and a few rationale sentences that could be trimmed.

Suggestions

Drop the repeated '(Per [factory_bot-readme][readme].)' inline citations after the first occurrence — the README is already linked in Overview and listed in References, so the attributions are redundant and add ~6 lines of noise.

Tighten the rationale sentences (e.g., the Faker/FactoryBot split in Overview and the 'instead of ten variant factories...' DRY justification in Traits) to a single clause each, keeping the concrete example but trimming the justification Claude can infer.

DimensionReasoningScore

Conciseness

Largely lean executable code with tight operational commentary, but the repeated '(Per [factory_bot-readme][readme].)' attributions (six occurrences) after the README is already linked, plus a few comparative/rationale sentences (the Faker split, the DRY justification), could be tightened — matching 'mostly efficient but could be tightened' rather than 'every token earns its place'.

2 / 3

Actionability

Fully executable, copy-paste-ready Ruby throughout — factories, sequences, associations, traits, Faker integration, RSpec/Minitest config, and a complete worked example — with no pseudocode gaps.

3 / 3

Workflow Clarity

The 'How to use' section is a clearly sequenced 7-step process ending in 'assert on the returned object' as a verification step; factory authoring is not a destructive/batch operation, so the missing-validation cap does not apply.

3 / 3

Progressive Disclosure

The body is an overview that delegates the build-strategy table and anti-pattern catalog to the verified one-level-deep reference references/strategies-and-anti-patterns.md, with clearly signaled links and well-organized sections.

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, third-person description that names concrete capabilities, surfaces natural trigger terms, and pairs an explicit 'what' with an explicit 'when'. It occupies a clear niche unlikely to conflict with adjacent skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — authoring factories with traits, associations, sequences, and build strategies; integrating RSpec/Minitest; pairing with Faker — matching the 'lists multiple specific concrete actions' anchor rather than the narrower score-2.

3 / 3

Completeness

Explicitly answers what it does (authors/integrates/pairs) and when to use it via the explicit 'Use when the project is Ruby / Rails and needs structured fixture creation' trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a Ruby developer would actually say — 'Ruby', 'Rails', 'FactoryBot', 'factories', 'RSpec', 'Minitest', 'Faker', 'test suites', 'fixture creation' — giving good coverage rather than just some relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Scoped to a specific library (FactoryBot) in a specific language (Ruby/Rails) with a clear niche distinct from sibling skills like faker-data, so it is unlikely to trigger for the wrong skill.

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