event-speaker-experience

Manages confirmed conference speakers from acceptance through post-event follow-up and recording consent.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-speaker-experience-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-speaker-experience
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-speaker-experience
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-speaker-experience-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Once a speaker accepts, organizers juggle bios, headshots, A/V needs, travel, recording consent, tech checks, and follow-up across scattered threads, and dropped commitments damage the event's reputation with exactly the people who talk to other speakers. ## Core Features & Use Cases - Deadline-anchored material collection: Builds a dated ladder pinning each item (bio, headshot, slides, A/V, travel) to the last date it is still usable, such as the programme print date or the venue's equipment ordering deadline. - Recording consent posture: Designs per-format consent covering recording, live streaming, and publication separately, with a consent record checked before anything goes public. - On-site speaker care: Defines the named point of contact, speaker packet, tech check on the real stage, green room norms, and post-event thank-you, feedback, and retention pass. - Use Case: Acceptance emails just went out for eleven speakers and three organizers are replying from personal accounts; the skill produces a single named contact, a speaker packet, and a per-item deadline ladder tied to the printer's date. ## Quick Start Ask the skill what to send newly accepted speakers and what to collect back from them by when, given your event date and print deadlines.

Frequently Asked Questions about event-speaker-experience

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What do I send speakers after they accept a conference talk?

Send one speaker packet containing their slot, room, format and length, all deadlines with reasons, the recording policy for their format, travel and reimbursement mechanics, arrival instructions, and one named contact with a stated response window.

How do I set deadlines for speaker bios and headshots?

Pin each material to the last date it is still usable, not the event date. Bios and titles pin to the programme print date, headshots to badge or programme production, and A/V needs to the venue's own equipment ordering deadline.

Does a CFP recording checkbox cover invited keynote speakers?

No. Invited speakers never filled in the submission form, so bundled consent does not cover them. Present the same recording, streaming, and publication terms at acceptance and record their answer per session format.

Should we book speaker travel directly or reimburse afterwards?

Reimbursement filters the lineup by who can front a flight and wait for repayment. Book and pay directly, or offer an advance, at least for international speakers and anyone who cannot carry the cost, and state the mechanism in the packet.

When should I not use this speaker experience skill?

Do not use it before acceptance: sourcing, cold outreach, CFP design, and selection belong to other skills. It also does not decide promised perks or write the day-of run-of-show; it delivers what was promised and hands timing needs upstream.

How long should we keep speaker passport and payment details?

Decide the deletion date when you collect the documents, write it in the speaker packet, and delete on that date. Nothing in travel handling needs to outlive the reimbursement; keep only the consent record and agreed contact details.