Prospecting · Claude Code skill

FullEnrich Event Attendees skill and the Yalc Framework

Turns LinkedIn events into a usable lead source for the first time. The CSV input mode means anyone can use it without scraper drama. FullEnrich does the verification waterfall so the output is ready for outreach, not a list of guesses.

Yalc Fit Score
9/10
License
MIT (Yalc)
Input modes
CSV file or BYO Apify actor
Provider
FullEnrich v2 (20 vendor waterfall)
Last reviewed
2026-05-06
Trigger phrases

Say this to fire the FullEnrich Event Attendees skill

Any of these natural language phrases activates the skill inside Claude Code.

enrich this LinkedIn event
enrich attendees of this event
enrich this attendees CSV
scrape and enrich LinkedIn event
FullEnrich event attendees
turn LinkedIn event into SDR list
What it does

FullEnrich Event Attendees, plainly

The FullEnrich Event Attendees skill takes a list of LinkedIn event attendees and turns it into an SDR ready CSV with verified work emails and mobile phones. Attendees come from a CSV file you drop in (PhantomBuster, Evaboot, Sales Navigator, or manual paste from the LinkedIn event page) or from a BYO Apify actor you configure with your own LinkedIn cookies.

Once the contact list lands, the skill estimates the credit cost, blocks on a hard approval prompt, then runs the contacts through FullEnrich v2 bulk enrichment with webhook callback delivery. Output is a flat CSV with email status from the FullEnrich triple verification waterfall.

Built in partnership with FullEnrich for the Yalc x FullEnrich skill family.

Where it slots in

Position in the GTM operating system

Intake
→
Enrich
→
Score
→
Route
→
Draft
→
Send
→
Listen

The FullEnrich Event Attendees skill sits at the **source** node of the Yalc workflow. Most operators ignore LinkedIn events as a lead source because the export does not exist and the attendee list is gated. This skill collapses that gap into a single command.

The hard approval gate before any FullEnrich API call is the safety story. You always know exactly how much you are about to spend, and the script will not spend a single credit until you type "yes" or pass --yes.

The Yalc Framework

Running the FullEnrich Event Attendees skill end to end

Workflow position

First step in any event driven outbound campaign. Output flows downstream into qualify-leads (if you want ICP scoring) or directly into unipile-campaign or email-sequence for outreach.

Required inputs

  • → Either a CSV of attendees (any common header shape) or a LinkedIn event URL plus a BYO Apify actor with cookies
  • → FULLENRICH_API_KEY from https://app.fullenrich.com/app/api

Outputs

  • → Flat CSV with first_name, last_name, linkedin_url, email, email_status, phone, company_domain
  • → Per row email_status from FullEnrich triple verification (DELIVERABLE, RISKY, INVALID, UNKNOWN)
  • → Auditable cost report (credits spent per batch via the webhook payload)

Chaining recommendations

UpstreamPhantomBuster, Evaboot, Sales Navigator, or BYO Apify actor with LinkedIn cookies
DownstreamQualified rows can flow into qualify-leads or directly into unipile-campaign or email-sequence

Anti patterns to avoid

Do not skip the --dry-run preview on first run. The cost preview tells you exactly what is about to happen.
Do not run without a --max-credits ceiling on lists you have not verified. Bad CSVs with 5,000 rows are how accidents happen.
Do not paste LinkedIn cookies into a public repo or shared chat. They authenticate the entire account.
Operator take

Pros, cons, who it's for

Pros

  • Two input modes cover every realistic source (BYO CSV or BYO Apify)
  • Hard approval gate makes credit spend explicit, never silent
  • Header mapping is tolerant of PhantomBuster, Evaboot, Sales Navigator, and manual paste
  • Webhook based delivery, not polling, so 200 contacts come back in 30 seconds not 5 minutes
  • --max-credits ceiling auto trims the list, --dry-run shows the preview without spending

Cons

  • Apify mode needs you to extract LinkedIn cookies once. They rotate every few weeks.
  • FullEnrich credits cost real money. A 200 attendee event runs about 600 credits.
  • The skill does not write outreach copy. Pair with personalize-message after.

Who it's for

  • GTM operators running event driven outbound (you find a relevant LinkedIn event, you want the attendees in pipeline by end of day)
  • Founders pre and post launch who want to mine industry events without paying for Sales Navigator
  • Agencies running multi client outbound who need a repeatable event to outreach pipeline
Dependencies

What this skill expects to find

MCP servers

Environment variables

The skill runs the FullEnrich v2 API directly so it works without the FullEnrich MCP. The MCP is a bonus path for ad hoc enrichment from inside Claude Code.

Related

The FullEnrich Event Attendees ecosystem inside Yalc

FullEnrich Content Engagers
Sister skill for LinkedIn post engagers. Same pipeline, different source.
→
Alternatives

Skills that overlap

Manual outreach with LinkedIn DMs
Skip the skill if your event has under 30 attendees and DMing each one is faster than the CSV round trip.
→
ZoomInfo enrichment
Switch if you already have a ZoomInfo seat and want everything inside that platform.
→
Clay.com workflow
Switch if you want a visual no code waterfall instead of a single command.
→
FAQ

Frequently asked

Why two input modes instead of one?

LinkedIn does not expose event attendees through any clean API and Unipile does not cover events. So we ship both paths and let the user pick. CSV mode is the easier path. Apify mode is the URL to CSV path if you have set up an Apify actor with cookies.

Which Apify actor should I use?

We do not pin a specific actor. Pick one in the Apify Store like giovannibiancia/linkedin-events-partecipants-scraper. Different actors have different input shapes; pass --actor-input '{"...":"..."}' if needed.

How much do FullEnrich credits cost?

Refer to your FullEnrich plan. As a rule of thumb, 1 credit per work email lookup, 2 per phone. A 200 attendee event with both fields runs about 600 credits.

What happens if I run out of credits mid run?

The script reads your balance before any API call and the --max-credits ceiling auto trims the contact list to fit. Even without it, you can pass --max-credits N to set a hard cap.

Can I trust the email_status values?

FullEnrich runs every email through a 20 vendor waterfall plus triple verification. DELIVERABLE means it deliverable today. UNKNOWN means the verification was inconclusive. Use DELIVERABLE only for cold outreach.

Get the FullEnrich Event Attendees skill

Clone the Yalc skill set, drop in your env, run from your next Claude Code session.

gh repo clone Othmane-Khadri/YALC-the-GTM-operating-system && cd YALC-the-GTM-operating-system/.claude/skills/fullenrich-event-attendees && cp .env.example .env
View on GitHub We deploy it for you
Last reviewed 2026-05-06 by Othmane Khadri