Playwright CI Triage

    1

    Turn a failed Playwright CI run into grouped investigation notes: retry history, error evidence and trace findings in HTML, Markdown and JSON.

    $5.90

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Playwright CI Triage

    Example session with this skill installed

    Our Playwright CI run failed again. Triage test-results/report.json and tell me which failures are real and which are flaky.

    • Read your context and instructions
    • Compiled the playwright ci triage
    • Generated the document

    Summary

    Scanned the supplied Playwright JSON report: 6 tests, 2 unexpected, 1 flaky, 2 expected, 1 skipped. One real regression, one flaky test, and one expected-failure test that now passes.

    Report outcomes

    OutcomeCount
    expected2
    flaky1
    skipped1
    unexpected2

    Assertion mismatch: demo.spec.cjs > broken checkout total

    Status: unexpected · Attempts: failed, failed

    Error: expect(received).toBe(expected)
    Expected: 29
    Received: 19
    > 4 | test('broken checkout total', async () => { expect(19).toBe(29); });
    

    Failed on both attempts, so this is a consistent failure, not flakiness. Next check: compare the checkout total source with the fixture price.

    Assertion mismatch: demo.spec.cjs > retry recovers

    Status: flaky · Attempts: failed, passed
    Passed only on retry. Next check: open the retry 0 trace and look for a timing or state dependency.

    Needs investigation: demo.spec.cjs > unexpectedly repaired defect

    Status: unexpected · Expected failed · Attempts: passed, passed
    A test marked test.fail() now passes. Either the defect was fixed (remove the annotation) or the test no longer exercises it.

    Next steps

    1. Fix the checkout total regression first; it blocks the release.
    2. Review the flaky test trace before re-running CI.
    3. Update the test.fail() annotation once the fix is confirmed.

    Full reports written to report/triage.html, triage.md and triage.json.

    triage.html

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    What it does

    Give your coding agent a repeatable workflow for failed Playwright runs. A bundled Python scanner (standard library only) reads your Playwright JSON report and produces HTML, Markdown and JSON summaries with error evidence, retry outcomes and attachment references. The skill then guides the agent through source and trace checks before it proposes a fix.

    Included (v0.2.0)

    • SKILL.md workflow
    • Python scanner, no dependencies
    • Retry history and expected-status handling
    • Local trace ZIP analysis: failed actions, slow actions, HTTP error responses
    • Sample reports from an intentionally failing demo suite
    • Self-tests: python tests/selftest.py

    Limits

    Tested with Playwright 1.65.0 trace format 10; other versions are flagged for review. Root cause still needs investigation in your project.

    Requires Python 3.10+. Tested with Playwright 1.65.0 trace format 10. Does not extract ZIP contents. Trace root must contain all referenced attachment paths.

    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 any payment.

    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 4 days ago

    Requires

    Node.js
    Python

    Permissions

    Terminal / Shell
    Browser
    Read Files
    Write Files
    Network Access
    Listed4 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the grouping and analysis of Playwright test failures by processing JSON reports and trace metadata, turning a massive pile of CI logs into structured, actionable summaries and hypotheses.

    The JSON report scanner works with Playwright's built-in JSON reporter. Trace ZIP analysis is tested with Playwright 1.65.0 (trace format 10); other trace versions are flagged for review instead of guessed.

    No, this skill is designed for local or CI-runner processing; it reads local ZIP metadata and JSON files without requiring you to manually upload large trace files to an LLM.

    It keeps Playwright's own outcome (flaky, unexpected, expected) and the full retry history, so a test that passed only on retry is listed separately from one that failed every attempt. Deciding why it was flaky still needs the source and trace review the skill guides you through.

    The SKILL.md workflow, the Python scanner (standard library only), sample HTML/Markdown/JSON reports from a demo suite, setup and compatibility notes, and self-tests.

    While the skill reads all metadata from Trace Format 10 ZIPs, it does not currently decompress or extract internal files like screenshots; it focuses on logs, action timings, and HTTP error responses.

    New in Testing & Debugging