SKILLEMALL.ai
GitHub ↗ RU Sign in

CF playwright-frontend

For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable `data-testid` attributes (naming convention, uniqueness in lists, stability rules) for React, Vue, Angular, and Svelte. Use when writing or reviewing components, or when an agent needs durable locators.

testdino-hq/playwright-skill Agent Skills author: testdino-hq 3 files body ≈ 504 tokens Open the sourcegithub.com↗ analyzed 2 d ago

For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents.

As a process F 31/100 · No process to follow — References files that are not bundled: ../core/locators.md, ../core/locator-strategy.md

ProcedurePlaywrightSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
F
31/100
No process to follow
References files that are not bundled: ../core/locators.md, ../core/locator-strategy.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../core/locators.md
  • warning missing-ref reference to a missing file: ../core/locator-strategy.md

Process rating: all ten parameters 31/100

Will not run. References files that are not bundled: ../core/locators.md, ../core/locator-strategy.md
  • 0Tools and files. 2 referenced file(s) missing: ../core/locators.md, ../core/locator-strategy.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (playwright-frontend) differs from the folder (frontend)
  • 100Steps. 8 steps
  • 100Execution cost. Instruction body is 504 tokens
  • 100Running it twice. No mutating operations

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
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 426: enough signal without eating the budget
  • +4Structure: 4 headings
  • +3Step-by-step instructions: 8 items
  • +1License stated

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