fullenrich-event-attendees
Skill298 starsChanged 6 months agoMITView on GitHub
Use when the user says "enrich this LinkedIn event", "enrich attendees of this event", "enrich this attendees CSV", "scrape and enrich LinkedIn event {URL}", "FullEnrich event attendees", or any variant indicating they want to turn LinkedIn event attendees into an SDR-ready CSV with verified emails and mobile phones. Two input modes: (a) bring-your-own attendees CSV (PhantomBuster, Evaboot, Sales Navigator, manual paste), or (b) run a user-configured Apify actor against a LinkedIn event URL. Both converge on FullEnrich v2 bulk enrichment with webhook callback delivery.
- Reads credentials
In this repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- answer-linkedin-commentsSkill
- build-routineSkill
- campaign-dashboardSkill
- campaign-strategySkill
- claap-weekly-recapSkill
- cross-platform-schedulerSkill
- debuggerSkill
- enrich-with-signalsSkill
- find-lookalikesSkill
- fullenrich-content-engagersSkill
- fullenrich-network-activationSkill
- fullenrich-plg-reverse-lookupSkill
- icp-importSkill
- import-leadsSkill
- integrate-with-yalcSkill
- launch-linkedin-campaignSkill
- lemlist-campaign-from-icpSkill
- list-adaptersSkill
- lost-deal-revival-agentSkill
- notion-reviewSkill
- personalize-messageSkill
- predictleads-dashboardSkill
- predictleads-lookalikesSkill
- predictleads-signalsSkill
- prospect-discovery-pipelineSkill
- provider-builderSkill
- qualify-leadsSkill
- research-prospectSkill
- run-competitive-intelSkill
- run-doctorSkill
- scrape-post-engagersSkill
- send-cold-emailSkill
- setupSkill
- show-routineSkill
- track-campaignsSkill
- yalc-orientationSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Does not include a built-in LinkedIn event scraper.
- Very specific: line 33
Does not write outreach copy.
- Distinctive: line 34
Does not push to a CRM.
- Distinctive: line 41
Always shows current balance: before doing anything.
- Very specific: line 48
ALWAYS run with --dry-run first to surface the attendee count and estimated cost.
- Very specific: line 50
WAIT for explicit user confirmation before re-running without --dry-run.
- Very specific: line 51
Only pass --yes after the user has approved the spend in this conversation.
- Very specific: line 101
Write enriched CSV with first_name, last_name, linkedin_url, email, email_status, phone, company_domain.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
FullEnrich Event Attendees
Turn a list of LinkedIn event attendees into an SDR-ready CSV with verified work emails and mobile phones, using the FullEnrich 20-vendor waterfall.
When This Skill Applies
- "enrich attendees of this event {URL}"
- "enrich this attendees CSV"
- "scrape and enrich LinkedIn event {URL}"
- "FullEnrich event attendees"
Two input modes
The skill does NOT bundle a LinkedIn event scraper. LinkedIn doesn't expose event attendees through any clean public API and Unipile's surface area doesn't cover events either. So the skill ships with two input paths and the user picks:
Mode A — CSV file (recommended). Bring an attendees CSV from any source:
- Manual copy-paste from the LinkedIn event page
- PhantomBuster "LinkedIn Event Attendees Export" automation
- Evaboot Sales Navigator export filtered to event registrants
- Any other tool
Mode B — Apify actor (BYO). The user configures an Apify actor (e.g. giovannibiancia/linkedin-events-partecipants-scraper) under their own Apify account, supplies their LinkedIn cookies via env vars, and the skill runs it. The skill does not pin a specific actor — the user picks one and provides the actor input shape via --actor-input if its keys differ from the defaults.
What This Skill Does NOT Do
- Does not include a built-in LinkedIn event scraper. Pick mode A or B above.
- Does not write outreach copy. Pair with
personalize-messageafter. - Does not push to a CRM.
- Does not spend FullEnrich credits without explicit user approval. See "Credit safety contract" below.
Credit safety contract (MANDATORY)
This skill spends FullEnrich credits, which cost real money. Safeguards:
- Always shows current balance before doing anything.
- Always shows estimated cost of the run.
--max-credits Nceiling (default 500) — auto-trims the contact list to fit.- Hard-approval prompt — blocks on stdin until the user types
yes. Non-TTY without--yesaborts. --dry-runmode — parses input + computes cost preview without spending a credit.
When Claude invokes this skill on a user's behalf:
- ALWAYS run with
--dry-runfirst to surface the attendee count and estimated cost. - Quote the EXACT estimated credit cost back to the user.
- WAIT for explicit user confirmation before re-running without
--dry-run. - Only pass
--yesafter the user has approved the spend in this conversation. - Exception: respect locally modified scripts.
Prerequisites
FULLENRICH_API_KEY= # https://app.fullenrich.com/app/apiFor Apify mode (Mode B) only:
APIFY_TOKEN= # https://console.apify.com/account/integrations
LINKEDIN_LI_AT= # browser cookie 'li_at' from a logged-in LinkedIn session
LINKEDIN_JSESSIONID= # browser cookie 'JSESSIONID'
LINKEDIN_USER_AGENT= # full UA string from the same browserOptional:
FULLENRICH_WEBHOOK_URL= # public URL for callbacks; otherwise a webhook.site URL is provisionedCLI Reference
Mode A — CSV file:
node scripts/run.mjs --input attendees.csv
[--out path.csv] # default attendees.csv (overwrite-safe via different name)
[--max <N>] # max attendees to consider (default 250)
[--max-credits <N>] # hard credit ceiling (default 500)
[--dry-run] # no spending
[--yes | -y] # skip the interactive approval promptMode B — Apify actor:
node scripts/run.mjs --event-url https://www.linkedin.com/events/<id>/
--actor <user>/<actor-slug>
[--actor-input '{"event_urls":["..."],"cookies":[...]}'] # override input shape per actor
[--out path.csv] [--max N] [--max-credits N] [--dry-run] [--yes]Workflow
- Validate inputs and load contacts (Mode A: parse CSV; Mode B: run Apify actor with humanlike polling).
- Map every row to FullEnrich-ready contact fields (
first_name,last_name,linkedin_url,company_name,domain,title). - Estimate FullEnrich credit cost from the contact list.
- Show cost preview, block on stdin for
yes. - Chunk into ≤100 contacts per FullEnrich bulk request, request
contact.work_emails+contact.phones. - Receive webhook callbacks (~30s per batch).
- Write enriched CSV with
first_name, last_name, linkedin_url, email, email_status, phone, company_domain.
Reference
- Shared API client:
./scripts/lib/fullenrich-client.mjs - Shared webhook receiver:
./scripts/lib/fullenrich-webhook.mjs - Shared CSV reader/writer:
./scripts/lib/csv.mjs - FullEnrich v2 docs:
https://docs.fullenrich.com/llms.txt - Webhook payload shape (verified live):
{ id, name, status: "FINISHED", cost: { credits }, data: [{ input, custom, contact_info: { most_probable_work_email: { email, status }, work_emails, personal_emails, phones } }] }
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

