Skip to content
TrustedSkillsbeta
Back to all skills

Playwright Debugging

Checked
ed3dai·vlatest·testing

Helps with Playwright, debugging as part of testing, debugging, and quality assurance workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add ed3dai/ed3d-plugins --skill playwright-debugging -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

ed3dai

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned ed3dai/ed3d-plugins at 0c90f4b5f0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0c90f4b5f0
Manifest
plugins/ed3d-playwright/skills/playwright-debugging/SKILL.md
Scanned
1 file, 434 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides debugging capabilities specifically tailored for Playwright, a popular web browser automation framework. It allows AI agents to inspect and troubleshoot Playwright test runs, identify errors in automated scripts, and analyze browser behavior during execution. This results in faster identification of issues and more reliable testing workflows.

When to use it

  • Debugging failing tests: When your Playwright tests are failing, this skill can help pinpoint the exact cause by providing detailed debugging information.
  • Analyzing unexpected behavior: If a test is passing but not behaving as expected, use this skill to inspect browser state and identify discrepancies.
  • Troubleshooting complex scenarios: For intricate testing workflows involving multiple pages or interactions, this skill simplifies debugging by offering focused insights.
  • Understanding Playwright script errors: When encountering errors within your Playwright scripts, the skill can assist in understanding the root cause and suggesting solutions.

Key capabilities

  • Playwright test run inspection
  • Automated error identification
  • Browser behavior analysis during execution
  • Troubleshooting assistance for Playwright scripts

Example prompts

  • "Debug my failing Playwright test."
  • "Show me the browser state at line 25 of my script."
  • "Why is this element not appearing on the page?"
  • "Analyze the error in my Playwright test and suggest a fix."

Tips & gotchas

This skill requires familiarity with Playwright testing concepts. Ensure your AI agent has access to the relevant Playwright project files for effective debugging.