Skip to content
TrustedSkillsbeta
Back to all skills

Playwright Debug

Checked
voicetreelab·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 voicetreelab/voicetree --skill playwright-debug -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

voicetreelab

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 voicetreelab/voicetree at 3c598d243e.

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

Commit
3c598d243e
Manifest
.claude/skills/playwright-debug/SKILL.md
Scanned
2 files, 119 lines
Copies in repo
2 — all of them scanned
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

The playwright-debug skill provides debugging capabilities within a Playwright testing environment. It allows users to inspect and interact with browser contexts, trace events, and troubleshoot test failures more effectively. This skill streamlines the process of identifying and resolving issues during automated web testing.

When to use it

  • Debugging failing tests: Use this when your Playwright tests are encountering errors and you need to understand why.
  • Inspecting browser state: When troubleshooting complex interactions, examine the current state of the browser within a test.
  • Analyzing performance bottlenecks: Identify slow operations or unexpected behavior in your web application during testing.
  • Understanding test execution flow: Trace the sequence of events that occur during a test to pinpoint where issues arise.

Key capabilities

  • Browser context inspection
  • Trace event analysis
  • Test failure troubleshooting
  • Playwright integration

Example prompts

  • "Show me the current browser context."
  • "Can you trace the last 5 events?"
  • "What was happening right before this test failed?"
  • "Inspect the DOM of the page at this point in the test."

Tips & gotchas

This skill requires a working Playwright testing environment to function. It's most effective when used alongside existing Playwright tests and configurations.