CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/playwright-extension-fixtures

Author the lower-level Playwright fixture pattern that every Chromium extension test depends on - `chromium.launchPersistentContext` with `--disable-extensions-except=$DIR` + `--load-extension=$DIR`, the `channel: 'chromium'` selection that unlocks headless extension support, the `context.serviceWorkers()` + `waitForEvent('serviceworker')` race-handling pattern, and the `extensionId = serviceWorker.url().split('/')[2]` extraction recipe. This is the launch-and-load layer shared by every extension test, not the assertions run on top of it. Use when authoring or debugging the fixture a Chromium extension test imports - popup, content script, service worker, options page, or side panel.

79

Quality

99%

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

100%

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 tight, executable reference: verbatim fixture code, field-by-field rationale, run modes, troubleshooting, and CI integration, all without padding. It assumes competence and every section delivers actionable or diagnostic value.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — it assumes Claude's competence, never explains what Playwright or service workers are, and every section (rationale table, anti-patterns, limitations) earns its place. No verbosity despite covering a lot of ground.

3 / 3

Actionability

Provides a verbatim, executable fixtures.ts, copy-paste spec-file examples, an MV2 fallback, and a complete GitHub Actions YAML. Commands like 'npx playwright install --with-deps chromium' and 'npx playwright test --headed=false' are copy-paste ready.

3 / 3

Workflow Clarity

Clear sequence across When-to-use, Authoring, Running, and Parsing results, with explicit error-recovery feedback loops (the swEvaluate retry, the extension-load-failure symptom/cause/fix table, the anti-patterns table). Validation guidance for the channel/flag matrix is present.

3 / 3

Progressive Disclosure

No bundle files are present; the single SKILL.md is well-organized into clear sections with the only external pointer being the authoritative Playwright docs reference. Per the rubric's simple-skill scoring note, a self-contained well-structured file scores 3.

3 / 3

Total

12

/

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 highly specific, naming concrete fixture elements and the race-handling pattern with an explicit 'Use when' trigger covering all extension test surfaces. It carves a clear niche distinct from the assertion-level neighbour skill.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'chromium.launchPersistentContext with --disable-extensions-except=$DIR + --load-extension=$DIR', 'channel: chromium selection', 'context.serviceWorkers() + waitForEvent(serviceworker) race-handling pattern', and 'extensionId = serviceWorker.url().split(/[2]) extraction recipe'.

3 / 3

Completeness

Clearly answers both what (the launch-and-load fixture pattern) and when ('Use when authoring or debugging the fixture a Chromium extension test imports - popup, content script, service worker, options page, or side panel').

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say — 'playwright', 'chromium', 'test-fixtures', 'browser-extension', 'popup, content script, service worker, options page, or side panel' — matching the skill's keyword metadata.

3 / 3

Distinctiveness Conflict Risk

Clear niche with distinct triggers and explicit boundary: 'This is the launch-and-load layer shared by every extension test, not the assertions run on top of it', and distinguishes itself from the neighbour skill browser-extension-tests.

3 / 3

Total

12

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents