cdp
Skill216 starsChanged 17 days agoApache-2.0View on GitHub
Visual verification of a running page through Chrome's DevTools Protocol, capturing screenshots and measuring the rendered DOM. Use when a frontend change can only be confirmed once rendered, for layout, spacing, alignment, overflow, or theme tokens.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- browser-use/browser-harness-jstheir own version, first seen Oct 9, 2026
- huoshen80/ReinaManagertheir own version, first seen Oct 8, 2026
- canddao1-dotcom/flare-agent-skillstheir own version, first seen Feb 13, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- huoshen80/ReinaManager★ 737same name
- browser-use/browser-harness-js★ 500same name
- canddao1-dotcom/flare-agent-skills★ 7same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architectureSkill
- blind-reviewSkill
- calibrateSkill
- dashboardSkill
- engineeringSkill
- ingestSkill
- mcp-catalogSkill
- playgroundSkill
- refineSkill
- simulateSkill
- specializeSkill
- testingSkill
- uiSkill
- writerSkill
- lagune-charterSkill
- lagune-detectSkill
- lagune-hardenSkill
- lagune-planSkill
- lagune-proveSkill
- lagune-repairSkill
- laguneSkill
- lagune-specializeSkill
- lagune-verifySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Put any query params the page supports, a forced theme, a route, or a flag, straight in the URL.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Rendered result verification
This skill owns the verification of what the browser actually renders. It drives a running page through Chrome's built-in DevTools Protocol (CDP) to inspect the DOM, computed styles, and layout, and to capture screenshots. It works against any URL, whatever app or domain is serving it.
Measure, never eyeball
For any spacing or alignment claim, measure the rendered DOM and report the numbers. Read geometry off the elements themselves, for example the box between an element and its container's edges, and state the values you found. A screenshot that looks aligned is not evidence.
When to use it
Reach for it when a change is hard to verify from the source alone: layout, spacing, alignment, overflow, theme tokens, or anything that only shows up once rendered. Skip it for simple, self-evident edits, for example adding a shadow, where the result is obvious from the diff.
Dependencies
The helper needs playwright and tsx. Check each with npm ls <package>, install whatever is missing as a development dependency with the package manager the root lockfile points to, then fetch the pinned browser with npx playwright install chromium.
Running it
The helper ships with this skill, at tools/cdp.ts next to this file. Run it from the project root under npx tsx, pointing at wherever the skill is installed, and write the PNGs to a directory the project ignores in git.
npx tsx <path-to-this-skill>/tools/cdp.ts --out ./temp/shots --shot 'label|<url>'| Flag | Purpose |
--shot 'label|url' | One capture, repeatable. The label names the PNG |
--measure <expr> | Expression evaluated on every shot, its value printed with the shot |
--out <dir> | Where the PNGs are written |
--attach <port> | Reuse a Chromium already exposing a CDP endpoint |
--width, --height, --scale | Viewport and device pixel ratio |
--settle <ms> | Wait after load before measuring and capturing |
Put any query params the page supports, a forced theme, a route, or a flag, straight in the URL. Take the same shot before and after a change when the point is the difference between them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

