Resources / Event Attendee List Builder
Live Discovery Events

"Saw you spoke at," one of the best cold openers.

Drop an event URL. The skill extracts the speaker / sponsor / exhibitor list as a structured CSV, with the event itself as the outreach hook. It's honest about what's public (speakers, sponsors, exhibitors usually yes) and what isn't (full attendee lists almost never).

Download skill Install instructions
v1.0 Web fetch required CSV + JSON output Self-selection signal
EV
event-attendee-list-builder.zip
16.9 KB · Bundle: .skill file + SKILL.md inside · v1.0
Download skill
Want to read what it does first? View source ↓
What it does

Events are self-selection signals.

Events are high-leverage for two reasons. The event itself is a real conversation hook, "saw you spoke at [conference] last week" is one of the strongest cold openers possible. And paying to attend, sponsor, or speak at a specific event is a category-interest signal that's harder to fake than firmographic guessing.

What's publicly extractable: speakers (with names, titles, companies), sponsors (often tiered diamond/platinum/gold), exhibitors, moderators, workshop instructors. What isn't: full attendee lists. The skill won't fabricate one. If you ask for "attendees of SaaStr", you'll get the speakers and sponsors, with a note that the full attendee list isn't public.

Stale event pages are a hidden trap, a 2-year-old conference page is evidence those people went 2 years ago, not current targets. The skill verifies the year/date and won't pitch a "saw you at [conference]" hook for an event that happened in 2023.

Try saying

Any of these will work.

Who's speaking at [conference URL]?
Sponsors and exhibitors of [event]
Build me an account list from this conference.
Find me speakers from SaaStr 2026.
How it works

Five steps.

01

Confirm the event

Disambiguate, many events have similar names (SaaStr Annual vs SaaStr Build vs SaaStr Europe). Verify the year, a 2023 conference is evidence for 2023, not now.

02

Fetch the event site

Speakers page, sponsors page, agenda, exhibitor hall, press page. Each gets parsed for company + role + role-in-event.

03

Surface what's public

Speakers, sponsors, exhibitors, moderators, instructors, all extractable. Full attendee lists almost never are; the skill says so plainly.

04

Filter and resolve

Drop pure marketing entities. Resolve domains. Tag each row with role-in-event (speaker / sponsor / exhibitor / moderator).

05

Emit CSV + JSON

CSV ready for Sales Nav upload. JSON for chaining into signal-based-dm-trigger ("saw you spoke at,") or account-research-brief.

Why it doesn't lie to you

No invented attendees.

!

Speakers ≠ attendees

Speaker lists are public. Full attendee lists almost never are. The skill never fabricates "300 attendees", it returns what's actually listable.

#

Year/date verified

A 2023 conference page is evidence of who went in 2023, not who's going now. The skill verifies the event's date before treating it as a fresh signal.

@

Role-in-event tagged

Speaker vs sponsor vs exhibitor matters for the outreach angle. A sponsor commits budget; a speaker commits time. Every row tagged.

?

Event-collision disambiguated

SaaStr Annual, SaaStr Build, SaaStr Europe are different events. The skill confirms which specific event before pulling lists.

The output

Companies + people, tagged by role.

Two CSVs (companies, people) plus a JSON for chaining. Every row carries the role-in-event (speaker / sponsor / exhibitor / moderator), the event name, and a source URL. Ready for outreach using the event itself as the conversation hook.

Sample row
Sarah Chen title: VP RevOps company: Globex domain: globex.io event: SaaStr Annual 2026 role: Speaker track: Revenue Operations source: saastr.com/sessions /pricing-tiers Hook: "Saw your talk on..."
Event contract
Output
CSV (people, companies) + JSON
Role types
Speaker / Sponsor / Exhibitor / Mod
Required tools
web_fetch, web_search
Date verification
Required
Attendee fabrication
Never
Pairs with
signal-based-dm-trigger
Install

Pick your Claude. Drop in the skill.

The download is a zip containing two things: the .skill file (what you upload to Claude) and a SKILL.md sidecar (the human-readable instructions). Unzip first, then follow the steps for your Claude.

⌘
Most people

Claude.ai or Desktop

  1. Download and unzip the bundle.
  2. Open or create a Project in Claude.
  3. Go to Project knowledge, click Add content.
  4. Upload the .skill file from the unzipped bundle.
  5. Start a new chat in that project. Ask it to run the skill.
Download bundle ↓ No restart needed
›_
Developers

Claude Code

  1. Download and unzip the bundle.
  2. Unzip the inner .skill file too (it's also a zip).
  3. Move the resulting folder into ~/.claude/skills/
  4. Restart Claude Code.
  5. Type a prompt that fits the trigger. The skill loads automatically.
Download bundle ↓ macOS / Linux / WSL
{ }
Builders

API or Agent SDK

  1. Download and unzip the bundle.
  2. Open the SKILL.md sidecar to read the full instructions.
  3. Load via the Skills API, or paste the instructions into your agent's system prompt.
  4. Make sure your agent has web_search and file output enabled.
  5. Ship it.
View SKILL.md ↓ v1.0
Source

Read the full instructions.

This is exactly what Claude reads when the skill triggers. No hidden prompts, no separate config. What you see here is what you get.

MD
event-attendee-list-builder-SKILL.md 11.6 KB · the full skill instructions
⌄
Loading SKILL.md...

Need help implementing this on your team?

We'll install the skills, customize them to your workflow, and run the output through your team's combined LinkedIn network. Skills do the research, Linkd does the motion.

Book a demo