chrome-devtools SKILL.md skillB
chrome-devtools from firzus/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add firzus/agent-skills/chrome-devtools@git:20261022.1b7748ePins git:20261022.1b7748e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- firzus/agent-skills
- Path
skills/engineering/chrome-devtools/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261022.1b7748e, committed Oct 22, 2026
- First version recorded
- Aug 12, 2026
- Size
- 9,230 bytes
- Repository stars
- 4
- License
- MIT
Debug and automate Google Chrome from the shell with the `chrome-devtools` CLI (npm package `chrome-devtools-mcp`), without configuring an MCP server. Use to inspect a web page's console errors, network requests, cookies and 401/403 failures, performance traces, LCP and Core Web Vitals, Lighthouse scores, accessibility, or memory leaks, and to script page navigation, clicks, form input, emulation, and screenshots. Not for native desktop applications or the host's built-in browser.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Chrome DevTools CLI Drive Chrome through `chrome-devtools`, a client of a background daemon that keeps pages, cookies, and state between commands. Inputs: the target URL or page, the goal (debugging or automation), and the browser mode. Output: findings backed by evidence (console messages, requests, trace insights) and the paths of the files produced. Side effects: a daemon and a browser start; files are written only at the paths you pass. ## 1. Check the CLI 1. Run `chrome-devtools --version`. 2. If the command is missing, report it and propose `npm i -g chrome-devtools-mcp@latest`. Install only with the user's approval. An "Update available" notice is information, not authorization to update. 3. Run `chrome-devtools status`. A running daemon prints its `version=` and `args=`. If a daemon you did not start is running, reuse it when its arguments suit the task. Otherwise tell the user before restarting it, since a restart closes its pages. **Done:** the CLI responds and the daemon state is known. **Blocked:** CLI absent and installation declined; report the blocker and stop. ## 2. Choose the browser mode …
Read the whole file at its exact version.
How to install
mdr add firzus/agent-skills/chrome-devtools@sha256:cb2938e227f8b6d4The line at the top of this page pins the label git:20261022.1b7748e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mj6526r3ijcgxaou)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 12, 2026 and Oct 22, 2026, about one every 36 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261022.1b7748e latest | 2026-10-22 | 1b7748e | 9,230 B | B | view · diff |
| git:20260812.7530717 | 2026-08-12 | 7530717 | 4,325 B | B | view · diff |
| git:20260812.788998f | 2026-08-12 | 788998f | 4,405 B | B | view |
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1:9222)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9230 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
firzus/agent-skills · 4 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mj6526r3ijcgxaou GET https://markdownregistry.com/api/v1/resolve?ref=firzus/agent-skills/chrome-devtools GET https://markdownregistry.com/api/v1/blob/cb2938e227f8b6d4af6346f37fa9c349ff0c31d9a95fccd9714e80c7faf18a34
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from firzus/agent-skills
Every file in firzus/agent-skills