首页 / Skills / 开发提效 / Chrome DevTools 代理
开发提效

Chrome DevTools 代理

awesome-copilot communityMITSkill 语言: 英文
协议已核对不含脚本依赖外部服务高风险
演示真实运行记录 · claude-sonnet-5-5 · 2026年10月
I need browser debugging and performance analysis on a page using Chrome DevTools. Open file:///private/tmp/claude-501/-Users-huipeizhu-git-aibars-portal/1db8d52d-0133-4843-9915-dc2b4b4fafd0/scratchpad/t_cd/site/index.html . Check the console messages and network requests for errors, record a performance trace with a reload and report the key findings (LCP and anything notable), then fill in the form with the email "[email protected]", choose the "Monthly" plan, submit it and tell me exactly what the page shows afterwards. Only use this page; do not visit any other site.
Skill: chrome-devtools

Here's what I found on the page.

Console errors

  • missing-logo.png failed to load (ERR_FILE_NOT_FOUND). The "Brew & Co logo" image is broken.
  • fetch of api/plans.json was blocked by CORS, because the page is opened from file:// and the origin is null. The page logged "Failed to load plans: Failed to fetch". That failure is most likely a side effect of opening the page from file://, so serving it over http:// should clear it.
  • One DevTools issue: an input has no autocomplete attribute.
  • There was also a plain page loaded log.

Network requests (3 total)

  • index.html returned 200.
  • missing-logo.png failed with ERR_FILE_NOT_FOUND.
  • api/plans.json failed with ERR_FAILED, the CORS block above.

Performance trace (reload)

  • LCP was 194 ms. TTFB was 0.2 ms, and the other ~194 ms was render delay.
  • CLS was 0.00.
  • There is no CrUX field data for this page.
  • The trace surfaced only the LCPBreakdown insight, so I didn't dig into further insights. The long render delay is the one thing worth a closer look.

Form submission
I entered [email protected], selected "Monthly" and clicked Subscribe. The page then showed this text below the form:

Subscribed [email protected] to Monthly

The email appears in uppercase in that message, although I typed it in lowercase. The page may be transforming it with JavaScript or CSS, which is worth checking if that wasn't intended. The form fields kept their values ([email protected], Monthly).

I only used this local page and visited no other sites.

试用方式:我用 Google 的 chrome-devtools-mcp(关闭使用统计和 CrUX 上报,用 `--isolated --headless` 的临时干净浏览器,不碰你的日常 Chrome 和登录状态),让模型只操作我做的一个本地页面。页面里有故意放的问题:缺失的图片、一个会失败的请求、把邮箱转成大写的提交逻辑。模型找到了这些,并正确报告了表单提交后的页面文字。注意:这个 Skill 本身没有安全提示,它能操控真实浏览器。

它做什么

给模型一份使用 chrome-devtools MCP 服务的操作手册。工具分为四组:页面管理(打开、跳转、切换、关闭页面,等待文字出现)、输入(点击、填表、悬停、按键、拖拽、上传文件、处理对话框)、调试(无障碍树快照、截图、控制台消息、在页面里运行 JavaScript、查看网络请求)以及模拟与性能(调整窗口、限制 CPU 或网络、录制并分析性能追踪以查看 Core Web Vitals)。

工作方式

  1. 先快照:用文字快照拿到元素 uid,再按 uid 点击或填写,页面变化后重新快照。
  2. 排查问题:先看控制台错误和失败的网络请求,再用脚本取特定的值。
  3. 性能分析:带刷新开始追踪,再分析 LCP、布局偏移等洞察。

适合什么场景

调试页面、检查性能,以及在你自己的开发站点上自动化浏览器操作。

说明与风险

高风险:它让模型操控一个真实、正在运行的 Chrome。这个浏览器可能登录着你的各种账号,模型可以点击、填写并提交表单、上传文件、在页面里运行任意 JavaScript、读取网络请求(其中可能含有令牌和个人数据),也就是说它可能以你的身份做事或泄露数据。Skill 本身没有任何安全提示。请使用没有登录会话的独立干净浏览器配置文件,避开线上和金融类网站,并盯着它的操作。已试用:我用 Google 的 chrome-devtools-mcp,加 `--isolated --headless` 的干净浏览器,只对一个本地页面跑了一次,模型查控制台和网络、录性能追踪、填表提交,结果和我预先埋的问题一致。须知:这个 MCP 默认会向 Google 发送使用统计、把性能追踪里的网址发给 CrUX 接口,还会检查更新并写入 `~/.cache`;默认浏览器配置目录是持久的,登录状态会留下。可用 `--usageStatistics=false`、`--performanceCrux=false`、`--isolated`、`--allowedUrlPattern`、`--javascriptEvaluation=false` 收紧。