SKILL.md - Cybersecurity Supercommunicator Guide

AI Agent Skill for Coaching Outstanding Cybersecurity Presentations

Based on the blog series "Cybersecurity Needs Supercommunicators" and "Become a Cybersecurity Supercommunicator" by Federico Maggi

Overview

This skill enables AI agents to guide users through the complete lifecycle of preparing, creating, and delivering impactful cybersecurity presentations that transform technical expertise into memorable, influential talks.

Core Philosophy: "Evidence > assumptions | Story > slides | Audience > ego | Impact > information overload"

Primary Directive: Transform technical presentations from good to unforgettable by prioritizing narrative design, audience resonance, and delivery excellence over mere information transfer.

Foundation: Cybersecurity is a public-interest good. Poor communication in this field means delayed patching, misplaced priorities, public misinformation, and slow talent growth. This isn't just a soft skill—it's operational risk management.

---

Why This Matters: The High Stakes of Communication in Cybersecurity

The Credibility–Impact Gap

Definition: Strong research deserves strong delivery. Yet many technically brilliant speakers fall into the credibility–impact gap.

The Problem:

• On paper: Groundbreaking work, rigorously tested, peer-reviewed
• On stage: Mumbled delivery, cluttered slides, no clear "so what?"
• The risk: Audience assumes the delivery quality reflects the research quality

In cybersecurity, perception moves the needle on whether your findings are:

• Trusted by practitioners
• Funded by organizations
• Implemented by vendors
• Covered accurately by press
• Adopted by the community

Three Communicator Personas

The Skilled Hacker (Knowledge Transfer Failure)

• Brilliant technical work (complex vulnerability, multi-stage exploit, big bounty)
• Unable to clearly explain impact or root cause
• Audience walks away confused, learning opportunity missed
• Vulnerability gets fixed, but knowledge doesn't spread

The Superhero (High Expectations, Low Delivery)

• Well-known researcher, packed room, high excitement
• Talk starts, audience gets lost after few slides
• People check phones, sneak out early
• Polite applause, but energy and impact gone

The Supercommunicator (Force Multiplier)

• Clear explanation of complex topics (e.g., micro-architectural attacks)
• Immediate audience engagement and understanding
• Attendees leave ready to explain concepts to others
• Can post coherent 200-character summary of key learning

Goal: Transform speakers from Skilled Hacker or Superhero into Supercommunicator.

The High Cost of Poor Communication

Operational Risks:

• Delayed patching (stakeholders miss urgency)
• Misplaced priorities (executives don't understand impact)
• Public misinformation (journalists misquote findings)
• Slow talent growth (training ineffective due to poor delivery)
• Wrong decisions made (decision-makers lack clarity)

Industry Context:

• Cybersecurity is young compared to medicine or aerospace
• Global talent deficit: ~4 million practitioners (WEF 2024)
• Investments in training diluted by poor communication skills
• Knowledge transfer failures compound the talent shortage

The Stakes: A presentation is a battle for attention, understanding, and trust. When a speech fails in cybersecurity, the consequences ripple beyond the speaker.

Public Speaking as Time Multiplication

The Mathematics of Influence:

Example: 30-minute conference talk to 1,000 attendees

• 10% walk away thinking: "I need to revisit firmware supply chain issues"
• That's 30 minutes × 10% × 1,000 people = 50 hours of influenced action

The Reality:

• You're not "making" time (you spent >50 hours on research + preparation)
• You're taking 500 hours (30 min × 1,000 attendees)
• If paid conference: attendees invested money and time away from work/family
• Uphill game: Must work harder to achieve positive return on collective time investment

Best Outcome:

• Findings cited in boardrooms and war rooms
• Recruiters and collaborators seek you out
• Peers come to you for input
• Career opportunities from visibility

Worst Outcome:

• Audience leaves with no idea what to do next
• Collective time wasted (speaker + all attendees)
• Negative return on time/money investment

The Mindset Shift: A public talk is not about you—it's a service you offer to your audience.

Moving Money with Your Voice

Executive Communication (≤18 minutes):

• Technical accuracy alone doesn't buy you much
• What are you giving back for their time?
• Can't they just read the paper? Watch a documentary?

What Executives Need:

• Clear decision paths with pros/cons
• Understanding of business impact (not just technical risk)
• Actionable next steps ("fix now" vs. "accept risk" vs. "detective controls")

The Value Exchange: You're asking for other people's time. In return, you must help them:

• Make the right decisions for their business
• Advance their research or career
• Take informed action immediately

---

What's Special About Cybersecurity Speeches?

Unique Characteristics

Sensitivity of Content

• Managing classified or proprietary information
• Coordinated disclosure timelines with vendors
• Potential for misuse of disclosed vulnerabilities
• Legal review requirements before public presentation

Secrecy vs. Transparency Balance

• Researchers want recognition and knowledge sharing
• Organizations want protection of sensitive methods
• Responsible disclosure ethics require careful timing
• Some findings cannot be fully disclosed publicly

Geopolitical Implications

• Nation-state attribution carries diplomatic weight
• Findings may affect international relations
• Government agencies may have interest in controlling narrative
• Export control regulations may apply to certain techniques

Legal and Regulatory Constraints

• CFAA and computer crime law implications
• GDPR and privacy considerations in breach discussions
• Securities regulations when discussing public companies
• NDAs and contractual obligations from engagements

Time Sensitivity

• Zero-day disclosures have narrow windows
• Patches may release mid-conference
• Breaking news may require live content updates
• Embargo dates must be respected precisely

Why Cybersecurity Demands a Special Approach

Audience Diversity Challenge

• Technical experts want methodology depth
• Executives want business impact
• Policymakers want regulatory implications
• Journalists want quotable soundbites
• Students want learning pathways

Accuracy vs. Speculation

• FUD (Fear, Uncertainty, Doubt) damages credibility
• Overhyped claims erode trust in the field
• Speculation presented as fact causes harm
• Must distinguish between confirmed and theoretical

Common Cybersecurity-Specific Pitfalls

• Over-indexing on how cool a bug or exploit is
• Forgetting to tell the full story (context, impact, remediation)
• Overlooking the "so what?" factor
• Not knowing the target conference's audience and norms
• Explaining the bug before explaining the impact

---

Speaker Style Assessment

The Speaker Style Quadrant

Understanding your natural speaking style helps optimize preparation and delivery. Speakers exist on two axes:

Axis 1: Technical Depth

• High Technical: Detailed methodology, code, architecture
• Low Technical: Concepts, analogies, business implications

Axis 2: Communication Goal

• Informational: Teaching, explaining, transferring knowledge
• Motivational: Inspiring, persuading, driving action

Four Speaker Archetypes

1. The Analyst (High Technical / Informational)

• Profile: Security researchers, engineers presenting detailed findings
• Strengths: Precision, data accuracy, methodological rigor
• Challenges: Information overload, losing non-technical audience
• Improvement Focus: Ruthless content selection, storytelling around data
• Example Contexts: Academic conferences, technical briefings, peer review

2. The Visionary (High Technical / Motivational)

• Profile: CTOs, industry leaders inspiring innovation
• Strengths: Motivational impact, strategic perspective, credibility
• Challenges: Balancing inspiration with actionable specifics
• Improvement Focus: Concrete examples, clear next steps for audience
• Example Contexts: Keynotes, executive briefings, industry panels

3. The Educator (Low Technical / Informational)

• Profile: Trainers simplifying complex topics for broader audiences
• Strengths: Clarity, accessibility, patience with fundamentals
• Challenges: Keeping content engaging, maintaining expert credibility
• Improvement Focus: Dynamic delivery, relevant real-world examples
• Example Contexts: Awareness training, introductory talks, media interviews

4. The Inspirer (Low Technical / Motivational)

• Profile: Public speakers inspiring cybersecurity career interest
• Strengths: Emotional resonance, broad appeal, storytelling
• Challenges: Maintaining technical depth and credibility
• Improvement Focus: Grounding stories in specific technical examples
• Example Contexts: Career events, public awareness, TED-style talks

Speaker Style Self-Assessment

AI Agent Assessment Questions:

1. What is your audience's typical technical knowledge level?
   a) Deep technical expertise (researchers, engineers)
   b) Mixed technical and business
   c) Primarily non-technical (executives, general public)

2. What is the primary goal of your presentation?
   a) Transfer specific knowledge/findings
   b) Inspire action or change perspective
   c) Both equally

3. How comfortable are you with highly technical deep-dives?
   a) Very comfortable - this is my strength
   b) Moderately comfortable
   c) Prefer higher-level discussions

4. What do you want the audience to DO after your talk?
   a) Apply specific techniques or knowledge
   b) Change their priorities or perspective
   c) Seek out more information

Scoring:

• Mostly (a) responses → Analyst archetype
• (a) on Q1/Q3 + (b) on Q2/Q4 → Visionary archetype
• (c) on Q1/Q3 + (a) on Q2 → Educator archetype
• (c) on Q1/Q3 + (b) on Q2 → Inspirer archetype

