workflows-chrome-devtools

Chrome DevTools Protocol (CDP) debugging is available through the bdg CLI tool, which executes commands like navigation, screenshots, and network tracing directly. The Skill routes CLI requests first for speed and token efficiency, falling back to MCP when CLI is unavailable, letting you choose your execution path based on your workflow needs.

Yes. This Skill orchestrates Chrome DevTools tasks optimized for CI/CD automation, supporting quick CDP access, HAR exports, console monitoring, and DOM queries. CLI-first routing prioritizes speed and token efficiency in automated environments where MCP integration isn't required.

CLI execution via bdg is faster and more token-efficient for single debugging tasks; MCP provides fallback support for complex multi-tool integration scenarios. The Skill automatically selects CLI when available and routes to MCP only when CLI is unavailable, optimizing for your context.

Chrome DevTools Protocol supports HAR exports for network tracing and screenshot capture as core CDP features. This Skill exposes both through CLI-first routing, with troubleshooting guidance and reference examples for navigation, screenshots, and network monitoring workflows.

DOM queries and console monitoring are built into Chrome DevTools Protocol; no additional tools are required. The Skill provides static references and routing logic to execute these tasks via CLI or MCP, with guidance for production debugging pipelines.

CLI execution requires the bdg tool to be available in your environment; complex tool integration scenarios may benefit from MCP fallback instead. The Skill documents this trade-off through its routing pattern and provides troubleshooting guidance for production use cases.