Skip to content
TrustedSkillsbeta
Back to all skills

Playwright Trace Debugging

Checked
nathanl·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 nathanl/playwright-trace-debugging --skill playwright-trace-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

nathanl

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 nathanl/playwright-trace-debugging at 81ffaed618.

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

Commit
81ffaed618
Manifest
SKILL.md
Scanned
2 files, 162 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 allows AI agents to record and analyze Playwright trace debugging data. It captures detailed information about browser interactions, network requests, console logs, and more during test execution. This recorded trace can then be replayed and inspected in the Playwright inspector for a deeper understanding of test failures or performance bottlenecks.

When to use it

  • Debugging failing tests: When automated UI tests fail, use this skill to record a trace that provides context beyond simple error messages.
  • Performance analysis: Identify slow network requests or inefficient browser rendering by analyzing the recorded trace data.
  • Reproducing intermittent issues: Capture traces of flaky tests to help pinpoint the root cause of inconsistent behavior.
  • Understanding complex user flows: Record traces of intricate user interactions to visualize and debug the sequence of events.

Key capabilities

  • Record Playwright traces during test execution.
  • Analyze recorded traces in the Playwright inspector.
  • Provides detailed information about browser interactions, network requests, and console logs.

Example prompts

  • "Record a trace while running the 'login' test."
  • "Generate a trace of the checkout process."
  • “Can you record a trace for this failing test?”

Tips & gotchas

  • Requires Playwright to be installed in your environment.
  • Trace files can be large, so ensure sufficient storage space is available.