Aller au contenu
TakoAPI
Retour aux skills

chrome-devtools

par podcasting101

Web & Frontend Development
755Téléchargements rapportés par clawskills.sh
0Vues
0 mention J'aimeConnecte-toi pour aimer ce skill
—Pas encore noté
Ta note

Résumé

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

Description

Ce que fait ce 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.

Quand l'utiliser

  • 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

Exemple de workflow

ENTRÉE

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

AGENT
  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

SORTIE

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

Prérequis

  • Google Chrome browser installed

Installation

clawhub install podcasting101/chrome-devtools

Exécute la commande CLI, ou colle l'instruction dans Claude Code, Cursor, Codex ou l'agent de code que tu utilises.

Liens