用 Chrome 把网页抓成干净的 Markdown,支持 X、YouTube 字幕,需要登录的页面也能抓。
帮我用 https://github.com/JimLiu/baoyu-skills 安装 baoyu-url-to-markdown skill,然后帮我把这个网页存成 Markdown,图片也下载到本地
让 Claude 操控 Chrome:打开网页、点击填表、截图、抓数据。
帮我用 https://github.com/vercel-labs/agent-browser 安装 agent-browser skill,然后打开我本地的网站把注册流程走一遍并截图
它会按这个仓库把 skill 装好,然后直接开始干活。把后半句换成你自己的任务即可。
/plugin marketplace add vercel-labs/agent-browser /plugin install agent-browser@agent-browser
npm i -g agent-browser,再运行 agent-browser install 下载 Chrome(Linux 缺系统依赖时用 agent-browser install --with-deps)Fast browser automation CLI for AI agents. Chrome/Chromium via CDP with accessibility-tree snapshots and compact @eN element refs.
Install: npm i -g agent-browser && agent-browser install
This file is a discovery stub, not the usage guide. Before running any agent-browser command, load the actual workflow content from the CLI:
agent-browser skills get core # start here — workflows, common patterns, troubleshooting
agent-browser skills get core --full # include full command reference and templates
The CLI serves skill content that always matches the installed version, so instructions never go stale. The content in this stub cannot change between releases, which is why it just points at skills get core.
Load a specialized skill when the task falls outside browser web pages:
agent-browser skills get electron # Electron desktop apps (VS Code, Slack, Discord, Figma, ...)
agent-browser skills get slack # Slack workspace automation
agent-browser skills get dogfood # Exploratory testing / QA / bug hunts
agent-browser skills get derive-client # Record a HAR, derive a standalone API client for a site
agent-browser skills get vercel-sandbox # agent-browser inside Vercel Sandbox microVMs
agent-browser skills get protected-vercel-deployments # Access protected Vercel deployments
agent-browser skills get agentcore # AWS Bedrock AgentCore cloud browsers
Run agent-browser skills list to see everything available on the installed version.
The dashboard runs independently of browser sessions on port 4848 and can also be opened through a proxied or forwarded URL such as https://dashboard.agent-browser.localhost. Agents should stay on the dashboard origin: session tabs, status, and stream traffic are proxied internally, so session ports do not need to be exposed.