Playwright Documentation Root Cause
Failure-analysis skill for Playwright runs. Use when Codex needs to investigate a failing test, distinguish likely product bugs from test issues, and produce a concise developer-focused root-cause report backed by evidence.
Install
$ agentstack add skill-jovd83-playwright-skill-root-cause ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jovd83-playwright-skill-root-cause) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Playwright Root Cause Analysis
Use this skill when a failure needs explanation, not just rerunning.
Inputs
- failing test output,
- trace artifacts, screenshots, videos, or HTML reports when available,
- related console, network, or application logs,
- recent code or requirement changes if they help explain the failure.
Analysis Workflow
- Identify the failing assertion or stopping point.
- Reconstruct what the app and test were each expecting.
- Classify the issue as likely
product bug,test defect,environment issue, orpossible flake. - Support the classification with concrete evidence.
Output Contract
Provide:
FailureMost likely causeClassificationEvidenceRecommended next actionConfidence
Guardrails
- Do not claim certainty when the evidence is mixed.
- Separate observation from hypothesis.
- If the right answer is "needs reproduction with more data," say that directly.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jovd83
- Source: jovd83/playwright-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.