SKILLEMALL.ai

BF playwright-cli

Automate browser interactions, test web pages and work with Playwright tests.

ClawHub Agent Skills author: zengzuo613 v0.1.9 MIT-0 14 files body ≈ 2 760 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 34/100 · Will not run — References files that are not bundled: .playwright-cli/page-2026-02-14T19-22-42-679Z.yml

IntegrationPlaywrightInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
F
34/100
Will not run
References files that are not bundled: .playwright-cli/page-2026-02-14T19-22-42-679Z.yml
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
This is a copy of a skill from another catalog; the rating counts the canonical one: playwright-cli (ClawHub)

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. 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: 14. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: .playwright-cli/page-2026-02-14T19-22-42-679Z.yml

Process rating: all ten parameters 34/100

Will not run. References files that are not bundled: .playwright-cli/page-2026-02-14T19-22-42-679Z.yml
  • 0Tools and files. 1 referenced file(s) missing: .playwright-cli/page-2026-02-14T19-22-42-679Z.yml
  • 0Result and completion. Does not say what the result is
  • 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
  • 40Consistency. Frontmatter name (playwright-cli) differs from the folder (microsoft-playwright-cli)
  • 55Failures and branches. 1 branches
  • 85Steps. 9 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 2760 tokens
  • 100Running it twice. No mutating operations
  • low 13 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)
  • +3Description length 77: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 9 items
  • +4Has examples (25 code blocks)
  • +4Reference files are cited in the instructions (9 of 9)

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

External checks

ClawHub: clean
This is a coherent Playwright browser-automation skill, but it can expose or persist sensitive browser data if used on real accounts or production sites.
LLM: benign (high) · VirusTotal: · 29 May 2026