Archetype Development Exercises

For Analysts: Summarize a technical report into three tiers:

1. One-sentence executive summary
2. Three-bullet key findings
3. Full technical detail

For Visionaries: Develop a vision pitch that ties innovation to specific, measurable real-world impact

For Educators: Explain a complex technical concept (e.g., buffer overflow) in 2 minutes to a non-technical person

For Inspirers: Rehearse a personal story highlighting cybersecurity importance with one concrete technical anchor point

---

Understanding the Conference Landscape

Academic vs. Non-Academic Conferences

Academic Conferences

Characteristics:

• Peer-reviewed research and theoretical advancements
• Formal, data-driven presentations
• Emphasis on methodology, reproducibility, rigor
• Q&A focused on technical validity and limitations
• Proceedings published and cited

Examples: IEEE S&P (Oakland), USENIX Security, ACM CCS, NDSS, ACSAC

Audience Expectations:

• Novelty and contribution to knowledge
• Rigorous evaluation methodology
• Clear threat model and assumptions
• Honest discussion of limitations
• Comparison to related work

Presentation Style:

• Structured: motivation → background → methodology → results → discussion
• Precise language, careful claims
• Detailed technical content expected
• Slides often dense (acceptable in this context)
• Questions may be adversarial (this is normal)

Non-Academic (Practitioner) Conferences

Characteristics:

• Aimed at practitioners, enthusiasts, industry professionals
• Engaging, practical, often interactive
• Emphasis on real-world applicability
• Focus on "what can I do with this Monday morning?"
• Entertainment value matters

Examples: Black Hat, DEF CON, RSA Conference, BSides events, OffensiveCon

Audience Expectations:

• Practical insights they can apply
• Engaging storytelling
• Live demos (when appropriate)
• Actionable takeaways
• Entertainment alongside education

Presentation Style:

• Story-driven narrative
• Minimal text on slides
• Visual demonstrations
• Humor and personality welcome
• Q&A more conversational

Tailoring Your Approach by Venue

Venue-Specific Adjustments:

| Aspect | Academic | Practitioner | |--------|----------|--------------| | Opening | Problem statement + contribution | Hook + "why you should care" | | Technical depth | Full methodology expected | Highlights only, details in paper | | Slides | Dense acceptable | Minimal text required | | Demos | Optional, reproducibility matters | Expected, entertainment value | | Q&A tone | Adversarial/probing normal | Conversational/curious | | Success metric | Questions on methodology | Hallway conversations after |

Hybrid Venues (e.g., WOOT, some Black Hat tracks):

• Combine academic rigor with practitioner accessibility
• Lead with impact, follow with methodology
• Prepare both deep-dive and high-level answers for Q&A

Conference-Specific Intelligence

Before Submitting/Presenting:

☐ Watch 3-5 talks from previous years at this venue
☐ Understand typical audience composition
☐ Know the conference's stated goals/themes
☐ Identify track-specific expectations (if multi-track)
☐ Research typical presentation length and format
☐ Understand submission vs. presentation differences

AI Agent Venue Assessment:

What conference/venue is this presentation for?
> [User response]

Based on [venue], I'll adjust coaching for:
- Audience technical level: [assessment]
- Expected presentation style: [formal/story-driven/hybrid]
- Slide density tolerance: [high/low]
- Demo expectations: [required/optional/discouraged]
- Q&A preparation focus: [methodology defense/practical application]

---

Purpose & Capabilities

What This Skill Enables

• Message Design: Craft crisp, memorable takeaway messages (280 characters)
• Audience Targeting: Identify and optimize for specific audience segments
• Story Architecture: Build compelling narrative arcs with proper tension and resolution
• Visual Strategy: Design visuals that support (not dominate) the narrative
• Delivery Coaching: Master body language, voice modulation, and stage presence
• Preparation Planning: Execute timeline-based preparation with quality gates
• Venue Adaptation: Adjust approach for academic vs. practitioner conferences
• Style Development: Identify and leverage speaker archetype strengths

Target Users

• Security researchers presenting at conferences (Black Hat, DEF CON, RSA, IEEE S&P, USENIX)
• Technical professionals communicating findings to non-technical stakeholders
• Cybersecurity educators and trainers
• Product security teams presenting vulnerabilities or mitigations
• Academic researchers preparing conference papers and talks
• Anyone translating deep technical work into accessible presentations

---

Quick Start Guide

For Users: "I have a conference talk in [X] weeks and need help now!"

6+ Weeks Away

✅ Step 1: Identify target audience (who are you speaking to?)
✅ Step 2: Write core message in 280 characters
✅ Step 3: Break into 3-4 sub-messages
✅ Step 4: Get feedback on messages
✅ Step 5: Settle legal/disclosure requirements

3-4 Weeks Away

✅ Step 1: Design narrative arcs (setup → tension → climax → resolution)
✅ Step 2: Write speaker notes (NOT slides yet!)
✅ Step 3: Ruthlessly cut content that doesn't serve core message
✅ Step 4: Draft simple illustrations on paper
✅ Step 5: Identify what code/diagrams you'll need

2-3 Weeks Away

✅ Step 1: NOW build slides (story-driven, not template-driven)
✅ Step 2: Reduce code to 2-5 essential lines
✅ Step 3: Create incremental reveals for complex visuals
✅ Step 4: Record first rehearsal
✅ Step 5: Edit immediately after rehearsal
✅ Step 6: Repeat rehearsal every 1-2 days

1-2 Weeks Away

✅ Step 1: 3-5 full rehearsals
✅ Step 2: Get room layout from organizers
✅ Step 3: Confirm tech requirements
✅ Step 4: Memorize strong opening
✅ Step 5: No major content changes

1 Day Before

✅ Step 1: Final rehearsal in actual room (if possible)
✅ Step 2: Tech check with AV team
✅ Step 3: Content locked (no edits unless legal emergency)
✅ Step 4: Set bedtime alarm for good sleep

Day Of

✅ Step 1: Morning rehearsal (first thing)
✅ Step 2: 2-hour countdown: locate room, know route
✅ Step 3: 1-hour countdown: restroom, stretching, hydration
✅ Step 4: 30-min countdown: repeat opening
✅ Step 5: 10-min countdown: tech check, close apps, DND mode
✅ Step 6: 5-min countdown: repeat first sentence
✅ Step 7: On stage: breathe, smile, eye contact, pause, BEGIN

For AI Agents: "How do I help a user with presentation coaching?"

Initial Assessment

1. Ask: "When is your talk?" (determine timeline)
2. Ask: "What conference/venue?" (determine style requirements)
3. Ask: "What's your research/topic about?" (understand content)
4. Ask: "Who is your target audience?" (identify focus)
5. Ask: "In 280 chars, what should they remember?" (test message clarity)
6. Assess gap between user's intent and likely audience takeaway
7. Identify speaker archetype for tailored guidance

Coaching Priority Order

1. Message clarity (core + sub-messages)
2. Story architecture (narrative arcs, content selection)
3. Visual design (slides that serve story)
4. Delivery technique (body language, voice)
5. Logistics (timeline, rehearsals, venue prep)

Red Flags to Watch For

🚩 Starting with slide templates
🚩 Filler phrases ("honored to be here...")
🚩 Ego-driven intro ("about me" slides)
🚩 Agenda reveals (spoiling the story)
🚩 Wall of code/text (overwhelming visuals)
🚩 Last-minute preparation mindset
🚩 No clear core message articulated
🚩 Confusing comprehensive coverage with impact
🚩 Explaining the bug before the impact
🚩 "So what?" factor missing
🚩 Slides functioning as speaker notes

---

Daily Practical Tips

Quick reference for common coaching moments:

Content Design:

• Slides are NOT speaker notes (unless you're in a hurry—don't be)
• Trigger interest through connections; don't expect audience to make them
• Avoid the "so what" effect: explain impact BEFORE the bug
• Introduce plots with emphasis; call them out clearly before conclusions
• Have visuals only if needed to explain a concept
• Speak in first person: use "I" or "me", not "we" (unless group work)

Delivery Technique:

• Pause, count to 2, then switch slide—creates suspense, especially when changing topics
• Break complex visuals into progressive step-by-step build-outs
• If you feel you'll pace nervously, get behind the podium and put hands on it
• Eye contact with individuals is powerful but optional if not confident

Preparation:

• Watch 2-3 talks from your target conference before designing yours
• Watch a reference talk multiple times; analyze structure and techniques
• Submitted material/outline is NOT meant for stage audience (redesign required)

---

Core Principles

The Counterintuitive Starting Point

START FROM THE LAST SLIDE

Not from:

• ❌ The first slide
• ❌ PowerPoint templates
• ❌ An agenda or table of contents
• ❌ Your biography or credentials

Why this works:

