活動潛在客戶開發技能。輸入會議或活動的講者網址，提取講者資訊，根據使用者的理想客戶檔案篩選公司，並深入調查符合條件的講者，生成以人物為主的 HTML 報告。
這是一個專為開發人員和 AI 代理用戶設計的「活動潛在客戶開發」技能。其核心功能是自動化會議或活動的講者研究流程。用戶只需提供一個活動的講者頁面網址，技能就會利用 Browserbase 或 Playwright 等瀏覽器自動化工具擷取所有講者名單。接著，它會根據用戶預先定義的「理想客戶檔案」來過濾這些講者所屬的公司，只保留那些符合 ICP 條件的公司。隨後，針對這些符合條件的講者，技能會進行深入的背景研究，收集他們的公開資料。最終，它會產出一個以人物為核心的 HTML 報告，每個講者卡片都清楚地回答了「為什麼業務人員應該與此人交談？」這個問題，並包含所有公開連結和一鍵複製的私訊開場白。此技能支援 Claude Code、Coder、Cursor 和 Codex 等平台，非常適合用於需要在會議前快速建立目標清單、尋找特定活動的潛在客戶，或評估會議講者是否符合公司目標市場的場景。
npx skills add https://github.com/browserbase/skills/tree/main/skills/event-prospectingInstalled? Explore more 研究與資料分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
活動潛在客戶開發技能。輸入會議或活動的講者網址，提取講者資訊，根據使用者的理想客戶檔案篩選公司，並深入調查符合條件的講者，生成以人物為主的 HTML 報告。每張卡片都會回答「為什麼業務人員應該與此人交談？」並提供所有公開連結和一鍵複製的私訊開場白。請在以下情況使用：(1) 在特定會議尋找潛在客戶，(2) 為活動做準備，(3) 研究活動講者，(4) 從贊助商/參展商頁面建立目標清單，(5) 爬取會議講者並按 ICP 契合度排名。觸發詞：「在 {event} 尋找潛在客戶」、「研究講者」、「開發此會議的客戶」、「stripe sessions 潛在客戶」、「ai engineer summit 潛在客戶」、「活動潛在客戶開發」、「爬取會議講者」、「我應該在該活動見誰」。
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.
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.
Build local constrained-browser agents with a safe_browser tool that owns CDP, enforces a domain allowlist with Fetch interception, and lets a runtime Claude Agent SDK agent complete browsing tasks without raw browser, shell, or CDP access. Use when the user wants an agent to browse or scrape while staying on approved domains, demo blocked off-domain navigation, or generate a safe browser client.
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.