Skip to content
TrustedSkillsbeta
Back to all skills

Chrome Devtools

Checked
johnlindquist·vlatest·frontend

This skill provides access to Chrome DevTools for debugging and inspecting web pages, offering valuable insights for developers.

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 johnlindquist/claude-workshop-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

johnlindquist

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 johnlindquist/claude-workshop-skills at bc9f16a437.

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

Commit
bc9f16a437
Manifest
skills/chrome-devtools/SKILL.md
Scanned
8 files, 2,920 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

The chrome-devtools skill enables AI agents to inspect, debug, and interact with web pages directly through the Chrome Developer Tools interface. It allows agents to execute JavaScript commands, analyze network traffic, and manipulate the Document Object Model (DOM) in real-time.

When to use it

  • Debugging complex frontend issues by running custom scripts within the browser console.
  • Inspecting live network requests to analyze headers, payloads, and response times.
  • Modifying page elements dynamically to test UI behavior or fix rendering errors.
  • Extracting specific data from a webpage that is difficult to parse via standard scraping methods.

Key capabilities

  • Direct access to the Chrome DevTools Console for command execution.
  • Real-time DOM inspection and modification.
  • Network tab analysis for HTTP request interception.
  • Execution of JavaScript snippets in the context of the current page.

Example prompts

  • "Open the Chrome DevTools console and run document.querySelector('.error').innerText to display any error messages on this page."
  • "Inspect the network tab and list all API requests that returned a 404 status code during the last load."
  • "Modify the background color of the header element to red using the DevTools inspector and confirm the change."

Tips & gotchas

Ensure the target website is loaded in Chrome or Chromium-based browsers for full compatibility. Some dynamic sites may restrict script execution if they detect automation tools, so test interactions carefully to avoid triggering security blocks.