AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Playwright Documentation Root Cause

skill-jovd83-playwright-skill-root-cause · by jovd83

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.

↗ Repository
— No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-jovd83-playwright-skill-root-cause

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

Are you the author of Playwright Documentation Root Cause? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

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

  1. Identify the failing assertion or stopping point.
  2. Reconstruct what the app and test were each expecting.
  3. Classify the issue as likely product bug, test defect, environment issue, or possible flake.
  4. Support the classification with concrete evidence.

Output Contract

Provide:

  • Failure
  • Most likely cause
  • Classification
  • Evidence
  • Recommended next action
  • Confidence

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.

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.

More in Web & Browser