safe-browser 是做什麼的？
使用 safe_browser 工具建立受限瀏覽器代理，該工具擁有 CDP 控制權、透過 Fetch 攔截執行網域白名單，讓執行中的 Claude Agent SDK 代理能在無原始瀏覽器、Shell 或 CDP 存取權限下完成瀏覽任務。當使用者希望代理能在核准的網域內瀏覽或抓取資料、展示跨域封鎖的導航行為，或產生安全瀏覽器客戶端時使用。
使用 safe_browser 工具建立受限瀏覽器代理，該工具擁有 CDP 控制權、透過 Fetch 攔截執行網域白名單，讓執行中的 Claude Agent SDK 代理能在無原始瀏覽器、Shell 或 CDP 存取權限下完成瀏覽任務。當使用者希望代理能在核准的網域內瀏覽或抓取資料、展示跨域封鎖的導航行為，或產生安全瀏覽器客戶端時使用。
browserbase/safe-browser 是一項專為建立受限制瀏覽器代理而設計的 AI 代理技能。它提供一個名為 safe_browser 的工具，該工具擁有 Chrome DevTools Protocol (CDP) 的完整控制權，並透過 Fetch 請求攔截技術來強制執行嚴格的網域白名單。這意味著 AI 代理只能在您預先核准的網站上進行瀏覽或資料擷取，任何嘗試訪問白名單以外網域的行為都會被自動阻擋並記錄。此技能主要適用於需要以安全、可控的方式執行網頁瀏覽任務的場景，例如自動化測試、受監管的網頁資料收集，或向使用者展示跨域存取被安全封鎖的示範。它與 Claude Agent SDK 完全整合，讓代理能在不直接暴露原始瀏覽器、Shell 或底層 CDP 存取權限的情況下執行任務，從而大幅降低安全風險。對於開發者而言，此技能不僅能產生安全的瀏覽器客戶端，還提供一個隔離的執行環境，確保代理行為可預測、可稽核。
npx skills add https://github.com/browserbase/skills/tree/main/skills/safe-browserInstalled? Explore more 研究與資料分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
使用 safe_browser 工具建立受限瀏覽器代理，該工具擁有 CDP 控制權、透過 Fetch 攔截執行網域白名單，讓執行中的 Claude Agent SDK 代理能在無原始瀏覽器、Shell 或 CDP 存取權限下完成瀏覽任務。當使用者希望代理能在核准的網域內瀏覽或抓取資料、展示跨域封鎖的導航行為，或產生安全瀏覽器客戶端時使用。
This repo contains 10 individual skills — each has its own dedicated page.
Self-improving browser automation via the auto-research loop. Iteratively runs a browsing task, reads the trace, and improves the navigation skill (strategy.md) until it reliably passes. Supports parallel runs across multiple tasks using sub-agents. Use when you want to build or improve browser automation skills for specific website tasks.
Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications. Supports remote Browserbase sessions with Browserbase Identity, Verified browsers, automatic CAPTCHA solving, and residential proxies — ideal for protected websites and JavaScript-heavy pages.
Use the Browserbase CLI (`browse`) for Browserbase Functions and platform API workflows. Use when the user asks to run `browse`, deploy or invoke functions, manage sessions, projects, contexts, or extensions, fetch a page through the Browserbase Fetch API, search the web through the Browserbase Search API, or scaffold starter templates. Prefer the Browser skill for interactive browsing; use the top-level `browse` driver commands (`browse open`, `browse get`, etc.) only when the user explicitly wants the CLI path.
Turn a website's observable HTTP traffic into a best-effort OpenAPI 3.1 spec by analyzing a `browser-trace` capture. Use when the user wants to discover/extract API endpoints from a browser session, build an OpenAPI doc from network traffic, or document a third-party site's XHR/fetch surface for client integration.
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.
Sync cookies from local Chrome to a Browserbase persistent context so the browse CLI can access authenticated sites. Use when the user wants to browse as themselves, sync cookies, or log into sites via Browserbase.
Event prospecting skill. Takes a conference / event speakers URL, extracts the people, filters their companies against the user's ICP, then deep-researches only the speakers at ICP-fit companies. Outputs a person-first HTML report where each card answers "why should the AE talk to this person?" with all public links and a one-click DM opener. Use when the user wants to: (1) find leads at a specific conference, (2) prep for an event, (3) research event speakers, (4) build a target list from a sponsor/exhibitor page, (5) scrape conference speakers and rank by ICP fit. Triggers: "find leads at {event}", "research speakers at", "prospect this conference", "stripe sessions leads", "ai engineer summit prospects", "event prospecting", "scrape conference speakers", "who should I meet at".
Use this skill when the user wants to retrieve a URL without a full browser session: fetch HTML or JSON from static pages, inspect status codes or headers, follow redirects, or get page source for simple scraping. Prefer it over a browser when JavaScript rendering and page interaction are not needed. Supports proxies and redirect control.
Deploy serverless browser automation as cloud functions using Browserbase. Use when the user wants to deploy browser automation to run on a schedule or cron, create a webhook endpoint for browser tasks, run automation in the cloud instead of locally, or asks about Browserbase Functions.
AI-powered adversarial UI testing via the browse CLI. Analyzes git diffs to test only what changed, or explores the full app to find bugs. Tests functional correctness, accessibility, responsive layout, and UX heuristics. Use when the user asks to test UI changes, QA a pull request, audit accessibility, or run exploratory testing. Supports local browser (localhost) and remote Browserbase (deployed sites).
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.