pw-trace-analyzer SKILL.md skillA
pw-trace-analyzer from pramoddutta/aitesterblueprint4x is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pramoddutta/aitesterblueprint4x/pw-trace-analyzer@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pramoddutta/aitesterblueprint4x
- Path
chapter_14_MCP_Create_VIBE/testskill-finder-mcp/skills/framework-packs/playwright-pack/pw-trace-analyzer/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 10, 2026
- Size
- 2,998 bytes
- Repository stars
- 14
- License
- none declared
Analyzes a Playwright trace.zip or test failure to pinpoint the root cause. Use when an SDET says "read this trace", "why did this test fail", "analyze the trace.zip", "my CI run failed — what broke", or pastes an error + trace. Reads the timeline, isolates the failing action/assertion, and recommends the fix — a diagnosis the engineer confirms by re-running.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# PW Trace Analyzer You turn a trace or failure into a **root-cause diagnosis the engineer must confirm by re-running** — a trace shows what happened, not always why it's wrong. ## When to use - A `trace.zip` or Playwright error/stack is available and needs interpreting. - A CI failure needs triage before anyone re-runs blindly. - Someone says "read/analyze this trace", "why did this fail". ## Workflow 1. **Open the trace** — recommend `npx playwright show-trace trace.zip` (or the CI report's trace link). If only an error string is provided, work from that and ask for the trace to go deeper. 2. **Locate the failing step** on the timeline — the last action/assertion before the error, its call log, and the DOM snapshot at that moment. 3. **Read the snapshot + call log** to classify the cause: element not found / not visible, strict-mode multi-match, navigation not settled, wrong assertion, backend error (check the Network tab), or a race with an animation/async render. 4. **Correlate signals** — console errors, failed requests, and the before/after snapshots — to separate a test bug from a genuine product bug. …
Read the whole file at its exact version.
How to install
mdr add pramoddutta/aitesterblueprint4x/pw-trace-analyzer@sha256:d63cfcb0ef3dc4aaThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_sw62ylowmi52vh4o)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 10, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2998 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pramoddutta/aitesterblueprint4x · 14 stars · license none declared · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sw62ylowmi52vh4o GET https://markdownregistry.com/api/v1/resolve?ref=pramoddutta/aitesterblueprint4x/pw-trace-analyzer GET https://markdownregistry.com/api/v1/blob/d63cfcb0ef3dc4aa4123de9a908d2901dcae8a77ef7a153597213898554bea58
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from pramoddutta/aitesterblueprint4x
Every file in pramoddutta/aitesterblueprint4x