CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/playwright-fixture-builder

Builds reusable Playwright fixtures via `test.extend` - picks the right scope (test vs worker), wires the `use(value)` setup/teardown split, composes auth (storageState per worker), database (per-test snapshot/restore), and feature-flag fixtures into one custom `test` object the whole suite imports. Outputs the `fixtures.ts` file plus per-fixture review notes (scope rationale, teardown ordering, `workerInfo.workerIndex` for parallel isolation). Use when the suite has copy-pasted `beforeEach` boilerplate that should be a fixture, or when adding auth / db / flag setup that crosses many specs.

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 build-a-skill body: executable code, a concrete scope table, a sequenced workflow with checkpoints, and clean one-level references to real bundle files. The only weakness is mild redundancy in the Overview that re-explains fixture basics Claude already knows.

Suggestions

Trim the Overview's definition of what Playwright fixtures are and the 'This skill is build-an-X' restatement; assume Claude's familiarity and lead with the actionable scope/composition guidance.

Add an explicit verification step in 'How to use' (e.g., run the suite to confirm the composed fixtures resolve and teardown ordering holds) so the workflow closes the loop on the generated code.

Consider moving the verbose Worked example paragraph into a reference or tightening it to the key scope-tradeoff takeaways to reduce token weight.

DimensionReasoningScore

Conciseness

Mostly efficient and actionable, but the Overview paragraph explains what Playwright fixtures are ('replace beforeEach/afterEach boilerplate with composable, lazy-initialized values') and the 'This skill is build-an-X' line restates the description — concepts Claude already knows that could be trimmed.

2 / 3

Actionability

Provides a complete, executable worker-scoped `storageState` auth fixture with real selectors and `workerInfo.workerIndex`, plus a concrete scope-assignment table and 7-step build procedure — copy-paste ready guidance.

3 / 3

Workflow Clarity

The numbered 'How to use' sequence (list → scope → write → compose → confirm teardown order → replace imports → emit review note) is clearly ordered with an explicit checkpoint ('Confirm teardown runs in reverse') and a reviewer sanity-check step, illustrated by the worked example.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with well-signaled one-level-deep references to real bundle files (fixture-recipes.md, composition-and-output.md, anti-patterns-and-limits.md), splitting detailed recipes and limits out of the main file.

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 states concrete capabilities and gives explicit 'Use when' triggers tied to recognizable signals (copy-pasted beforeEach, cross-spec setup). It is specific, complete, and clearly distinct from neighboring skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions via `test.extend`, picks test-vs-worker scope, wires the `use(value)` setup/teardown split, composes auth/db/flag fixtures, and outputs `fixtures.ts` plus review notes — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (builds/composes fixtures, outputs files) and when via the 'Use when the suite has copy-pasted beforeEach boilerplate... or when adding auth / db / flag setup that crosses many specs' clause.

3 / 3

Trigger Term Quality

Covers natural terms a developer would say — 'Playwright fixtures', 'beforeEach boilerplate', 'auth / db / flag setup', 'specs' — alongside the technical API names, giving good coverage of likely phrasings.

3 / 3

Distinctiveness Conflict Risk

A clear niche (Playwright fixture scaffolding via test.extend) with distinct triggers around beforeEach boilerplate and cross-spec auth/db/flag wiring, 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