What problem does it solve? Debugging failed Playwright tests usually requires opening a browser-based trace viewer, which slows down headless and CI workflows. This Skill lets you inspect .zip trace files entirely from the command line to find failing actions, network errors, and console output. ## Core Features & Use Cases - Action Inspection: List all test actions as a tree, filter by title or errors, and drill into individual actions for parameters, logs, and source locations. - Cross-Cutting Views: Review network requests, console messages, and errors across the entire trace with filters for failed requests or error-only output. - DOM Snapshots: Load before/after DOM snapshots for any action, run eval queries against them, and capture screenshots without a live browser. - Use Case: A CI pipeline reports a failed end-to-end test. Open the uploaded trace.zip, list failed actions, inspect the failing action's snapshot, and check for failed API requests to identify the root cause in minutes. ## Quick Start Open the trace.zip file from my failed Playwright test and show me which action failed and what the page looked like at that moment.