event-prospecting
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.
Install / Use
npx skills add browserbase/skills --skill event-prospectingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Tags
Our assessment of event-prospecting
event-prospecting scores 95/100 on our quality scale, 82nd of 642 Marketing skills we index (top 13%).
Its SKILL.md is 21 KB long, well organised into 33 sections with 20 code examples: a thorough specification that gives an agent plenty to work with.
With 3,731 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so event-prospecting is actively maintained.
- Our last check on 2026-11-16 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit β read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk β read a skill before letting an agent act on it.
event-prospecting compared with similar skills
All 4 of these similar skills score higher than event-prospecting; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| event-prospecting (this skill)by browserbase | 95 | 3.7k | 2mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install event-prospecting?
- Run
npx skills add browserbase/skills --skill event-prospecting. The install tabs above show the steps for each supported agent. - Which AI agents does event-prospecting work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is event-prospecting safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is event-prospecting still maintained?
- The repository was last updated about 2 months ago, so event-prospecting is actively maintained.
Skill content
View source on GitHubname: event-prospecting
description: |
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".
license: MIT
compatibility: Requires browse CLI (npm install -g browse) and BROWSERBASE_API_KEY env var. The same browse binary covers both API commands and JS-rendered page fallback.
allowed-tools: Bash Agent AskUserQuestion
metadata:
author: browserbase
version: "0.1.0"
Event Prospecting
Take a conference URL β get a ranked list of people the AE should talk to, with a "why reach out" rationale per person.
Required: BROWSERBASE_API_KEY env var and the browse CLI installed (npm install -g browse). Use browse cloud ... for API calls and browse open / browse get markdown for JS-heavy speaker pages.
Path rules: Always use the full literal path in all Bash commands β NOT ~ or $HOME (both trigger "shell expansion syntax" approval prompts). Resolve the home directory once and use it everywhere. When constructing subagent prompts, replace {SKILL_DIR} with the full literal path (typically /Users/jay/skills/skills/event-prospecting).
Output directory: All event prospecting output goes to ~/Desktop/{event_slug}_prospects_{YYYY-MM-DD-HHMM}/. Final deliverable is index.html (people grouped by company, ranked by company ICP), with companies.html and people.html (filterable) as alternate views, plus results.csv for cold-outbound import.
CRITICAL β Tool restrictions (applies to main agent AND all subagents):
- All web searches: use
browse cloud search. NEVER use WebSearch. - All page content extraction: use
node {SKILL_DIR}/scripts/extract_page.mjs "<url>". This script fetches viabrowse cloud fetch --output, parses title + meta tags + visible body text, and automatically falls back tobrowse get markdownwhen fetch fails or returns thin JS-rendered content. NEVER hand-roll abrowse cloud fetch | sedpipeline. NEVER use WebFetch. - All research output: subagents write one markdown file per company OR per person to
{OUTPUT_DIR}/companies/{slug}.mdor{OUTPUT_DIR}/people/{slug}.mdusing bash heredoc. NEVER use the Write tool orpython3 -c. Seereferences/example-research.mdfor both file formats. - Report compilation: use
node {SKILL_DIR}/scripts/compile_report.mjs {OUTPUT_DIR} --open. - Subagents must use ONLY the Bash tool. No other tools allowed.
- HARD TOOL-CALL CAPS: ICP triage = 1 call/company; deep research = 5 calls/company; person enrichment = 4 calls/person. See
references/workflow.mdfor enforcement detail.
CRITICAL β Anti-hallucination rules (applies to main agent AND all subagents):
- NEVER infer
product_description,industry, or a person'srole_reasonfrom a site's fonts, framework, design system, or typography. These are cosmetic and say nothing about what the company sells or what the person does. - NEVER let the user's own ICP leak into a target's description. If you don't know what the target does, write
Unknownβ do not pattern-match them onto the ICP. product_descriptionMUST quote or paraphrase a specific phrase fromextract_page.mjsoutput. If none of TITLE/META/OG/HEADINGS/BODY yield a recognizable product statement, writeUnknown β homepage content not accessibleand capicp_fit_scoreat 3.- A person's
hookMUST quote or paraphrase a specific finding from abrowse cloud searchresult (podcast title, blog headline, GitHub repo, talk abstract). If no public signal exists in the last 6 months, fall back to event-context (their talk title at this event).
CRITICAL β Minimize permission prompts:
- Subagents MUST batch ALL file writes into a SINGLE Bash call using chained heredocs. One Bash call = one permission prompt.
- Batch ALL searches and ALL fetches into single Bash calls using
&&chaining.
Pipeline Overview
Follow these 10 steps in order. Do not skip steps or reorder.
- Setup β output dir + clean slate
- Load profile β read
profiles/{user_slug}.json - Recon β detect event platform
- Extract people β
people.jsonl - Group by company β
seed_companies.txt - ICP triage β fast company-level scoring (1 call/company)
- Filter β companies with
icp_fit_score >= --icp-threshold - Deep research β full PlanβResearchβSynthesize on ICP fits
- Enrich speakers β ask user: ICP-fit only (default) or all speakers
- Compile report β HTML + CSV, open in browser
The user invokes the skill with a URL like /event-prospecting <URL>. Parse EVENT_URL from that invocation message. Defaults: DEPTH=deep, ICP_THRESHOLD=6. The USER_SLUG (ICP profile) is auto-resolved in Step 1 from whatever profile files exist locally β there is no built-in default profile. Do NOT ask the user to confirm the URL β they already gave you it.
Step 0: Setup Output Directory
Derive the output directory from the URL the user gave you. Do NOT hardcode any event name.
# EVENT_URL came from the invocation message (whatever the user typed after `/event-prospecting`)
EVENT_SLUG=$(node -e 'const h = new URL(process.argv[1]).hostname.replace(/^www\./,""); console.log(h.split(".")[0])' "$EVENT_URL")
TIMESTAMP=$(date +%Y-%m-%d-%H%M)
OUTPUT_DIR=/Users/jay/Desktop/${EVENT_SLUG}_prospects_${TIMESTAMP}
mkdir -p "$OUTPUT_DIR/companies" "$OUTPUT_DIR/people"
Use the full literal home path β never ~ or $HOME. Pass {OUTPUT_DIR} as the full literal path to all subagent prompts.
Step 1: Load User Profile
The profile defines the ICP that ICP triage and deep research score against. Load from {SKILL_DIR}/profiles/{user_slug}.json (interchangeable across all GTM skills β same shape as company-research). example.json is a template, not a real profile β never use it.
DO NOT look outside {SKILL_DIR}/profiles/ for profiles β never reach into other skills' directories. If a profile is needed elsewhere, the user copies it explicitly.
Resolution order:
- If the user invoked with
--user-company <slug>, use that slug. - Else, list
profiles/*.jsonexcludingexample.json. If exactly one profile exists, use it (and tell the user which one). If multiple exist, ask the user (plain chat) which one. - If zero profiles exist, fail loudly and instruct the user to create one (copy
profiles/example.jsontoprofiles/<your_slug>.jsonand fill it in, or run the company-research skill which builds one automatically).
PROFILES=$(ls {SKILL_DIR}/profiles/*.json 2>/dev/null | xargs -n1 basename | sed 's/\.json$//' | grep -v '^example$')
COUNT=$(echo "$PROFILES" | grep -c .)
if [ -z "$USER_SLUG" ]; then
if [ "$COUNT" -eq 0 ]; then
echo "No profiles found in {SKILL_DIR}/profiles/. Copy profiles/example.json to profiles/<your_slug>.json and fill it in, or run the company-research skill to build one."
exit 1
elif [ "$COUNT" -eq 1 ]; then
USER_SLUG=$PROFILES
echo "Using the only profile available: ${USER_SLUG}"
else
echo "Multiple profiles found:"
echo "$PROFILES" | sed 's/^/ - /'
echo "Re-invoke with --user-company <slug> to pick one."
exit 1
fi
fi
test -f {SKILL_DIR}/profiles/${USER_SLUG}.json || {
echo "Profile not found: profiles/${USER_SLUG}.json"
exit 1
}
cat {SKILL_DIR}/profiles/${USER_SLUG}.json
The profile yields: company, product, icp_description, existing_customers. These get embedded verbatim in every subagent prompt downstream.
Step 2: Recon
Detect the event platform and extraction strategy. One command:
node {SKILL_DIR}/scripts/recon.mjs {EVENT_URL} {OUTPUT_DIR}
Writes {OUTPUT_DIR}/recon.json with platform, strategy, and (for Next.js) nextDataPaths. See references/event-platforms.md for the platform catalog and detection priority.
Expected outcomes:
- Stripe Sessions class (Next.js):
platform: "next-data", 1-3 paths - Sessionize:
platform: "sessionize" - Lu.ma / Eventbrite:
platform: "luma" | "eventbrite" - Anything else:
platform: "custom",strategy: "markdown"(best-effort fallback)
Step 3: Extract People
node {SKILL_DIR}/scripts/extract_event.mjs {OUTPUT_DIR} --user-company {USER_SLUG}
Reads recon.json, dispatches to the platform-specific extractor, writes people.jsonl (one speaker per line) and seed_companies.txt (deduped companies).
The --user-company flag also drops the host-org's own employees (a Stripe-hosted event drops Stripe employees) and the user's own employees from the speaker list β those aren't prospects.
Sanity-check the output:
wc -l {OUTPUT_DIR}/people.jsonl {OUTPUT_DIR}/seed_companies.txt
head -3 {OUTPUT_DIR}/people.jsonl
If people.jsonl is empty or under ~10 lines, recon picked the wrong platform β see references/event-platforms.md and re-run with adjusted strategy.
Step 4: Group by Company
extract_event.mjs emits seed_companies.txt already (one company per line, deduped, sorted). This step is informational β verify the count looks reasonable before fanning out:
wc -l {OUTPUT_DIR}/seed_companies.txt
Expected: roughly 0.4-0.6Γ the speaker count (most events have ~2 speakers per company on average, some companies send 5+, many send 1).
Step 5: ICP Triage
Fast pass β one tool call per company, no deep research. Score every company in seed_companies.txt against the user's ICP and write a thin triage stub to companies/{slug}.md. Companies with icp_fit_score >= --icp-threshold (default 6) advance to Step 7's deep research; the rest stay as triage stubs.
Dispatch pattern: split seed_companies.txt into batches of ~10 and fan out N subagents in a SINGLE Agent batch (multiple Agent tool calls in one message). Each subagent runs the prompt from references/workflow.md β "ICP Triage" section. Hard cap: 1 tool call per company (just extract_page.mjs on the homepage), enforced via the # browse call N/1 comment pattern.
# Build batch files: each batch line is "name|guessed_homepage|slug".
# extract_event.mjs only emits company NAMES (no URLs), so we slugify and guess
# https://{slug-without-spaces}.com as the canonical homepage. The triage subagent
# is allowed to write product_description: "Unknown β homepage content not accessible"
# and cap score at 3 if the guessed URL 404s β that's the documented fallback in
# workflow.md (rule 3 of the ICP Triage prompt). Burning a real browse cloud search to
# discover the URL would bust the 1-call-per-company HARD CAP.
node -e '
const fs = require("fs");
const slugify = (s) => (s || "").toLowerCase().replace(/[^a-z0-9]+/g, "-").replace(/^-+|-+$/g, "");
const seed = fs.readFileSync("{OUTPUT_DIR}/seed_companies.txt", "utf-8").split("\n").filter(Boolean);
const lines = seed.map(c => {
const slug = slugify(c);
const guessedHost = c.toLowerCase().replace(/[^a-z0-9]/g, "");
return `${c}|https://${guessedHost}.com|${slug}`;
});
fs.writeFileSync("{OUTPUT_DIR}/_seed_with_urls.txt", lines.join("\n") + "\n");
'
# Split into ~10-company batches
split -l 10 {OUTPUT_DIR}/_seed_with_urls.txt {OUTPUT_DIR}/_batch_triage_
# Count batches β number of subagents to dispatch (cap at 6 per message; second wave for the rest)
ls {OUTPUT_DIR}/_batch_triage_* | wc -l
Then in a single message,
Truncated for display β read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 β pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way β as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an emβ¦
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVGβ¦
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit β see the Safety scan above for what the skill file itself contains.
