Chrome Devtools
ListedThis skill leverages Chrome DevTools to inspect and debug web pages, offering developers a powerful way to analyze website code and troubleshoot issues.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add samhvw8/dot-claude --skill chrome-devtools -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
samhvw8
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.
Automated safety checks
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.orgundeclaredWhat it found (3 of 8)
- skills/chrome-devtools/references/puppeteer-reference.md:99contacts proxy.com
server: 'http://proxy.com:8080' - skills/chrome-devtools/scripts/install-deps.sh:171contacts pptr.dev
echo " See: https://pptr.dev/troubleshooting" - 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 samhvw8/dot-claude at 28c7616211.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 28c7616211
- Manifest
- skills/chrome-devtools/SKILL.md
- Scanned
- 21 files, 5,493 lines
About this skill
What it does
This skill provides access to Chrome DevTools functionality within an AI agent. It allows for inspecting web pages, debugging JavaScript code, and analyzing network requests directly through prompts. The skill aims to automate tasks typically performed manually using the Chrome browser's developer tools.
When to use it
- Web Scraping: Extract data from websites by programmatically interacting with elements in the DOM.
- Debugging Web Applications: Identify and fix errors in JavaScript code running within a web page.
- Performance Analysis: Analyze network requests and identify bottlenecks affecting website loading times.
- Automated Testing: Simulate user interactions and verify expected behavior on web pages.
Key capabilities
- DOM inspection
- JavaScript debugging
- Network request analysis
Example prompts
- "Inspect the element with ID 'submit-button' and tell me its attributes."
- "Set a breakpoint in this JavaScript code: [code snippet] and show me the values of variables when it’s hit."
- "Analyze the network requests made by this page and identify any requests taking longer than 1 second."
Tips & gotchas
The skill requires a Chrome browser instance to be running and accessible. Ensure that the AI agent has the necessary permissions to interact with the browser's DevTools.