chrome-devtools

Control and inspect live Chrome instances via the Chrome DevTools Protocol.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Kuass/kiro-gateway-plus --skill chrome-devtools-kuass
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/Kuass/kiro-gateway-plus/tree/main/.opencode/skill/chrome-devtools
Command: npx skills add https://github.com/Kuass/kiro-gateway-plus --skill chrome-devtools-kuass

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a programmatic interface to control and inspect live Chrome browser instances, enabling debugging, performance analysis, and browser automation tasks without manual intervention.

Core Features & Use Cases

  • Browser Control: Navigate pages, open new tabs, and manage existing ones.
  • Element Interaction: Click, fill, and hover over elements identified by unique UIDs.
  • Inspection: Capture screenshots and evaluate JavaScript within the page context.
  • Use Case: Automate the testing of a web application by navigating to specific pages, filling out forms, and verifying the UI state through screenshots.

Quick Start

Use the chrome-devtools skill to navigate to the URL https://example.com.

Frequently Asked Questions about chrome-devtools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Chrome browser debugging and control programmatically?

Automate Chrome browser debugging by using the Chrome DevTools Protocol to control and inspect live instances, navigate pages, manage tabs, and evaluate JavaScript within the page context without manual intervention.

Can I capture screenshots and inspect UI state during web application testing?

Yes, you can capture screenshots and inspect UI state during web application testing by interacting with elements identified by unique UIDs captured from page snapshots, verifying visual output programmatically.

Does browser automation with DevTools require executing JavaScript in the page context?

Yes, browser automation with DevTools requires executing JavaScript in the page context to interact with elements based on UIDs obtained from page snapshots, enabling tasks like form filling and UI state verification.

What is the best way to perform performance analysis on live Chrome instances?

The best way to perform performance analysis on live Chrome instances is programmatically through the Chrome DevTools Protocol, which automates inspection and performance analysis tasks without manual intervention.

Why does element interaction fail when automating web scraping with Chrome DevTools?

Element interaction during web scraping automation fails when elements are not correctly identified by unique UIDs obtained from page snapshots, which are required to accurately click, fill, or hover over target elements.