browser-trace
Capture a full DevTools-protocol trace of a locally driven browser automation - CDP firehose, screenshots, and DOM dumps - then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress local session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Browser Trace
- When to use
- Setup check
- How it works
- Quickstart
- Remote (Browserbase) sessions - not supported
- Filesystem layout
- Summary shape
Attach a second, read-only CDP client to a browser session that is already being driven by your main automation. The trace records the full DevTools firehose to NDJSON, polls for screenshots and DOM dumps in parallel, and slices everything into a directory tree that bash tools can search. This skill does not drive pages - it only listens. Pair it with agent-browser (the primary local driver, attached via agent-browser connect ), Playwright, Stagehand, or anything else that speaks CDP. The user wants to debug a browser-automation run (failing form, missing element, hung navigation, JS exception). The user has a running automation and wants to attach a trace mid-flight without restarting it. The user wants to split a CDP firehose into network / console / DOM / page buckets. The user wants screenshots + DOM snapshots over time, joined to CDP events by timestamp. If the user just wants to drive the browser, use the agent-browser skill instead. No npm install is needed: the firehose and sampler are raw CDP over Node's built-in WebSocket. Every Chrome DevTools target accepts multiple concurrent CDP clients. Your main automation is one client; this skill adds a second one that only enable
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- vanducng/skills
- Source file
- skills/browser-trace/SKILL.md
- Fixed revision
- c20411b8df8f821988c87689f6aefe142b6f9025
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: vanducng/skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-11T14:02:27.218Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.