event-speaker-experiencelisted

Run the speaker-side experience from the moment a speaker confirms through to the thank-you after their talk - collecting bio, headshot, A/V needs and travel details against a deadline ladder, a single named point of contact, the pre-event briefing and slide deadline, tech check and green room, documented recording consent and its per-format opt-out asymmetry, and post-event follow-up. Use whenever the user mentions what to send an accepted speaker, a green room, speaker travel or hotel, a tech check, recording consent, a speakers' dinner, or supporting a first-time speaker - even if they never say "speaker experience". Do NOT use before acceptance - inviting is samber/dev-event-organizer-skills@event-speaker-cold-outreach.
samber/dev-event-organizer-skills · ★ 2 · AI & Automation · score 76

Install: claude install-skill samber/dev-event-organizer-skills

# Event Speaker Experience You take care of a speaker who has already said yes. Your input is the acceptance email `samber/dev-event-organizer-skills@event-talk-selection` has just sent, and specifically its closing line: "What you get: {the perks exactly as the call stated them}. What we need next: {confirmation, bio, headshot, slide deadline, travel or A/V details}." You start there. Your output is a speaker who arrives knowing what happens when, delivers without an equipment surprise, agreed in writing to whatever was recorded, and hears from you after the event. What this skill does not do: - **Promise terms**: you do not decide what a speaker is promised. `samber/dev-event-organizer-skills@event-cfp-design` set the perks and left the honorarium open. You deliver whatever was promised and never invent a figure nobody confirmed. - **Decline or waitlist messages**: not your ground - that belongs to `samber/dev-event-organizer-skills@event-talk-selection`, and those speakers never enter your scope. - **Sourcing, inviting or selecting**: you do none of it. - **Population-agnostic fundamentals**: you add only the speaker-specific layer on top of `samber/dev-event-organizer-skills@event-hospitality`, and you hand timing needs upstream rather than writing a schedule yourself. Every ranking below is a default, not a law - it shifts with context and with who executes it. After the interview, re-rank all three menus against what you know - each of the following overturns a def