Drive a headless Chrome over the Chrome DevTools Protocol (CDP) for browser QA — navigate, click, fill forms, read the DOM/accessibility tree, screenshot, and assert. Use whenever a task requires loading a web page and interacting with it like a user. Chrome is launched by a bash step (recipe below); this skill attaches over CDP — no MCP server, no Puppeteer/Playwright needed to drive.
75
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill examples explicitly place plaintext credentials (e.g., "hunter2") as CLI arguments to the cdp tool and show passing header/env values (e.g., $CDP_HEADERS), which requires the LLM to emit secret values verbatim in generated commands—an exfiltration risk.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The skill’s runtime workflow reads page content from an outsider-controlled URL (via `cdp-client`→`fetch` for CDP targets and `b.goto()`→`Page.navigate`), and then turns the resulting DOM/text/snapshot strings into LLM-visible output (e.g., accessibility tree/text/screenshot metadata) for the agent context.
23e91d0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.