Skip to content
TrustedSkillsbeta
Back to all skills

Chrome Devtools

Checked
chromedevtools·vlatest·frontend·Apache-2.0

This skill leverages Chrome DevTools to inspect and debug web pages directly within your workflow for faster problem-solving and enhanced development.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add chromedevtools/chrome-devtools-mcp --skill chrome-devtools -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

chromedevtools

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned chromedevtools/chrome-devtools-mcp at 47c5b3753d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
47c5b3753d
Manifest
skills/chrome-devtools/SKILL.md
Scanned
1 file, 75 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Chrome DevTools skill provides developers with tools to inspect, debug, and optimize web applications directly within the Chrome browser. It includes features like the Elements panel for DOM inspection, Console for JavaScript debugging, Network for monitoring HTTP requests, and Performance for analyzing page load times.

When to use it

  • Debugging JavaScript errors in a web application during development
  • Analyzing network activity to identify slow-loading resources or API calls
  • Optimizing performance by profiling rendering and memory usage
  • Inspecting and modifying the DOM structure of a webpage in real time

Key capabilities

  • Real-time inspection and modification of HTML and CSS
  • Debugging JavaScript with breakpoints and console logging
  • Monitoring network requests, headers, and response times
  • Performance profiling for CPU, memory, and rendering analysis

Example prompts

  • "Open the Network panel and show me all XHR requests made in the last 30 seconds."
  • "Debug this JavaScript error by stepping through the code line by line."
  • "Analyze the performance of this webpage and suggest optimizations."

Tips & gotchas

  • Ensure you are using a supported version of Chrome for full compatibility.
  • Some advanced features may require enabling experimental flags or extensions.