Saltar al contenido
TakoAPI
Volver a skills

chrome-devtools

por podcasting101

Web & Frontend Development
755Descargas según clawskills.sh
0Vistas
0 me gustaInicia sesión para dar me gusta a esta skill
—Aún sin valoraciones
Tu valoración

Resumen

Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation.

Descripción

Qué hace esta skill

Controls Chrome via the Chrome DevTools Protocol through an MCP server. Supports navigating pages, interacting with DOM elements, running JavaScript, capturing screenshots, and analyzing network requests. The browser starts automatically and maintains a persistent profile across tool calls.

Gives agents direct access to a live browser without requiring a separate Playwright or Selenium setup.

Cuándo usarla

  • Debug a broken form that fails silently in production
  • Scrape data from a JavaScript-rendered page
  • Trace slow network requests to find a bottleneck
  • Automate a multi-step login flow for testing
  • Inspect DOM structure to fix a layout regression

Flujo de trabajo de ejemplo

ENTRADA

User asks: Why is the checkout button not responding on my e-commerce page?

AGENTE
  1. 1

    Call navigate_page to open the checkout page

  2. 2

    Call wait_for to confirm the page is fully loaded

  3. 3

    Call take_snapshot to map the page structure and locate the button uid

  4. 4

    Call evaluate_script to check for JavaScript errors or missing event listeners on the button

  5. 5

    Report the console errors and handler state back to the user

SALIDA

Identifies that a missing script dependency is preventing the click handler from attaching

Requisitos

  • Google Chrome browser installed

Instalación

clawhub install podcasting101/chrome-devtools

Ejecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.

Enlaces