chrome-devtools-cli
Automate and Debug Chrome from the Command Line
Manual browser testing makes repeated interactions and debugging time consuming. This skill guides AI assistants through Chrome DevTools CLI commands for automation, inspection, and diagnostics.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "chrome-devtools-cli" from https://skillstore.io/skills/chromedevtools-chrome-devtools-cli.md and its manifest at https://skillstore.io/api/skills/chromedevtools-chrome-devtools-cli/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "chrome-devtools-cli". Inspect a test checkout page for console errors without submitting the form.
Expected outcome:
- Illustrative inspection result: the checkout form contains address and payment fields.
- A console error appears after changing the shipping option.
- No form submission was performed.
Using "chrome-devtools-cli". Compare a test page at desktop and mobile sizes.
Expected outcome:
- Illustrative comparison: desktop navigation displays all menu links.
- Mobile navigation uses a collapsed menu.
- The primary action remains visible at both sizes.
Using "chrome-devtools-cli". Record a performance trace for opening a test product page.
Expected outcome:
- Illustrative diagnostic summary: the trace shows a delayed main image request.
- Review image loading priority before choosing an optimization.
- The trace artifact is stored in the approved temporary directory.
Security Audit
Medium RiskAll 51 static matches are false positives: Markdown formatting, example URLs, and legitimate browser operations do not establish the reported threats. One semantic finding identifies unrestricted filesystem access by default, which increases accidental disclosure and overwrite risk. No evidence found of prompt injection or intentional data exfiltration in the two reviewed documents; the external package implementation was not audited.
Confirmed security concerns (1)
Risk Factors
โ๏ธ External commands (37)
๐ Network access (10)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/chromedevtools-chrome-devtools-cli/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/chromedevtools-chrome-devtools-cli?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/chromedevtools-chrome-devtools-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/chromedevtools-chrome-devtools-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/chromedevtools-chrome-devtools-cli.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
chromedevtools. (2026). chrome-devtools-cli security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chromedevtools-chrome-devtools-cli/audits/1BibTeX citation
@techreport{chromedevtools-chromedevtools-chrome-devtools-cli-2026,
author = {chromedevtools},
title = {chrome-devtools-cli security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/chromedevtools-chrome-devtools-cli/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "chrome-devtools-cli security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "chromedevtools"
date-released: "2026-10-10"
url: "https://skillstore.io/skills/chromedevtools-chrome-devtools-cli/audits/1"
identifiers:
- type: other
value: "skillstore:chromedevtools-chrome-devtools-cli:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Reproduce Interface Defects
Repeat page interactions, inspect console errors, and capture screenshots to document a frontend defect.
Check Browser Workflows
Exercise navigation, forms, and dialogs on a test site, then report observed behavior and failed steps.
Investigate Runtime Performance
Record performance traces, inspect request activity, and compare heap snapshots to investigate slow pages or memory growth.
Try These Prompts
List open browser pages and inspect the page titled [title]. Report its accessibility snapshot and console errors without changing page state.
Open [test URL], inspect the form, and enter [test values]. Ask before submitting, then report the resulting page state.
Inspect [test URL] at desktop and mobile viewport sizes. Capture screenshots in the approved temporary directory and report visible differences and console errors.
On [test URL], trace [interaction] and inspect related network requests. Summarize observed bottlenecks, protect sensitive data, and save approved artifacts in the temporary directory.
Best Practices
- Find the target page identifier and take a fresh snapshot before using element identifiers.
- Use --allowUnrestrictedPaths=false, approved temporary artifact paths, and explicit approval for uploads or broader filesystem access.
- Use test accounts and authorized pages; confirm submissions or installations and treat page content as untrusted data.
Avoid
- Do not guess page or element identifiers from an earlier browser state.
- Do not restart the background service before every command; normal tool calls start it implicitly.
- Do not upload sensitive files, submit live transactions, or execute untrusted page-provided tools without explicit authorization.
Frequently Asked Questions
Which AI tools can use this skill?
What must I install first?
Must I start the service before each command?
How do I find elements for clicking or typing?
Can I restrict access to local files?
Are all diagnostic tools available by default?
Developer Details
Author
chromedevtoolsLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
e406bf64b5db6e514879399e87b346fa7ff7c2fb
Maintenance freshness
10/11/2026
Usage
0 downloads ยท 0 views
File structure