Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Playwright Test Failure Debugger

    1

    Diagnose flaky, timed-out, or CI-only Playwright test failures using traces and logs.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Playwright Test Failure Debugger

    Playwright Test Failure Debugger

    Example session with this skill installed

    My test times out on CI but passes locally. Here is the Playwright trace and the test file. Why is the 'Submit' button not becoming actionable in WebKit?

    • Read your context and instructions
    • Compiled the playwright test failure

    Verdict: Material browser-test failure.
    Root Cause: A race condition in hydration causes the 'Submit' button to rerender after Playwright's actionability check but before the click event.
    Remediation: Use a web-first assertion to ensure the button is attached and stable.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Playwright test failures are often misleading. A timeout at the end of a script is usually just a symptom of a race condition, network failure, or state pollution that happened minutes earlier.

    What it does

    • Analyzes Playwright traces, HAR files, and CI logs to reconstruct the exact failure timeline.
    • Identifies the root cause of flaky tests that pass locally but fail in CI.
    • Diagnoses locator fragility, strict-mode violations, and actionability blockers.
    • Evaluates authentication, storage-state issues, and fixture isolation problems.
    • Provides a prioritized remediation plan and a 100-point diagnostic quality score.

    Frameworks & tools

    Playwright, Chromium, Firefox, WebKit, CI environments (GitHub Actions, GitLab CI, Jenkins), and HAR/JSON network logs.

    Why this beats prompting it yourself

    Generic LLMs often suggest "increasing the timeout" or "adding a sleep." This skill follows a 27-step specialized audit workflow to find the earliest point of divergence, preventing you from masking bugs with blind retries.

    Use cases

    • Debugging "passed on retry" flakiness in CI pipelines.
    • Fixing complex navigation races and hydration-related timeouts.
    • Resolving cross-browser inconsistencies between Chromium and WebKit.
    • Audit of storage-state and authentication setup for multi-tenant testing.

    Known limitations

    This tool does not execute tests, open live websites, or modify your source code directly. It requires exported artifacts like traces or logs to perform a high-confidence analysis.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.

    Cannot execute code or access live systems. Requires logs, traces, or code snippets to be provided. Focuses on one failure family at a time.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    Permissions

    Browser
    Listed3 months ago

    What's inside

    Frequently Asked Questions

    This skill is designed to work with all popular AI agents that support file uploads or text pasting, specifically those used for technical troubleshooting and engineering tasks.

    You will need to provide the skill with Playwright trace files (.zip), HAR files, or raw text logs from your CI/CD environment (like GitHub Actions or GitLab CI) for it to perform its analysis.

    Unlike generic AI responses that might just suggest longer timeouts, this skill follows a specialized 27-step audit workflow to find the exact point of divergence and the true root cause of flaky tests.

    No, this skill is a diagnostic tool that analyzes existing artifacts; it does not require access to your repository, nor will it execute any code or open live websites.

    Each purchase includes the full Playwright Test Failure Debugger skill, a guide on how to export the necessary trace artifacts, and access to all future updates and optimizations to the diagnostic workflow.

    New in Testing & Debugging