Skip to content
TrustedSkillsbeta
Back to all skills

Chrome Devtools

Listed
binjuhor·vlatest·testing

This skill leverages Chrome DevTools to inspect and debug web pages, offering developers a powerful way to troubleshoot issues and optimize performance.

Repository

Install on your platform

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

Installs under a different name. Its SKILL.md names it ck:chrome-devtools, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add binjuhor/shadcn-lar --skill ck: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

binjuhor

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 3 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: pptr.dev, proxy.com, site.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

    site.comundeclaredproxy.comundeclared127.0.0.1localpptr.devundeclarednodejs.orgdocumentation

    What it found

    • .claude/skills/chrome-devtools/SKILL.md:565contacts site.com
      node "$SKILL_DIR/connect-chrome.js" --browser-url http://localhost:9222 --url https://site.com
    • .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"

  • 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 binjuhor/shadcn-lar at b73310ed25.

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

Commit
b73310ed25
Manifest
.claude/skills/chrome-devtools/SKILL.md
Scanned
23 files, 5,839 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

This skill provides access to Chrome DevTools functionality within an AI agent. It allows agents to inspect and debug web pages, analyze network requests, and identify performance bottlenecks directly from within the AI environment. This enables more sophisticated interactions with web applications and automated troubleshooting capabilities.

When to use it

  • Debugging Web Applications: When an AI agent is interacting with a website and encountering errors or unexpected behavior.
  • Analyzing Website Performance: To understand how quickly a webpage loads and identify areas for optimization.
  • Inspecting Network Requests: To examine the data being sent and received during interactions with web servers.
  • Automated Testing: To automate tasks like verifying page content or checking for broken links.

Key capabilities

  • Access to Chrome DevTools features
  • Web page inspection
  • Network request analysis
  • Performance debugging

Example prompts

  • "Inspect the network requests made when I click this button."
  • "What is the loading time of this webpage?"
  • "Show me the console output for this website."

Tips & gotchas

This skill requires a compatible browser environment to be available. The agent's capabilities are limited by what Chrome DevTools can expose and control.