SKILLEMALL.ai

BD playwright-pro

End-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration. Use when writing E2E tests, fixing flaky tests, or migrating from Cypress/Selenium.

borghei/Claude-Skills Agent Skills author: borghei 26 files · 8 scripts body ≈ 2 563 tokens Open the sourcegithub.com↗ analyzed 32 h ago

End-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration.

As a process D 46/100 · Unfinished process — References files that are not bundled: scripts/*.py, assets/reports/run1-3.json

AnalyzerPlaywrightData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
D
46/100
Unfinished process
References files that are not bundled: scripts/*.py, assets/reports/run1-3.json
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 26. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/*.py
  • warning missing-ref reference to a missing file: assets/reports/run1-3.json

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: scripts/*.py, assets/reports/run1-3.json
  • 0Tools and files. 2 referenced file(s) missing: scripts/*.py, assets/reports/run1-3.json
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 85Steps. 33 steps, 1 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2563 tokens
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 230: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 33 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 6 scripts are documented
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.