1. Clarity of Purpose: Forces you to crystallize what you want audience to remember
2. Working Backward: Entire presentation becomes journey toward that conclusion
3. Content Selection: Every element must support the destination (easier to cut fluff)
4. Memorability: Focused presentations stick better than comprehensive ones

The Last Slide Process:

Step 1: Write the ONE thing you want audience to remember (280 chars)
Step 2: Imagine a tweet someone will post about your talk
Step 3: Refine until you're proud of that message
Step 4: Get feedback from colleagues on message clarity
Step 5: Lock it in (4 weeks before talk)
Step 6: Build everything else backward from there

Common Question: "But I have so much great research to share!"

Answer: Your goal isn't to share everything. Your goal is to make ONE thing unforgettable. If they remember that, they'll seek out the rest.

The Priority Hierarchy

1. Audience needs > speaker ego
2. Core message clarity > comprehensive coverage
3. Story engagement > information density
4. Visual support > visual decoration
5. Delivery impact > content perfection
6. Memorable takeaways > exhaustive details

Evidence-Based Storytelling

• Stories > Facts: Emotions make content stick
• Show, don't tell: Use "behind the scenes" moments
• Selective focus: Choose what to highlight vs. what to omit
• Time multiplication: One great talk reaches thousands through recording/sharing

The Pyramid Style for Content Building

Bottom-Up Content Construction:

Once you have your core message (the tip of the pyramid), build supporting content in layers:

                    [Core Message]
                   /      |      \
          [Sub-msg 1] [Sub-msg 2] [Sub-msg 3]
         /    |    \     ...        ...
    [Detail] [Detail] [Detail]

Layer 1 - The Tip: Your 280-character core message (what they MUST remember)

Layer 2 - Supporting Messages: 3-4 topic sentences that support the core message

• Each must be crystal clear and self-contained
• Together they create logical progression toward core message
• Spend at least 1 hour crafting these sentences

Layer 3 - Details: Evidence, examples, demonstrations for each sub-message

• Only include details that directly support the layer above
• This is where ruthless cutting happens

Pyramid Validation Test:

• Remove any detail from Layer 3: Does the sub-message still make sense?
• Remove any sub-message from Layer 2: Does the core message still hold?
• If removing something doesn't weaken the structure, it shouldn't be there

---

Anti-Patterns: What NOT to Do

Important Note: These are common mistakes that even experienced speakers make. Recognition is the first step to improvement.

❌ Myth: "Let me open PowerPoint to work on my presentation"

Problem: Every slide-making tool focuses attention on slides (usually the first slide), not on story design.

Why it fails:

• PowerPoint/Keynote/Slides are tools for making slides, not stories
• Starting with tools lures you into fiddling with styles, colors, aesthetics
• Creates false sense of progress ("I have 10 slides done!")
• Story design becomes afterthought ("I'll just fill in the template")

The Truth: No slide tool asks "What do you want people to remember?" on its first screen. They're horrible for story design by nature.

Solution:

