Skip to content
TrustedSkillsbeta
Back to all skills

Chrome Devtools

Listed
mrgoonie·vlatest·frontend

This skill provides access to Chrome DevTools for debugging and inspecting web pages, boosting development efficiency and troubleshooting issues effectively.

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 mrgoonie/claudekit-skills --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

mrgoonie

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 4 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: feross.org, pptr.dev, proxy.com, www.patreon.com.

    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.

    Hosts contacted

    proxy.comundeclaredpptr.devundeclarednodejs.orgdocumentationgithub.comsource hostwww.patreon.comundeclaredfeross.orgundeclared

    What it found (3 of 8)

    • .claude/skills/chrome-devtools/references/puppeteer-reference.md:99contacts proxy.com
      server: 'http://proxy.com:8080'
    • .claude/skills/chrome-devtools/scripts/install-deps.sh:171contacts pptr.dev
      echo "   See: https://pptr.dev/troubleshooting"
    • .claude/skills/chrome-devtools/scripts/package-lock.json:257contacts www.patreon.com
      "url": "https://www.patreon.com/feross"

  • 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 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 mrgoonie/claudekit-skills at 80113d86bc.

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

Commit
80113d86bc
Manifest
.claude/skills/chrome-devtools/SKILL.md
Scanned
24 files, 6,130 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 mrgoonie-chrome-devtools skill provides integration with Chrome DevTools, enabling AI agents to interact with and analyze web browser environments. It allows users to inspect web pages, debug JavaScript code, monitor network activity, and manipulate DOM elements directly through an AI interface.

When to use it

  • Debugging complex frontend issues in a web application
  • Analyzing network requests made by a webpage for performance optimization
  • Inspecting and modifying HTML/CSS in real time during development

Key capabilities

  • Access to Chrome DevTools console for executing JavaScript
  • Inspection of DOM elements and their properties
  • Monitoring of network activity and resource loading
  • Debugging tools for JavaScript execution and breakpoints

Example prompts

  • "Inspect the current webpage's DOM structure."
  • "Debug this JavaScript error in the console."
  • "Show me the network requests made by this page."

Tips & gotchas

  • Ensure Chrome DevTools is enabled and accessible within your environment.
  • Some features may require additional permissions or setup to function properly.