Agent skill · software engineering · microsoft
playwright-trace
Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.
Why this skill is useful
Provides domain-specific commands for inspecting Playwright trace files that the AI wouldn't reliably generate on its own.
What it needs
Requires npx installed locally. About 3k tokens when loaded. Last updated 2026-08-06. 94,118 stars on the source repository.
What this skill does
Playwright Trace CLI Inspect .zip trace files produced by Playwright tests without opening a browser. Workflow 1. Start with trace open <trace.zip> to extract the trace and see its metadata. 2. Use trace actions to see all actions with their action IDs. 3. Use trace action <action-id> to drill into a specific action — see parameters, logs, source location, and available snapshots. 4. Use trace requests, trace console, or trace errors for cross-cutting views. 5. Use trace snapshot <action-id> to get the DOM snapshot, or run a browser command against it. 6. Use trace close to remove the extracted trace data when done. All commands after open operate on the currently opened trace — no need to pass the trace file again. Opening a new trace replaces the previous one. Commands Open a trace Close a trace Actions Action details The action command displays available snapshot phases (before, action, after) and the exact command to extract them. Requests Request details Console Errors Snapshots The snapshot command loads the DOM snapshot for an action into a headless browser and runs a single browser command against it. Without a browser command, it returns the accessibility snapshot. Only three browser commands are useful on a frozen snapshot: snapshot, eval, and screenshot. Attachments Typical investigation
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills microsoft/playwright-trace