---
name: speaker-content
description: Process and transform speaker content for event programs, marketing, and communications. Use when creating speaker bios in multiple formats, writing session descriptions, drafting CFP submissions, generating speaker proposals, building run-of-show intros, or processing speaker packets. Triggers on requests involving speaker bios, session descriptions, learning outcomes, CFP submissions, emcee scripts, or speaker proposals.
---

# Speaker Content Processor

## Purpose
Transform raw speaker information into polished, event-ready content — bios, session descriptions, emcee intros, and proposals — fast and consistently.

## When to Use
- Creating speaker bios in multiple formats (emcee, program, website, social)
- Writing or rewriting session descriptions for an event program or website
- Drafting CFP submissions for a speaker or event
- Building emcee scripts and run-of-show introductions
- Processing a speaker packet into standardized event-ready outputs
- Generating speaker proposals for clients or bureaus

## Inputs
- Speaker name, title, and company
- Credentials, notable achievements, and one humanizing or personal detail
- Session title and abstract (raw or polished)
- CFP requirements (word counts, track/theme, required fields) if applicable
- Target audience and event context

## Quick Reference

### Bio Formats
- **25-word emcee intro**: "Please welcome [Name], [credential] who [achievement]."
- **50-word program bio**: Name + expertise + 1-2 achievements + one humanizing detail
- **100-word website bio**: Expanded credentials, professional-approachable tone, third person
- **LinkedIn teaser** (for event promotion): First-person, 2-3 sentences, ends with a hook

### Session Description Formula
1. Opening hook — what's at stake or what problem this solves (15 words)
2. What attendees will learn or do (30 words)
3. Specific takeaways they'll leave with (20 words)
4. Why it matters right now (10 words)

### Learning Outcomes
Always start with action verbs: **Implement, Apply, Build, Create, Deploy, Evaluate, Identify, Master**
Never use: Explore, Discuss, Learn about, Understand, Discover, Dive into, Unpack

## Workflow by Task

### Task 1: Generate Bio Variations
1. Gather key facts: name, title, company, credentials, 1-2 achievements, one personal/humanizing detail
2. Draft all three bio formats (25-word, 50-word, 100-word)
3. Ensure third-person consistency throughout
4. Strip fluff words (see What to Avoid below)
5. Read emcee intro aloud — it must flow naturally when spoken

### Task 2: Write Session Description
1. Identify the core value proposition: what does the attendee GAIN?
2. Rewrite in attendee-focused language (not speaker-centered)
3. Generate 75-word abstract + 3 action-verb learning outcomes
4. Verify no weak verbs are used
5. Test: does this make someone want to attend?

### Task 3: Draft CFP Submission
1. Match the CFP requirements (word counts, fields required, track/theme)
2. Generate all required elements: title, description, outcomes, bio, tech requirements
3. Make track alignment explicit in the description
4. Verify word counts match requirements exactly before submitting

### Task 4: Build Emcee / Run-of-Show Intro
1. Pull from the 25-word formula
2. Add one sentence of session context ("In this session, [Name] will walk us through...")
3. End with an applause cue: "Please give a warm welcome to..."
4. Read aloud test — no tongue-twisters, no awkward pauses

### Task 5: Process a Speaker Packet
1. Review all submitted materials (bio, headshot info, session abstract, AV needs)
2. Generate standardized outputs: formatted bio, session abstract, 3 takeaways, alt text for headshot
3. Run quality control: third person, no fluff, action verb outcomes
4. Export in a format ready for your event program or website

## Output Format
- **Bio variations**: Three versions (25-word, 50-word, 100-word) in a single document, labeled by format
- **Session description**: 75-word abstract + 3 learning outcomes with action verbs
- **CFP submission**: All required fields filled, word counts matched, track alignment explicit
- **Emcee intro**: Speakable 2-3 sentence introduction with applause cue
- **Speaker packet output**: Formatted bio, session abstract, takeaways, and alt text in one clean document

## Key Principles

### Attendee-Focused, Always
- FROM: "In this session, I'll share my 10 years of experience..."
- TO: "Walk away with a tested framework you can implement next week."

The shift: What attendees GAIN, not what the speaker SHARES.

### Remove the Fluff
Banned words: thought leader, visionary, guru, passionate about, world-class, cutting-edge, revolutionary, groundbreaking, leverage, synergize, transformative, innovative

Replace with: specific numbers, named clients or events, measurable outcomes, concrete credentials.

### Speakable Intros
Emcee introductions must be tested by reading aloud. If it's hard to say, it's hard to hear.

### Consistency Across Assets
The same speaker should sound cohesive whether their bio appears in the app, on the website, in the program, or in an email. Slight variations in length, same core narrative.

## What to Avoid
- Using banned fluff words: thought leader, visionary, guru, passionate about, world-class, cutting-edge, revolutionary, groundbreaking, leverage, synergize, transformative, innovative
- Writing learning outcomes with weak verbs: Explore, Discuss, Learn about, Understand, Discover, Dive into, Unpack
- Speaker-centered session descriptions that focus on the presenter's experience rather than attendee gains
- Emcee intros that are difficult to read aloud — test every one before finalizing
- Inconsistent voice or narrative across bio formats for the same speaker
- Copying the speaker's own bio language without editing it into event-ready format

## Tool / System Integration
- **Google Docs**: Draft all bio variations in a single Doc for easy client review and comment
- **Google Sheets**: Use a speaker roster sheet to track bio status (received / drafted / approved)
- **Gmail**: Use the 25-word bio directly in speaker announcement emails
- **Google Drive**: Store approved bios in a shared speaker folder for your whole team
- **OneDrive**: Same workflow applies — save approved bios to your shared speaker folder for team access

## Resources
- `references/bio-formats.md` — Bio length standards and format templates with examples
- `references/session-standards.md` — Session descriptions, learning outcomes, CFP checklist
- `references/proposal-templates.md` — Speaker proposal templates for clients and bureaus
- `references/fluff-word-list.md` — Banned words and their stronger replacements