Purpose
Produce a ready-to-distribute event communication kit that gives speakers a tight briefing and gives frontline staff exact talking points, FAQ responses, and escalation paths — so every person representing the event delivers the same core message in their own voice. Eliminates the last-minute scramble of writing briefs the week of the event and the inconsistency that comes from staff improvising.
When to Use
Invoke this skill when the user asks to:
- Prepare a keynote speaker, panelist, or presenter with a briefing document
- Train booth staff, volunteers, or brand ambassadors on what to say
- Create talking points or scripts for a conference, trade show, or product launch
- Build FAQ responses and objection-handling guidance for an event team
- Standardize event messaging across multiple staff or multiple sessions
- Write a run-of-show communication kit before an in-person or virtual event
Inputs Required
Before starting, collect:
- Event type and format: Conference session, trade show booth, product launch, webinar, panel, in-person activation, etc.
- Event goal: The single outcome the event must drive (sign-ups, demos booked, awareness, pipeline, product adoption)
- Core message: The one thing every attendee should walk away understanding
- Audience: Who is attending — role, seniority, buying stage, familiarity with the brand
- Brand voice: 3–5 adjectives describing how the brand should sound (e.g., confident, warm, plainspoken)
- Roles to brief: Which roles need materials — speakers, booth staff, registration/greeters, volunteers
- Known sensitive topics or hard questions: Pricing, competitors, roadmap, incidents, or anything staff should not freelance on
If brand voice or sensitive topics are missing, use plainspoken professional defaults for voice and flag pricing/roadmap/competitor questions as escalate-by-default.
Instructions
Step 1: Distill the Message Spine
Before writing any script, lock the message architecture everyone will work from:
- One-sentence core message: The single takeaway, phrased so a staffer could repeat it verbatim
- Three supporting proof points: The specific facts, results, or differentiators that back the core message
- One primary call to action: The single action attendees should take (visit the booth, scan the QR code, book a demo, sign up)
- What we do NOT say: 2–4 topics staff must route rather than answer
Every downstream script must trace back to this spine. If a line doesn't reinforce the core message or CTA, cut it.
Step 2: Build the Speaker Briefing
Produce a one-page speaker brief containing:
- The assignment: Session title, format, length, audience, and the one thing this session must accomplish
- Opening hook (written out): A 2–3 sentence opener the speaker can use or adapt — pattern-interrupt, provocative stat, or relevant question
- Message flow: 3–5 beats mapping how the talk moves from hook → problem → point of view → proof → CTA
- Signature line: One quotable sentence the speaker should land clearly — the tweetable moment
- Transitions and CTA close: Exact wording for the close that drives the primary action
- Tone note: 1–2 sentences on how to sound given this specific audience
- Landmines: Topics to avoid or deflect, with a one-line redirect for each
Write the brief so a speaker can skim it in 90 seconds and internalize it in 10 minutes.
Step 3: Build Staff Talking Points
For each frontline role provided, create a talking-points card:
- Role goal: The one behavior this role should drive at the event
- The 15-second pitch (written out): What to say when someone approaches or asks "what is this?" — conversational, not scripted-sounding
- The follow-up question: One question that qualifies interest and opens a conversation
- Bridge to CTA: The exact phrasing that moves a warm conversation toward the primary action
- Voice guardrails: 2–3 phrases that are on-brand and 2–3 phrases to avoid
Keep each card short enough to fit on a lanyard-sized reference or a phone screen.
Step 4: Write the FAQ and Objection Scripts
Draft 8–12 anticipated questions attendees will ask, split into:
- Answer directly (6–8 questions): Product, logistics, "how does this work," "who's it for" — with a written response staff can deliver in their own words
- Answer with care (2–4 questions): Sensitive but answerable topics — with an approved framing and clear boundaries on what not to promise
- Escalate (2–3 questions): Pricing specifics, competitor comparisons, roadmap, or complaints — with the exact handoff line and who to route to
For each escalate item, include a graceful bridge sentence so staff never say "I can't answer that" flatly.
Step 5: Add the Escalation and Run-Support Guidance
Close the kit with operational safety rails:
- Escalation map: What kind of question or situation goes to which person/role, with a named handoff phrase
- If something goes wrong: A 2–3 line holding response for a demo failure, a hostile question, or a logistics breakdown
- The reset line: A single sentence any staffer can use to steer any awkward moment back to the core message and CTA
Output Format
- Structure: Five labeled sections in kit order — Message Spine → Speaker Briefing → Staff Talking Points (one card per role) → FAQ & Objection Scripts (grouped by answer/care/escalate) → Escalation & Run-Support Guidance
- Length: 900–1,400 words
- Format: Structured document — briefing prose for the speaker section; scannable cards and labeled Q→A pairs for staff and FAQ sections
- Sections: Message Spine; Speaker Briefing; Staff Talking Points; FAQ & Objection Scripts; Escalation & Run-Support Guidance
- Tone: Practical and repeatable — written in the brand voice provided, calibrated so a non-professional presenter or a first-day volunteer could use it confidently without further editing
Quality Checklist
Before delivering output, verify:
- [ ] The one-sentence core message and single primary CTA are stated once and reused consistently across every section
- [ ] Every role listed in the inputs has its own talking-points card (count them against the roles provided)
- [ ] FAQ section contains 8–12 questions split into answer-directly / answer-with-care / escalate, and every escalate item has a written handoff line
- [ ] Speaker briefing includes a written-out opening hook, signature line, and CTA close — not just instructions to "add a hook"
- [ ] Every sensitive topic named in the inputs appears in either the "answer with care" or "escalate" list — none are left for staff to improvise
- [ ] All scripted lines are written in the specified brand voice, with no bracket placeholders left in the final text
Notes
- The 15-second staff pitch is the highest-leverage element — it's said the most times across an event, so prioritize making it sound natural rather than corporate.
- Speakers resist over-scripting; give them the message spine and signature line, then let them phrase the rest — a brief that's too rigid gets ignored.
- If the event runs multiple sessions or shifts, the message spine stays fixed while talking-points cards can be duplicated and lightly tailored per role — reuse the spine, not the whole kit.
- For virtual events, add a chat-response variant of the FAQ scripts, since much staff communication happens in text rather than in person.
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills