← ClaudeAtlas

event-attendee-extractorlisted

Turns an event page link (Partiful, Luma, Eventbrite, Meetup, Lu.ma calendars, conference pages, Tech Week listings) into a clean CSV of attendees with name, job title, company, LinkedIn and other social links. Use this skill whenever the user shares an event URL and wants to know who is going, who the guests are, who is on the list, or wants attendees / participants / RSVPs / guest list exported, enriched, or turned into a prospect list. Trigger even if they just paste an event link and say "get me the attendees", "who's attending this", "scrape the guest list", "find the people going to this", "enrich these guests", or paste a wall of guest names copied from an event page. Always produces a CSV plus a confidence score per attendee. Do not use for scraping product pages, pricing, or job listings (use website-scraper) or for general company research.
vicfromthegtmclub/gtmskills · ★ 1 · Data & Documents · score 68
Install: claude install-skill vicfromthegtmclub/gtmskills
# Event Attendee Extractor Take an event link, get the guest list, enrich every guest with occupation, company and social links, and hand back a CSV the user can push into lemlist or a CRM. Respond in the user's language. Write the CSV in English column names so it imports cleanly. ## The one thing to understand first Event platforms show very little. Partiful shows display names and cartoon avatars, and hides the list behind "Must be on the list to view". Luma shows names and sometimes a one-line bio. Eventbrite and Meetup show first name plus initial at best. None of them show job title, company or LinkedIn in a reliable way. So this is always a two-stage job: 1. **Capture**: get the raw names off the page the way the user sees it (logged in). 2. **Enrich**: resolve each name to a real professional profile using the event context as the disambiguation key, then pull title, company and socials. Never skip stage 2 by guessing titles from names. An unenriched row is fine; an invented row is not. ## Stage 0: Read the event page (always, before anything else) `web_fetch` the URL first, even if the guest list is gated. You need the **event context** for the enrichment stage, and this is free: - Event name, date, city - Host name and host company - Audience described in the blurb ("B2B founders and marketing leaders", "designers", "VCs") - Any hashtag or umbrella event (#SFTechWeek, Web Summit, VivaTech) - Whether the guest list is public, partially visible, or gated