Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Playwright Suite Skills

    1

    Automation suites often decay into a mess of brittle locators, inconsistent patterns, and trust-destroying "green" results that hide real bugs.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    playwright-suite-skills

    playwright-suite-skills

    Example session with this skill installed

    The checkout tests are failing. Run the suite, triage the failures, and fix anything that is a test-side defect. Refer to .claude/test-profile.md for the run commands.

    • Read your context and instructions
    • Compiled the playwright-suite-

    I have executed the test suite and triaged the results. There were 4 failures in total. 3 were identified as test-side defects due to updated DOM structures in the checkout flow, and 1 appears to be a genuine product bug where the 'Place Order' button remains disabled despite valid input.

    Triage Report

    Test CaseFailure CategoryRoot CauseAction Taken
    checkout-shipping.spec.tsTest DefectLocator button.next is now ambiguous.Updated to getByRole('button', { name: 'Continue to Shipping' }).
    checkout-payment.spec.tsTest DefectInput ID card-num changed to cc-number.Updated Page Object to use new ID.
    checkout-summary.spec.tsProduct BugAssertion failed: Total expected $100, received $0.Reported to team; test remains red to track bug.
    checkout-auth.spec.tsTest DefectSession cookie name changed in dev environment.Updated playwright.config.ts storage state logic.

    Next steps

    • Review the applied locator fixes in checkout-shipping.spec.ts.
    • Verify the product bug in the checkout-summary flow with the backend team.
    • Run npx playwright test --project=chromium to confirm the three test-side fixes now pass.

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

    About this skill

    Automation suites often decay into a mess of brittle locators, inconsistent patterns, and trust-destroying "green" results that hide real bugs. This package provides 13 specialized skills for Playwright environments, designed to maintain suite health without imposing an external house style. It works by first probing your repository's unique conventions and then operating strictly within those bounds.

    What it does

    • Probes conventions by inspecting your Playwright config, directory layout, and locator habits to create a local profile.
    • Audits changesets by reviewing PRs in order of consequence, prioritizing weakened assertions and secrets over style.
    • Hardens locators by replacing positional CSS and XPath with role-based and accessible name selectors.
    • Scaffolds tests across browser, API, and database layers while mirroring existing import paths and patterns.
    • Triages red suites by classifying failures into product bugs versus test defects before suggesting fixes.
    • Manages infrastructure by registering fixtures, writing page objects, and resolving the correct runner commands.

    How it works

    1. Initialize by running the probe-conventions skill to generate a .claude/test-profile.md file.
    2. Execute tasks like write-e2e-test or harden-locators, which automatically read the profile to ensure consistency.
    3. Manage flow using clarify-scope for vague requests or handoff-notes for session persistence.

    Frameworks & tools

    Specifically designed for Playwright suites using TypeScript or JavaScript. Integrates with Claude Code and Cursor to interact with the local filesystem, shell, and git diffs.

    Why this beats prompting it yourself

    Generic prompts often suggest "best practices" that conflict with your team's existing code style, creating friction during PRs. These skills derive their rules from your actual code, ensuring every generated spec or locator looks like your team wrote it.

    Use cases

    • Auditing a pull request to ensure no assertions were accidentally widened or disabled.
    • Converting a brittle suite filled with XPath selectors into one using stable roles.
    • Quickly scaffolding new API client methods and corresponding request specs.
    • Summarizing a complex debugging session into a handoff for another developer.

    Known limitations

    Requires an initial convention probe to function accurately. Does not support non-Playwright runners like Cypress or Selenium. Requires access to the local shell to run tests.

    Requires an initial convention probe to function accurately. Does not support non-Playwright runners. Requires shell access to execute test runs and diffs.

    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 1 month ago

    Requires

    Git

    Permissions

    Browser
    Read Files
    Write Files
    Network Access
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    The suite starts by running a 'probe-conventions' skill that analyzes your Playwright config and existing codebase to create a local profile, ensuring all generated code matches your team's specific style and patterns.

    It is optimized for Playwright environments using TypeScript or JavaScript and is designed to work seamlessly with agentic interfaces like Claude Code and Cursor that have filesystem and shell access.

    Unlike generic prompts, these skills prioritize 'consequence-based' auditing—flagging weakened assertions and security risks over simple style preferences—and use your actual repository as the source of truth for best practices.

    You receive a package of 13 specialized skills covering the entire testing lifecycle, including tools for repository probing, locator hardening, test scaffolding, and automated failure triaging.

    The suite requires an initial convention probe to function effectively and currently only supports Playwright; it is not compatible with other runners like Cypress, Selenium, or Vitest.

    New in Testing & Debugging