SKILLEMALL.ai

BD writing-playwright-tests

Writes Playwright e2e tests for ComfyUI_frontend. Use when creating, modifying, or debugging browser tests. Triggers on: playwright, e2e test, browser test, spec file.

Comfy-Org/ComfyUI_frontend Agent Skills author: Comfy-Org 1 file body ≈ 2 389 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Writes Playwright e2e tests for ComfyUIfrontend.

As a process D 48/100 · Unfinished process — References files that are not bundled: ../../../browser_tests/README.md

GeneratorPlaywrightSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
D
48/100
Unfinished process
References files that are not bundled: ../../../browser_tests/README.md
Tools and files w 18
0
Result and completion w 14
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../../browser_tests/README.md
  • note edit-residue the text marks something as outdated (lines 33): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: ../../../browser_tests/README.md
  • 0Tools and files. 1 referenced file(s) missing: ../../../browser_tests/README.md
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 5 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 85Steps. 19 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2389 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 167: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (10 code blocks)

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