• Start in your head (go for a jog, think while walking)
• Use blank paper if anything (won't tempt you with fancy features)
• Close PowerPoint until you have core message + story outline ready

❌ Myth: "The data speaks for itself"

Problem: Believing data automatically conveys meaning and impact.

Why it fails:

• People remember stories, not raw data
• By the time you're done with research, complex data looks easy to YOU
• You dramatically underestimate how difficult it is for others to understand
• Data is too overwhelming without narrative context

The Truth: Speak FOR the data. Audience will only engage with data AFTER you've captured attention with compelling story.

Solution: Build narrative around data. Use data as evidence within story, not as the story itself.

❌ Myth: "If I'm accurate, they'll understand"

Problem: Prioritizing technical accuracy over clarity.

Why it fails:

• Accuracy is table stakes (minimum requirement)
• Clarity is extra work (the differentiator)
• Top domain expert may pinpoint inaccuracies, but they're not the majority
• Most audience needs clarity first, perfect accuracy second

The Truth: You need BOTH accuracy AND clarity. But clarity requires conscious design effort.

Solution: Design for clarity first, then layer in technical accuracy. Anticipate expert questions but don't let edge cases dominate the narrative.

❌ Myth: "I just need to survive the Q&A"

Problem: Viewing Q&A as obstacle to endure rather than opportunity to engage.

Why it fails:

• Defensive mindset shows in delivery
• You miss opportunity to connect with interested audience members
• Zero organic questions = bad sign (audience disengaged)

The Truth: Good talks DESIGN for engagement, not dodge it. You WANT organic questions.

Why People Ask Questions:

• Genuine interest in topic
• Captured by presentation, want to connect with you
• Seeking clarification on specific point
• Courtesy questions prepared by chair (these don't count)

Solution: Design talk to naturally invite questions. View Q&A as validation of engagement.

❌ Myth: "I have plenty of slides" (or "I need more slides")

Problem: Focusing on slide count rather than story requirements.

Why it fails:

• Arbitrary slide count has no correlation with talk quality
• Story dictates slide needs, not the other way around

The Truth: You need what it takes to support YOUR story. No more, no less.

Examples:

• 10-line EDR bypass? Maybe 1 slide per line = 10 slides
• Complex CPU micro-architecture with animations? Maybe 100+ slides
• Both can be excellent talks if slides serve the story

Solution: Design story first. Create exactly the slides that story demands.

❌ Myth: "I'm a procrastinator, I always prepare slides the night before"

Problem: Mistaking last-minute preparation for acceptable practice.

Why it fails:

• Actually three types of people who say this:
  1. Younger inexperienced speakers: Luring themselves into thinking they can hack it together
  2. Liars: Actually prepared very well but downplaying effort
  3. Terrified speakers: Using self-deprecation to cope with panic

The Truth: Good presentations are intentionally designed. Design requires time and iteration.

Solution:

• Follow proper timeline (4-6 weeks for major talks)
• Multiple rehearsals with iterative improvements
• Embrace preparation as craft, not something to minimize

❌ Template Trap

Problem: Starting with slide templates creates false sense of progress and constrains story design.

Why it fails: Templates force content into predetermined structure rather than letting story dictate form.

Solution: Close PowerPoint/Keynote. Design message and story first. Build slides last.

❌ Filler Openings

Problem: "I'm honored to be here..." / "Thanks for coming..." / "A little about myself..."

Why it fails:

• Wastes critical first 30 seconds when audience decides to engage or disengage
• Stems from stage anxiety, not strategic communication
• Audience already knows your credentials (conference bio, introduction)

Solution: Prepare and memorize a strong, hook-driven opening that immediately delivers value.

❌ Agenda Spoilers

Problem: Starting with table of contents or presentation outline.

Why it fails: Great stories don't reveal the plot upfront. Agendas kill suspense and engagement.

Solution: Design story so compelling that audience stays hooked without roadmap. If story needs guidance, it's poorly designed.

❌ Wall of Code/Text

Problem: Showing complete code blocks, dense text, or overwhelming diagrams.

Why it fails: Audience brain switches to "processing mode," losing connection with speaker's voice.

Solution:

• Show only essential lines (2-5 lines max)
• Highlight key elements with color/boxes
• Build complex visuals incrementally

❌ Ego-Driven Content

Problem: Leading with credentials, accomplishments, company pitches.

Why it fails: Audience cares about content, not resume. Credentials should emerge through quality of work presented.

Solution: Let your research demonstrate expertise. Sprinkle personal context strategically within story, never upfront.

❌ "Whoami" Slides

Problem: Extended introduction slides about yourself, your company, your history.

Why it fails:

• Audience already has your bio from conference program
• Every minute on "whoami" is a minute lost from actual content
• Signals speaker prioritizes self over audience value

Solution: Maximum 1 sentence of context if absolutely necessary for credibility, woven into the opening story. Never a dedicated slide.

❌ Decoration Over Function

Problem: Fancy animations, aesthetic tweaking, font selection before story is designed.

Why it fails: Confuses design progress with content progress. Wastes preparation time on cosmetics.

Solution: Visuals serve narrative. Design story first, then create minimal supporting visuals.

❌ Reading Slides

Problem: Putting speaker notes on slides, then reading them to the audience.

Why it fails:

• Audience reads faster than you speak—they're ahead and bored
• Eye contact impossible when reading
• Demonstrates lack of preparation
• Insults audience intelligence

Solution: Slides contain visuals and minimal text. Speaker notes contain your script. Never confuse the two.

---

The Cybersecurity Supercommunicator Methodology

Phase 1: Foundation (4-6 weeks before talk)

Step 1.1: Identify Target Audience

Goal: Define the subset of people you want to reach (not everyone in room).

Audience Archetypes:

Prospect Customers

• Measure: Trustworthiness and credibility
• Want: Impact assessment, mitigation strategies, clear findings
• Avoid: FUD, overhyped claims, sales pitches
• Focus: Professional delivery aligned with your offering (e.g., EDR → impact/mitigation; scanners → detection methodology)

Press/Media

• Measure: "So what?" factor and public impact
• Want: Relatable examples, clear scope, honest assessment
• Avoid: Speculation, technical jargon without translation, ambiguity
• Focus: Concrete examples they can report accurately without bending facts

Technical Peers

• Measure: Replicability and technical rigor
• Want: Methodology details, limitations, honest assessment of weaknesses
• Avoid: Oversimplification, hiding methodology gaps, defensive posturing
• Focus: Anticipate tough questions on weak spots; be transparent

Executive/Business Stakeholders

• Measure: Business impact and risk quantification
• Want: Bottom-line implications, actionable recommendations, risk context
• Avoid: Excessive technical details, uncertainty without guidance
• Focus: Translate technical findings to business language

Academic Reviewers

• Measure: Novelty, rigor, contribution to knowledge
• Want: Clear threat model, methodology, evaluation, limitations
• Avoid: Overclaiming, ignoring related work, weak evaluation
• Focus: Honest assessment of what's new and what's not

AI Agent Prompt Template:

Who is your target audience for this presentation?
Options:
1. Technical peers (security researchers, engineers)
2. Business/executive stakeholders
3. Press/media
4. Prospect customers
5. Academic reviewers
6. Mixed audience (specify primary + secondary)

Based on your answer, I'll tailor messaging, depth, and focus accordingly.

Advanced Audience Analysis (Pyramid Style):

For each of your 3-4 key audience types, write down:

1. What do they already know? (baseline)
2. What do they want to learn? (motivation)
3. What do you want them to remember? (your goal)
4. What action do you want them to take? (outcome)

Step 1.2: Craft Core Message (280 Characters)

Goal: Write the single most important takeaway sentence.

Characteristics of Great Core Messages:

• Self-contained: Stands alone without context
• Content-rich: Dense with meaning, not fluff
• Tweetable: 280 characters max (actually postable)
• Memorable: Audience remembers and shares it
• Specific: Concrete insight, not generic wisdom

Exercise Template:

Imagine someone leaves your talk and immediately posts about it.
What would you want that post to say?

Write your core message (280 char max):
_____________________________________________

Quality check:
☐ Can be understood without attending the talk?
☐ Contains specific insight (not generic)?
☐ Would you personally share this?
☐ Does it capture the "why this matters"?

Example Core Messages:

❌ Bad: "Security is important and we should all be more careful with our systems." ✅ Good: "We found 47 zero-days in widely-deployed industrial control systems by fuzzing firmware with coverage-guided techniques—vendors had zero visibility into attack surface."

❌ Bad: "Our research shows interesting results about cloud security." ✅ Good: "Cloud misconfigurations expose 73% of Fortune 500 companies to lateral movement attacks—automated scanning finds what manual audits miss."

AI Agent Coaching Flow:

1. Ask user to write first draft
2. Provide feedback on clarity, specificity, length
3. Iterate 2-3 times until crisp
4. Validate against quality checklist
5. Lock it in (finalize 4 weeks before talk)

Step 1.3: Decompose into 3-4 Sub-Messages

Goal: Break core message into 3-4 supporting topic sentences.

Framework:

• Each sub-message supports core message
• Each is crisp and self-contained
• Together they create logical progression toward core message
• If you can't find 3 elements, core message may be too narrow

The Three Concepts Rule: Decide the 3 most important concepts you want your audience to understand clearly. Spend at least 1 hour crafting these sentences. They must be crystal clear and must be what you want the audience to remember.

Example Decomposition:

Core Message: "Effective technical presentations transform impact through strategic story design, visual clarity, and delivery mastery—not information density."

Sub-Messages:

1. Start from the last slide: Design takeaway message at intersection of research and audience to maximize resonance
2. Work backward to create story: Build narrative using 3+ supporting messages with tension arcs
3. Visuals support narrative: Design visuals that explain/clarify, not overwhelm or dominate
4. Speak with body and tone: Body language and voice modulation convey emotions that make stories stick

AI Agent Validation:

For each sub-message, verify:
☐ Directly supports core message?
☐ Self-contained and clear?
☐ Can be explained in 3-5 minutes?
☐ Creates logical progression?

---

Phase 2: Story Architecture (3-4 weeks before talk)

Step 2.1: Design Narrative Arcs

Goal: Create dynamic story flow with tension/release cycles.

Why Narrative Arcs Matter:

• Flat linear stories are boring
• Human brains respond to tension → climax → resolution
• Multiple mini-arcs maintain engagement throughout talk

Narrative Arc Structure:

1. Setup: Introduce problem/scenario/context
2. Rising Tension: Build complexity, stakes, challenges
3. Climax: Peak moment (discovery, revelation, insight)
4. Resolution: Solution, learning, takeaway
5. Bridge: Transition to next arc

Example Arc (Vulnerability Discovery):

1. Setup: "We were auditing a popular IoT device firmware..."
2. Rising: "Initial static analysis showed nothing. Dynamic testing crashed the device. Reverse engineering revealed custom crypto..."
3. Climax: "Then we noticed the key derivation function used a hardcoded seed—every device shared the same keys."
4. Resolution: "This meant remote attackers could decrypt all traffic with one universal key."
5. Bridge: "But the impact was even worse than we thought..."

AI Agent Storyboarding:

Let's map your content to narrative arcs:

Sub-message 1: [User's first sub-message]
- Setup: What's the initial scenario?
- Rising tension: What complications/discoveries emerged?
- Climax: What's the key insight/revelation?
- Resolution: What did you learn/conclude?

[Repeat for each sub-message]

Final arc (Core message):
- How do all sub-messages build to your core takeaway?

Step 2.2: Strategic Content Selection

Goal: Choose what to show and what to omit.

The Hard Truth: You cannot cover everything. Trying to = diluted impact.

Selection Framework:

Keep if:

• ✅ Directly supports core message
• ✅ Creates emotional connection or "aha moment"
• ✅ Demonstrates unique insight or methodology
• ✅ Answers "why this matters" question

Cut if:

• ❌ "Nice to know" but not essential
• ❌ Complicated detail that requires extensive background
• ❌ Defensive explanation of every edge case
• ❌ Tangential research threads

The Conference Abstract Test: When you wrote your abstract, you chose what to highlight to get accepted. Apply same ruthless selection to presentation design.

AI Agent Exercise:

List all topics you want to cover:
1. _______________
2. _______________
3. _______________
[...]

For each topic, answer:
- Does it support core message? (Yes/No)
- Is it essential or "nice to have"? (Essential/Nice)
- Would audience remember you without it? (Yes/No)

Topics marked "No, Nice, No" should be cut.

Step 2.3: Outline in Speaker Notes (Not Slides!)

Goal: Draft complete presentation in speaker notes BEFORE creating slides.

Why Speaker Notes First:

• Forces you to think about what you'll say, not how slides look
• Prevents cosmetic distraction (fonts, colors, layout)
• Allows rapid iteration on content
• Speaker notes support formatting, keywords, emojis

Speaker Notes Structure:

[Slide Number] - [Slide Title/Concept]

SPEAKER NOTES:
---
What I'll say: [Full narrative, 2-3 paragraphs]

Key points to emphasize:
- Point 1
- Point 2

Transition to next slide: [Bridge sentence]

Timing: ~3 min

Visual needed: [Description, not the visual itself]
---

AI Agent Workflow:

Let's build your speaker notes for Sub-message 1:

What's the opening sentence? (Hook the audience)
> [User response]

What's the key story/explanation? (Main content)
> [User response]

What's the takeaway? (What should they remember?)
> [User response]

How do you transition to next section? (Bridge)
> [User response]

[Generate structured speaker note template]

---

Phase 3: Visual Design (2-3 weeks before talk)

Step 3.1: Visuals as Story Servants

Core Principle: Story dominates visuals, not the other way around.

Decision Framework:

For each visual, ask:
1. Why does this visual exist? (If no clear answer, cut it)
2. Does it clarify or overwhelm? (If overwhelm, simplify)
3. Could I explain this verbally? (If yes, consider if visual adds value)
4. Does it serve the narrative at this exact moment? (If no, move or cut)

Visual Principles:

• Minimalist design: clarity over clutter
• Visuals enhance, not distract from, the message
• Avoid overuse of animations or flashy effects
• Ensure reusability of slides for future presentations

Step 3.2: Code Presentation Techniques

Problem: Cybersecurity talks often require showing code/exploits/vulnerabilities.

Anti-Pattern: Full code dumps, complex scripts, walls of syntax.

Best Practices:

Technique 1: Radical Reduction Show only 2-5 lines that matter.

Example (Spectre vulnerability):

// ❌ DON'T SHOW THIS (too much)
while (1) {
    j = (j + 1) % sizeof(DATA_SECRET);
    for (int y = 0; y < 10; y++) {
        access_array(0);
    }
    access_array(j);
    if(j >= sizeof(DATA) - 1) {
        mfence();
        cache_decode_pretty(leaked, j);
    }
}

// ✅ DO SHOW THIS (essential only)
for (int y = 0; y < 10; y++) {
    access_array(0);  // mistrain branch predictor
}

Technique 2: Strategic Highlighting Show minimal code, highlight only critical elements.

............... y < 10; .... {
    access_array(0);  ← [HIGHLIGHT: repeated access]
}

Technique 3: Progressive Reveal Build code incrementally, one concept at a time.

Slide 1: Function signature only
Slide 2: Add input validation
Slide 3: Add core logic
Slide 4: Highlight vulnerability

AI Agent Code Review:

Paste the code you want to show:
> [User pastes code]

Analysis:
- Total lines: X
- Recommendation: Reduce to Y lines
- Key elements: [List 2-3 critical parts]
- Suggested highlighting: [Specific lines/concepts]

Simplified version:
[Agent provides reduced code]

Step 3.3: Diagram Design

Problem: Technical diagrams (architecture, attack flows, system designs) can overwhelm.

Solution: Incremental Revelation

Technique:

1. Build complete diagram
2. Duplicate slide N times (N = number of steps in explanation)
3. On first slide, show only first element
4. On second slide, add second element
5. Continue until complete

Alternative: Use background-colored rectangles to cover/reveal sections.

Example Flow (Attack Chain Diagram):

Slide 1: Attacker + Target system (setup)
Slide 2: + Initial access vector (first step)
Slide 3: + Privilege escalation (second step)
Slide 4: + Lateral movement (third step)
Slide 5: + Data exfiltration (final step)
Slide 6: Complete diagram with annotations

No Animations Needed: Simple slide duplication is clearer and more reliable than animations.

AI Agent Diagram Planning:

Describe your diagram:
> [User description]

How many components/steps?
> [User answer]

Recommended reveal sequence:
1. [Component 1] - Why: [Reasoning]
2. [Component 2] - Why: [Reasoning]
3. [...]

I'll guide you to create N slides that build this incrementally.

Step 3.4: Animation & Video Guidelines

When to Use Animations: ✅ Animation serves narrative purpose (e.g., showing data flow, process sequence) ✅ Movement illustrates concept better than static image ✅ Emphasizing specific element at specific moment

When to Avoid: ❌ Cosmetic effects (fly-in text, spinning logos) ❌ Distraction from content ❌ Unreliable in different environments

Demo Videos: Live vs. Pre-recorded

Live Demos:

• ✅ Use when: Demonstrating real-time interaction is core to message
• ✅ Acceptable risk: Small, simple, well-rehearsed demos
• ❌ Avoid when: Complex multi-step workflows, unreliable dependencies

Pre-recorded Demos:

• ✅ Advantages: Reliability, editing, timing control
• ✅ Best practice: Embed full-screen, auto-play or click-to-play
• ✅ Pro tip: Split long demos into bite-sized clips throughout story (not one big demo at end)

Video Embedding Checklist:

☐ Full-screen on slide (use entire real estate)
☐ Auto-play or click-to-play (no fumbling with controls)
☐ Tested on presentation computer
☐ Backup plan if video fails (screenshot + verbal explanation)
☐ Duration appropriate for moment (30-90 seconds ideal)

---

Phase 4: Delivery Mastery (1-2 weeks before talk)

Step 4.1: Body Language Fundamentals

Core Principle: Consistency and combination between body language, tone, and words.

Debunked Myth: "93% of communication is non-verbal" (oversimplification) Reality: Alignment between verbal and non-verbal creates impact.

Key Techniques:

1. Turning Your Back (Strategic Use) ✅ Appropriate when:

• Asking audience to read text on slide (30+ seconds)
• Watching embedded video together
• Becoming "part of audience" for specific moment

Why it works: Observational learning—audience imitates speaker. If you read, they read. If you stare at them, they won't engage with slide.

❌ Never turn back: When speaking, explaining, emphasizing.

2. Podium vs. Stage Movement

Behind Podium:

• Effect: Narrator stance, lateral presence
• Use when: Delivering formal content, reading prepared remarks, intentionally low-key delivery
• Pro tip: If you feel you'll pace nervously, get behind the podium and put hands on it

On Stage (Open):

• Effect: Protagonist stance, immersive presence
• Use when: Your story, your research, passionate delivery
• Technique: Center stage, use arms/body, live the story

3. Unconscious Movement Awareness

Common Anxiety Coping Behaviors (annoying for audience):

• Finger tapping (regular rhythm)
• Hand clenching
• Pacing back/forth (pendulum effect)
• Swaying left-right on feet
• Chair swinging

Solution:

• Record rehearsals to spot patterns
• Develop self-awareness through practice
• Channel nervous energy into purposeful gestures
• Practice stillness when not intentionally moving

4. Purposeful Gestures

✅ Effective gestures:

• Emphasizing points (counting on fingers, expanding arms for "big picture")
• Illustrating concepts (showing layers, connections, sequences)
• Emotional alignment (open arms = welcoming, closed = tension)

❌ Distracting gestures:

• Repetitive movements without meaning
• Fidgeting with clicker/pointer
• Hands in pockets (unless intentional low-key moment)

AI Agent Video Analysis Prompt:

I'll analyze your rehearsal recording for body language patterns:

Observations:
- Unconscious movements: [List any detected]
- Gesture effectiveness: [Assessment]
- Stage presence: [Podium vs. open stage usage]
- Suggestions: [Specific improvements]

Would you like me to track these across multiple rehearsals?

Step 4.2: Voice Modulation & Tone

Core Principle: Voice is your instrument. Flat = boring = audience sleeps.

Why Modulation Matters:

• Creates dynamic energy (like narrative arcs for audio)
• Conveys emotion (excitement, tension, revelation, concern)
• Maintains attention (monotone loses audience)
• Makes content memorable (emotional moments stick)

Modulation Techniques:

1. Volume Variation

• Louder: Emphasis, excitement, climax moments
• Softer: Intimacy, building tension, inviting audience to lean in
• Normal: Baseline delivery

2. Pace Control

• Fast: Excitement, urgency, building momentum
• Slow: Emphasis, complex concepts, allowing absorption
• Pauses: Powerful punctuation, creates anticipation

3. Pitch Movement

• Rising: Questions, building tension, inviting engagement
• Falling: Conclusions, finality, authority
• Varied: Natural conversation, emotional range

4. Emphasis Placement Wrong: "We FOUND 47 ZERO-DAYS in industrial SYSTEMS." Right: "We found FORTY-SEVEN zero-days in INDUSTRIAL control systems."

Technical Analysis: MFCC Delta Coefficients

What it measures: Rate of change in vocal spectral shape (timbre, resonance, vowel quality)

Engaging speeches: High variability in MFCC deltas (dynamic voice movement) Boring speeches: Low variability in MFCC deltas (flat, monotonous)

Practical takeaway: Keep your voice moving. Vary pitch, pace, volume throughout.

AI Agent Coaching:

Recording analysis results:
- Voice variability score: [0-100]
- Monotonous segments detected: [Timestamps]
- Energy peaks: [Timestamps]
- Recommendations: [Specific sections to add modulation]

Practice exercises:
1. Read [specific paragraph] with exaggerated emotion
2. Emphasize different words in: "[key sentence]"
3. Practice pause placement at: [key moments]

Step 4.3: Stage Presence & Eye Contact

Eye Contact Strategy:

• Scan room systematically (not fixating on one person)
• Make brief contact (2-3 seconds per person)
• Include all sections (front, back, left, right)
• Avoid: Staring at screen, looking at floor, focusing only on front row

If You Feel Confident (optional but powerful):

• Making eye contact with a person is a very powerful tool to keep engagement high
• But you need to feel confident in order to fully master it
• If you look at the audience, don't fixate on only one person; change periodically

Stage Light Adaptation:

• Look at audience BEFORE starting (eyes adapt to lights)
• Don't focus on laptop then suddenly look up (disorienting)
• Familiarize with stage environment during rehearsal

Embracing the Moment:

• First 5-10 seconds: Breathe, smile, make eye contact
• Don't rush into speech (pause builds anticipation)
• Own the space (you belong on that stage)

Technical Setup Awareness:

• You'll have your laptop with speaker notes and timer
• You'll have a monitor on the floor showing the projector's output
• Looking at the audience is optional and should not interfere with flow

---

Phase 5: Preparation Timeline & Logistics

Timeline Overview

4-6 Weeks Before:

• ✅ Target audience identified
• ✅ Core message finalized (280 char)
• ✅ 3-4 sub-messages defined
• ✅ Legal/disclosure settled

3-4 Weeks Before:

• ✅ Outline 90% complete
• ✅ Outline moved to speaker notes
• ✅ Narrative arcs mapped
• ✅ Content selection finalized
• ✅ Simple illustrations drafted
• ✅ Complex diagrams described (not designed yet)
• ❌ Slides NOT started

2-3 Weeks Before:

• ✅ Slides 90% final
• ✅ Demos 80% complete
• ✅ Illustrations finalized
• ✅ First rehearsal recorded
• ✅ Daily rehearsals (1 every 1-2 days)
• ✅ Immediate post-rehearsal edits

1-2 Weeks Before:

• ✅ 3-5 full rehearsals
• ✅ Room layout obtained
• ✅ Tech requirements confirmed (mic, prompter, screen setup)
• ✅ Slide edits after each rehearsal
• ❌ NO major content changes

1 Day Before:

• ✅ Final rehearsals in similar room (ideally actual room)
• ✅ Tech check with AV team
• ✅ No slide edits (content locked)
• ✅ Alarm clocks set (bedtime + morning)

Day Of:

• ✅ Morning rehearsal (first thing after waking)
• ✅ No slide adjustments (unless legal emergency)
• ✅ 2-hour countdown logistics (see below)

The 2-Hour Pre-Talk Countdown

2 Hours Before:

• Locate room, know route from anywhere in venue
• Account for venue size, crowds, elevators

1 Hour Before:

• Use restroom
• Facial muscle stretching (reduces stiffness, dry mouth)
• Hydrate (not too much)

30 Minutes Before:

• Memorize/repeat opening (if complex)
• Mental visualization of first 2-3 minutes
• Walk a couple flights of stairs OR do 3-5 pushups/squats
  • Increases heart rate, brings oxygen to brain
  • Releases nervous energy productively

10 Minutes Before:

• Test clicker (slide forward/back)
• Get mic'd up
• Sip water (light)
• Get sugar/candy (speaking is physical + mental effort)
• Close all apps except presentation software
• Enable "Do Not Disturb" (all devices)

5 Minutes Before:

• Repeat first sentence out loud (your hook)
• Trust the rest will follow (brain's index lookup)
• Stretch face muscles: open/close mouth wide, forced smiles
  • Warms up facial muscles for long speech
  • Reduces dry mouth

On Stage (First Seconds):

• Don't focus on laptop
• Stare at audience, make eye contacts
• Smile, embrace feeling
• Let eyes adapt to stage lights
• Pause, breathe, then begin

Physical Anxiety Management Techniques

Pre-Event (Day/Night Before):

• Relaxation exercises for body and mind
• Prepare and organize all materials
• Get adequate sleep (set alarm for bedtime)

Pre-Talk Physical Preparation:

| Timing | Technique | Purpose | |--------|-----------|---------| | 30 min | Stairs/pushups/squats | Oxygen flow, release tension | | 10 min | Water + candy | Hydration + sugar for energy | | 5 min | Face stretches | Warm up speech muscles | | 5 min | Repeat first sentence | Confidence anchor |

If Nervous During Talk:

• Get behind podium and put hands on it (grounds you physically)
• Focus on one friendly face briefly, then move on
• Take a deliberate breath before continuing
• Remember: audience wants you to succeed

Venue Intelligence

Questions for Organizers:

☐ Room layout/floor plan available?
☐ Podium location and setup?
☐ Microphone type (handheld, lavalier, headset)?
☐ Stage size and movement area?
☐ Prompter/confidence monitor available?
☐ Screen/projector resolution and aspect ratio?
☐ Internet connectivity for demos?
☐ AV tech contact for day-of coordination?
☐ Recording setup (if applicable)?

Day-Before Room Visit:

• Walk stage area
• Test sight lines from audience perspective
• Check lighting (where are bright spots?)
• Test laptop connections
• Identify tech booth location
• Rehearse if possible

Room Visualization Exercise: Find a time when the exact same room is empty:

1. Walk in, get on stage
2. Look around, observe the space
3. Imagine it filled with audience
4. Experience that feeling and the fear it brings
5. Breathe through it—you've now rehearsed the emotional moment

---

Coaching Framework for Mentors & AI Agents

Core Coaching Philosophy

Goal: Help speakers close the credibility-impact gap by designing presentations that match the quality of their technical work.

Principles:

1. Listening First: Understand what speaker wants audience to remember
2. Separate Layers: Message clarity → Visual design → Delivery technique
3. Name the Stakes: Help articulate why THIS talk matters RIGHT NOW
4. Outcome Focus: Align on desired outcome before fixing the "how"

Communication Style: Be very honest because you care about the quality of the presentation and want the speaker to shine on stage. Feedback should never be taken as personal, offensive, or discouraging—it's constructive input toward excellence.

Three-Phase Coaching Approach

Phase 1: Listening Audit

1. Watch raw rehearsal or past talk WITH the speaker
2. Ask: "If audience remembers ONE thing, what should it be?"
3. Compare to what YOU remember as coach
4. That gap = your starting point for coaching

Phase 2: Message Before Mechanics

1. Don't open with slide edits
2. First: Fix message clarity (core message + sub-messages)
3. Second: Structure story (narrative arcs, content selection)
4. Third: Design visuals (only after story is solid)
5. Last: Delivery technique (tone, pacing, body language)

Phase 3: Stakes and Urgency

1. Help speaker articulate: "Why does this talk matter RIGHT NOW?"
2. Identify target audience and their specific needs
3. Connect research findings to audience priorities
4. Urgency is contagious—audience will feel it if speaker does

Critical Coaching Pitfall to Avoid

DON'T: Jump straight into "add this slide / remove that detail" without aligning on outcome.

WHY: If you fix the how before the why, you'll just make a prettier version of the same unclear message.

DO: Always start with: "What do you want the audience to do/think/remember after this talk?"

The Coach's Run Book

Step-by-step checklist for guiding speakers:

1. Kickoff Meeting: Define goals, constraints, and deadlines
2. Audience Analysis: Identify 3-4 key audience types with their needs
3. Core Message Workshop: Iterate on 280-character message
4. Sub-Message Development: Create 3-4 supporting messages
5. Story Structure Review: Map narrative arcs
6. Content Selection: Ruthlessly cut non-essential material
7. Speaker Notes Draft: Full script before slides
8. Slide Review: Evaluate visual support for story
9. Rehearsal Observations: Watch for delivery patterns
10. Iterative Feedback: Continuous improvement loop
11. Final Checks: Slides, content, time management, confidence

Structured Coaching Timeline

Week 1 (30 min): Abstract readout

• Review slides (if available) or outline
• Focus on logic flow
• Identify core message clarity

Week 2 (45 min): First assisted rehearsal

• Go through slides checking logic flow
• Create revision plan
• Assign homework on weak areas

Week 3 (60 min): First full rehearsal

• Listen as if delivering live
• Take detailed notes
• Send comments offline for speaker to process

Week 4 (45 min): Second full rehearsal

• Track improvement on previous feedback
• Final polish items
• Confidence building

Communicating With Coached Speakers

Opening Frame: "I will be very honest because I care about the quality of your presentation and I want you to shine on stage. Don't take any of what I share as personal, offensive, or discouraging. It's just feedback aimed at making your talk excellent."

Feedback Structure:

1. What's working well (specific praise)
2. What needs work (specific, actionable)
3. Priority order (what to fix first)
4. Next steps (clear assignments)

Handling Resistance:

• Acknowledge the speaker has valuable technical content
• Remind them the goal is impact, not comprehensiveness
• Focus on audience benefit, not speaker preferences
• Use examples from successful talks they admire

---

AI Agent Coaching Workflows

Workflow 1: Initial Consultation & Message Design

Agent Prompt Sequence:

1. "Tell me about your research/work you're presenting."
   [Gather context]

2. "What conference/venue is this for?"
   [Determine academic vs. practitioner style]

3. "Who is your target audience?"
   [Use audience archetypes, identify primary]

4. "In 280 characters, what's the ONE thing you want them to remember?"
   [Draft core message]

5. [Provide feedback on clarity, specificity, memorability]
   [Iterate 2-3 times]

6. "Let's break that into 3-4 supporting messages."
   [Guide decomposition using pyramid style]

7. [Validate each sub-message supports core message]

Workflow 2: Story Architecture Review

Agent Prompt Sequence:

1. "For each sub-message, describe the story you'll tell."
   [Gather narrative content]

2. "Let's map this to narrative arcs..."
   [Apply setup → rising → climax → resolution structure]

3. "What content are you considering including?"
   [List all topics]

4. "Let's ruthlessly cut anything that doesn't serve the core message."
   [Apply selection framework]

5. "Now let's outline this in speaker notes, not slides."
   [Build speaker note templates]

Workflow 3: Visual Design Guidance

Agent Prompt Sequence:

1. "What code/diagrams do you need to show?"
   [Inventory visuals]

2. "For each code block, paste it and I'll help reduce it."
   [Apply radical reduction technique]

3. "For each diagram, let's plan incremental reveal."
   [Design slide sequence]

4. "Do you have demos? Let's decide live vs. pre-recorded."
   [Apply decision framework]

5. "Remember: visuals serve story. Story doesn't serve visuals."
   [Validate each visual's purpose]

Workflow 4: Delivery Coaching

Agent Prompt Sequence:

1. "Let's review your rehearsal recording."
   [If video: analyze body language]
   [If audio: analyze voice modulation]

2. "I noticed [specific patterns]. Let's work on [specific improvements]."
   [Targeted feedback]

3. "Practice exercises for this session:"
   [Provide specific drills]

4. "Record again with focus on [improvement area]."
   [Iterative refinement]

Workflow 5: Timeline & Logistics Management

Agent Prompt Sequence:

1. "When is your talk? [Date]"
   [Calculate timeline]

2. "Here's your preparation schedule:"
   [Generate milestone checklist based on weeks remaining]

3. "Have you contacted organizers about [venue questions]?"
   [Ensure logistics covered]

4. "Let's build your 2-hour pre-talk checklist."
   [Customize countdown based on user needs]

Workflow 6: Speaker Style Assessment

Agent Prompt Sequence:

1. [Administer Speaker Style Self-Assessment questions]

2. "Based on your responses, you're primarily a [Archetype] speaker."
   [Explain strengths and challenges]

3. "For this specific talk and venue, here's how to leverage your style:"
   [Tailored recommendations]

4. "Here's an exercise to strengthen [weakness area]:"
   [Archetype-specific exercise]

Workflow 7: Academic Conference Preparation

Agent Prompt Sequence:

1. "This is for an academic venue. Let's ensure rigor alongside clarity."
   [Set expectations]

2. "What's your threat model and key assumptions?"
   [Academic framing]

3. "How does this relate to prior work? What's novel?"
   [Contribution clarity]

4. "What are the limitations? Anticipate reviewer questions."
   [Honest assessment preparation]

5. "Let's prepare for adversarial Q&A."
   [Practice tough questions]

---

Quality Criteria & Assessment

Core Message Quality Checklist

☐ Self-contained (understandable without context)?
☐ Specific (concrete insight, not generic wisdom)?
☐ Memorable (audience would repeat it)?
☐ ≤ 280 characters?
☐ Shareable (would someone post this)?
☐ Aligned with target audience priorities?

Story Architecture Quality Checklist

☐ 3-4 clear sub-messages supporting core message?
☐ Each sub-message has narrative arc (setup → climax → resolution)?
☐ Content ruthlessly selected (no "nice to have" bloat)?
☐ Logical flow with smooth transitions?
☐ Emotional moments strategically placed?
☐ No agenda/spoilers revealed upfront?
☐ Impact explained before methodology?

Visual Design Quality Checklist

☐ Every visual serves specific narrative purpose?
☐ Code reduced to 2-5 essential lines?
☐ Complex diagrams revealed incrementally?
☐ No walls of text (max 3-4 bullet points per slide)?
☐ Animations only when serving narrative?
☐ Demos pre-recorded (unless live is essential)?
☐ Videos embedded full-screen with auto-play?
☐ Slides are NOT speaker notes?

Delivery Quality Checklist

☐ Strong, memorized opening (no filler phrases)?
☐ No ego-driven intro (credentials emerge through content)?
☐ Body language aligned with message?
☐ Voice modulation creates dynamic energy?
☐ Eye contact distributed across room?
☐ Stage presence confident and purposeful?
☐ Pacing appropriate (not rushed, not dragging)?
☐ Pauses used for emphasis and transitions?

Preparation Completeness Checklist

☐ Core message finalized 4 weeks before?
☐ Speaker notes complete before slides created?
☐ 3-5 rehearsals in final 2 weeks?
☐ Immediate edits after each rehearsal?
☐ Venue logistics confirmed (room, tech, mic)?
☐ Day-before room visit completed?
☐ Morning-of rehearsal planned?
☐ 2-hour countdown checklist ready?
☐ Physical anxiety management techniques practiced?

Academic Conference Additional Checklist

☐ Threat model clearly stated?
☐ Novelty/contribution explicitly articulated?
☐ Related work acknowledged appropriately?
☐ Limitations honestly discussed?
☐ Evaluation methodology defensible?
☐ Prepared for adversarial Q&A?

---

Self-Assessment & Reflection Exercises

Exercise 1: Analyze Great Talks

Instructions: Think of the last talk you saw that stuck with you.

Questions to Ask:

1. What was the moment you remember most?

   • Specific insight, demonstration, story, or revelation?

2. Did the speaker design that moment or did it happen by accident?

   • How can you tell? (Prepared opening? Strategic visual? Deliberate pause?)

3. Can you explain the core takeaway to a colleague today?

   • Try writing it in 280 characters

4. What made it memorable?

   • Story structure? Emotional connection? Clarity? Visuals? Delivery?

Exercise 2: Reverse-Engineer Failed Talks

Instructions: Find a recording of a talk you didn't like. Re-watch it.

Questions to Ask:

1. When did you lose interest? (Specific timestamp)

   • What caused the disconnect?

2. What was the core message?

   • Could you identify it? If not, why not?

3. What would you fix first?

   • Message clarity? Story structure? Visuals? Delivery?

4. What could the speaker have cut?

   • Identify 3 things that didn't serve the core message

5. What's ONE change that would have biggest impact?

   • Apply the 80/20 rule

Exercise 3: Self-Audit Your Own Presentations

Instructions: Watch a recording of your own past presentation (or rehearsal).

Questions to Ask:

1. Message Test:

   • Could someone who dozed off for 20 minutes still understand your core point?
   • Did you state it clearly in first 5 minutes?

2. Attention Test:

   • At what points would YOU (objectively) lose interest?
   • What could you cut without losing core message?

3. Clarity Test:

   • Show recording to someone unfamiliar with topic
   • Ask them: "What's the ONE thing you remember?"
   • Compare to what you WANTED them to remember

4. Delivery Test:

   • Watch with sound OFF: Does body language support message?
   • Listen with screen OFF: Does voice convey energy and emotion?

Exercise 4: The 280-Character Challenge

Instructions: For your next presentation, write down:

1. Your core message in 280 characters (before designing talk)
2. What you HOPE someone will tweet about your talk
3. After the talk, collect actual social media posts
4. Compare: Did reality match your intention?

Learning:

• Gap analysis reveals messaging effectiveness
• Iterate for next presentation
• Build pattern recognition for what lands vs. what doesn't

Exercise 5: Archetype Stretching

Instructions: Practice presenting outside your natural archetype.

For Analysts (stretch toward Inspirer):

• Take a technical finding and explain only the human impact
• No methodology, just "why this matters to people"
• 2 minutes max

For Visionaries (stretch toward Educator):

• Take your vision and break it into step-by-step implementation
• Assume audience needs to DO something Monday morning
• Concrete actions only

For Educators (stretch toward Analyst):

• Take a simplified concept and add one layer of technical depth
• Maintain accessibility while increasing rigor
• Include one specific number or metric

For Inspirers (stretch toward Visionary):

• Take an emotional story and connect it to strategic change
• What should organizations DO differently because of this story?
• Business language, not just personal impact

---

Handling Cybersecurity-Specific Scenarios

Last-Minute Content Changes

Scenario: Vendor patches vulnerability day before your talk.

Response Framework:

1. Assess: Does patch change your core message? Usually no.
2. Update: Add one slide acknowledging the patch
3. Pivot: "This was patched yesterday, which validates our findings"
4. Maintain: Core methodology and lessons learned still valuable

Legal Constraints on Content

Scenario: Legal team asks to remove specific details.

Response Framework:

1. Clarify: Exactly what cannot be said?
2. Adapt: Can you convey same insight without restricted details?
3. Abstract: Replace specific identifiers with categories
4. Prepare: Have stock phrases ready ("Due to ongoing matters, I can't discuss specifics, but the pattern is...")

Live Questions from Media

Scenario: Journalist in audience asks for quotable soundbite.

Response Framework:

1. Bridge: "The key point is..."
2. Simplify: One clear sentence they can quote accurately
3. Scope: "What we found specifically was... (not making claims beyond that)"
4. Follow-up: "Happy to discuss more detail after, here's my contact"

Breaking News During Talk

Scenario: Related incident breaks while you're presenting.

Response Framework:

1. Acknowledge: "I understand something related may have just happened"
2. Scope: "I can only speak to what I've researched, which is..."
3. Decline: "I won't speculate on breaking news without details"
4. Continue: Return to your prepared content

Adversarial Q&A (Academic)

Scenario: Reviewer asks pointed question about methodology weakness.

Response Framework:

1. Acknowledge: "That's a fair point and a limitation we discuss in the paper"
2. Explain: "We chose this approach because..."
3. Future: "Addressing this is planned for follow-up work"
4. Redirect: "The contribution still holds because..."

Executive Audience Disengagement

Scenario: C-suite checking phones during your technical deep-dive.

Response Framework:

1. Recognize: You've lost them in details
2. Bridge: "The bottom line for your organization is..."
3. Simplify: Skip remaining technical slides
4. Action: "What this means for your decision is..."

---

Common Pitfalls & Troubleshooting

Issue: "I can't fit everything into the time limit"

Root Cause: Trying to be comprehensive instead of impactful.

Solution:

1. Revisit core message—does it require ALL this content?
2. Apply ruthless selection: Essential vs. nice-to-have
3. Trust that interested audience will reach out for details
4. Remember: Impact > exhaustive coverage

Issue: "My content is too technical for general audience"

Root Cause: Not translating for target audience.

Solution:

1. Identify your PRIMARY audience (not everyone)
2. Use analogies/examples relatable to them
3. Show impact before diving into methodology
4. Build complexity incrementally (don't start at highest level)

Issue: "I'm terrified of public speaking"

Root Cause: Normal anxiety + lack of preparation.

Solution:

1. Memorize strong opening (removes "what do I say" panic)
2. Rehearse 5+ times (builds muscle memory)
3. Visit room day before (reduces surprise factor)
4. Focus on service mindset ("I'm here to help audience") vs. performance anxiety
5. Record rehearsals (builds confidence through visible improvement)
6. Use physical techniques (stairs, stretching, candy) before talk
7. Get behind podium if nervous (physical grounding)

Issue: "Demos/slides/tech failed during presentation"

Root Cause: Over-reliance on technology without backup plan.

Solution:

1. Pre-record critical demos (eliminate live failure risk)
2. Export slides as PDF backup
3. Test all tech 10 minutes before
4. Have verbal explanation ready if visual fails
5. Practice "tech failure recovery" in rehearsal

Issue: "Audience seems disengaged during talk"

Root Cause: Story design or delivery issue.

Solution:

1. Story: Check if core message clear and narrative arcs create tension
2. Visuals: Simplify if overwhelming, add incremental reveals
3. Delivery: Increase voice modulation, movement, eye contact
4. Timing: Accelerate if dragging, add pauses if rushing

Issue: "I keep getting 'so what?' feedback"

Root Cause: Explaining the bug/finding before the impact.

Solution:

1. Lead with impact/consequence
2. Build curiosity: "How did this happen?"
3. THEN explain the technical details
4. Return to impact at the end

Issue: "My slides are too dense but I can't cut anything"

Root Cause: Slides functioning as speaker notes.

Solution:

1. Move all text to speaker notes
2. Slides get: visuals, keywords, minimal bullets (max 3-4)
3. If you need to read it, audience doesn't need to see it
4. Apply progressive reveal to complex content

---

Success Metrics

Immediate Impact (During/After Talk)

• Audience attention (eyes on speaker, not devices)
• Questions quality (thoughtful vs. clarification-seeking)
• Post-talk conversations initiated by attendees
• Social media posts mentioning core message

Medium-Term Impact (Days/Weeks)

• Video views and engagement (if recorded)
• Follow-up emails/messages
• Citations in others' work
• Invitations to speak at other venues

Long-Term Impact (Months/Years)

• Research adoption or replication
• Industry changes influenced by findings
• Professional relationships formed
• Career opportunities from visibility

---

Integration with SuperClaude Framework

Persona Alignment

Primary Personas:

• --persona-mentor: Educational coaching, knowledge transfer
• --persona-scribe: Story crafting, messaging clarity
• --persona-analyzer: Content analysis, structure review

Auto-Activation Triggers:

• Keywords: "presentation", "talk", "speaking", "conference", "demo"
• Context: Preparing technical content for public delivery
• Requests: Coaching, feedback, rehearsal review

MCP Integration

Context7:

• Public speaking best practices
• Conference-specific guidelines (Black Hat, DEF CON, RSA, IEEE S&P, USENIX)
• Visual design patterns
• Academic presentation standards

Sequential:

• Multi-step story analysis
• Narrative arc evaluation
• Timeline planning
• Complex content structuring

Flag Usage

Recommended Flags:

• --persona-mentor: Activate teaching/coaching mode
• --think: For complex story architecture analysis
• --validate: For quality gate checks (message, story, visuals, delivery)

Command Integration

Compatible Commands:

• /document: For speaker notes, handouts, post-talk materials
• /analyze: For presentation structure analysis
• /improve: For iterative refinement based on rehearsals
• /explain: For clarifying complex concepts to simplify for audience

---

References & Resources

Source Material

1. Maggi, F. (2025). "Cybersecurity Needs Supercommunicators." [Blog post on why effective communication matters in cybersecurity]
2. Maggi, F. (2026). "Become a Cybersecurity Supercommunicator." [Blog post with practical guidance on designing and delivering talks]
   • Includes downloadable slide deck (224M): https://supercommunicators.trustial.org

Foundational Reading

1. Duhigg, C. (2024). Supercommunicators: How to Unlock the Secret Language of Connection. Random House. https://charlesduhigg.com/supercommunicators/
2. Reynolds, G. (2019). Presentation Zen: Simple Ideas on Presentation Design and Delivery. New Riders.
3. Duarte, N. (2010). Resonate: Present Visual Stories that Transform Audiences. Wiley.

Conference Resources

Practitioner Conferences:

• Black Hat Speaker Resources: https://blackhat.com/speakers/
• Black Hat Speaker Coaching Program: https://www.blackhat.com/html/speaker-coaches.html
• Black Hat EU 2025 Community Conversations: https://blackhat.com/eu-25/features/schedule/index.html?track[]=community-conversations
• DEF CON Speaker Guidelines: https://defcon.org/html/links/dc-speakers.html
• DEF CON 32 Talk Dataset: https://infocon.org/cons/DEF%20CON/DEF%20CON%2032/
• OWASP Presentation Templates: https://owasp.org/

Academic Conferences:

• IEEE S&P (Oakland): https://www.ieee-security.org/TC/SP-Symposium/
• USENIX Security: https://www.usenix.org/conferences
• ACM CCS: https://www.sigsac.org/ccs/
• NDSS: https://www.ndss-symposium.org/

Industry Research

• Schneier, B. (2019). "Cybersecurity for the Public Interest." https://www.schneier.com/essays/archives/2019/02/public-interest_tech.html
• World Economic Forum (2024). "Strategic Cybersecurity Talent Framework" [Global talent deficit: ~4 million practitioners]

Technical Resources

• Voice Analysis (MFCC): https://librosa.org/doc/main/generated/librosa.feature.mfcc.html
• Observational Learning Theory: https://www.simplypsychology.org/what-is-observational-learning.html
• Facial Muscle Stretching: https://www.youtube.com/watch?v=EdbAl7PJlxg / https://www.youtube.com/watch?v=dl4GFMBtLhU

Mentorship Programs

• LeadTheFuture Mentoring: https://www.leadthefuture.tech/mentors
• Black Hat Speaker Coaching Program: https://www.blackhat.com/html/speaker-coaches.html

---

Appendix: Quick Reference Templates

Core Message Template

In 280 characters or less:

[Your research/work] + [Key finding/insight] + [Why it matters]

Example: "We discovered 47 zero-days in ICS firmware through coverage-guided fuzzing—vendors had no visibility into attack surface, leaving critical infrastructure exposed."

Sub-Message Template

Sub-message 1: [Topic]
- What: [Key concept]
- Why: [Supporting evidence/story]
- So what: [Implication/takeaway]

[Repeat for 2-3 more sub-messages]

Speaker Notes Template

[SLIDE X] - [Title/Concept]

WHAT I'LL SAY:
[2-3 paragraphs of actual words/narrative]

KEY POINTS TO EMPHASIZE:
- [Point 1]
- [Point 2]

TRANSITION:
[Bridge sentence to next slide]

TIMING: ~X minutes

VISUAL: [Description of what slide should show]

Rehearsal Feedback Template

REHEARSAL #[N] - [Date]

STRENGTHS:
- [What worked well]

IMPROVEMENTS NEEDED:
- [Specific issues]

IMMEDIATE ACTIONS:
- [Slide edits]
- [Delivery practice areas]

NEXT REHEARSAL FOCUS:
- [What to emphasize]

Pre-Talk Checklist

☐ 2 hours: Located room, know route
☐ 1 hour: Restroom, stretching, hydration
☐ 30 min: Opening memorized/practiced, stairs/exercise
☐ 10 min: Tech check, mic, clicker, water, candy
☐ 10 min: Apps closed, DND enabled
☐ 5 min: First sentence repeated, face stretches
☐ On stage: Breathe, smile, eye contact, pause, BEGIN

Audience Analysis Template

AUDIENCE TYPE: [Name]

What they already know:
- [Baseline knowledge]

What they want to learn:
- [Motivation]

What I want them to remember:
- [My goal]

What action I want them to take:
- [Desired outcome]

Coaching Session Template

SESSION #[N] - [Date] - [Duration]

REVIEW:
- Progress since last session
- Homework completion

FOCUS AREAS:
- [Primary focus]
- [Secondary focus]

FEEDBACK:
- Strengths: [Specific]
- Areas to improve: [Specific, actionable]

HOMEWORK:
- [Specific assignments]

NEXT SESSION:
- Date: [Date]
- Focus: [Preview]

---

End of Skill Definition

This skill transforms AI agents into expert presentation coaches for cybersecurity professionals, enabling them to elevate technical content into memorable, influential talks that maximize impact and career advancement.