BF playwright
Operate Playwright for browser automation end to end: author and debug E2E test suites (robust locators, network interception and mocking, parallel workers, accessibility snapshot checks), wire them into CI, and drive headless browsing and scraping with an extract -> validate -> save loop. Use when writing, running, fixing, or scraping with Playwright, when a Playwright CI failure or JSON report needs triage, or when the bundled pwrun script should analyze a run. Do not use for QA strategy or test framework selection (route to qa-methodology), for frontend component or architecture design (route to frontend-engineering), or for Cloudflare/DDoS-GUARD challenge bypass (use flaresolverr).
Operate Playwright for browser automation end to end: author and debug E2E test suites (robust locators, network interception and mocking, parallel workers…
As a process F 41/100 · Will not run — References files that are not bundled: ../qa-methodology/SKILL.md, ../frontend-engineering/SKILL.md, ../flaresolverr/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securityreferences/06-scraping-and-headless.md:70Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **No credential harvesting, no personal data extraction, no auth-session
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../qa-methodology/SKILL.md - warning
missing-refreference to a missing file: ../frontend-engineering/SKILL.md - warning
missing-refreference to a missing file: ../flaresolverr/SKILL.md - warning
missing-refreference to a missing file: ../react/SKILL.md - warning
missing-refreference to a missing file: scripts/pwrun
Process rating: all ten parameters 41/100
- 0Tools and files. 5 referenced file(s) missing: ../qa-methodology/SKILL.md, ../frontend-engineering/SKILL.md, ../flaresolverr/SKILL.md
- 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
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 48 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2900 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 top-level sections: this looks like several domains in one skill
- low No test case covers injection arriving through data
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
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 694: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.