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.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « chrome-devtools-cli ». Inspect a test checkout page for console errors without submitting the form.
Résultat attendu:
- 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.
Utilisation de « chrome-devtools-cli ». Compare a test page at desktop and mobile sizes.
Résultat attendu:
- Illustrative comparison: desktop navigation displays all menu links.
- Mobile navigation uses a collapsed menu.
- The primary action remains visible at both sizes.
Utilisation de « chrome-devtools-cli ». Record a performance trace for opening a test product page.
Résultat attendu:
- 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.
Audit de sécurité
Risque moyenAll 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.
Préoccupations de sécurité confirmées (1)
Facteurs de risque
âïž Commandes externes (37)
đ AccĂšs rĂ©seau (10)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/chromedevtools-chrome-devtools-cli/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/chromedevtools-chrome-devtools-cli?utm_source=security_passport_badge)Badge HTML
<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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation APA
chromedevtools. (2026). chrome-devtools-cli security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chromedevtools-chrome-devtools-cli/audits/1Citation BibTeX
@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"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
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.
Essayez ces 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.
Bonnes pratiques
- 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.
Ăviter
- 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.
Foire aux 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?
Détails du développeur
Auteur
chromedevtoolsLicence
MIT
Révision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
Réf
e406bf64b5db6e514879399e87b346fa7ff7c2fb
Récence de maintenance
11/10/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers