이벤트 발굴 스킬입니다. 컨퍼런스/이벤트 연사 URL을 입력받아 참가자 정보를 추출하고, 사용자의 ICP(이상 고객 프로필)에 맞는 기업의 연사만 심층 조사합니다. 각 카드가 'AE가 왜 이 사람과 대화해야 하는가'에 답하는 HTML 보고서를 모든 공개 링크와 원클릭 DM 발신 기능과 함께 출력합니다.
이 스킬은 컨퍼런스 연사 페이지를 입력으로 받아 참석자를 추출하고, 사용자가 정의한 ICP에 해당하는 기업의 연사만 필터링하여 심층 조사합니다. 그 결과를 HTML 보고서로 생성하는데, 각 참석자 카드는 판매 담당자(AE)가 왜 그 사람과 접촉해야 하는지에 대한 이유를 공개 프로필 링크와 함께 제시하며, 원클릭으로 DM을 보낼 수 있는 버튼도 포함합니다. 주로 '특정 컨퍼런스에서 리드 발굴', '이벤트 사전 준비', '연사 조사', '스폰서/전시업체 페이지에서 타겟 목록 구성', '컨퍼런스 연사 스크래핑 후 ICP 적합도 순위 매기기' 등의 상황에서 사용됩니다. 이 스킬은 브라우저 기반 자동화 및 LLM 기반 추론을 활용하며, 다양한 컨퍼런스 웹사이트(예: Stripe Sessions, AI Engineer Summit)와 호환됩니다.
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 →
이벤트 발굴 스킬입니다. 컨퍼런스/이벤트 연사 URL을 입력받아 참가자 정보를 추출하고, 사용자의 ICP(이상 고객 프로필)에 맞는 기업의 연사만 심층 조사합니다. 각 카드가 'AE가 왜 이 사람과 대화해야 하는가'에 답하는 HTML 보고서를 모든 공개 링크와 원클릭 DM 발신 기능과 함께 출력합니다. 사용자가 다음 작업을 원할 때 사용하세요: (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.