Webinar Run-of-Show & Script

Writes the live webinar itself: minute-by-minute run of show, slide outline, speaker script, polls, seeded Q&A, CTA, and producer cues.

Marketingwebinarsevent-marketing
by AgentVoltv1.0.0
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Plan a technical webinar about building microservices architecture”
Beforegeneric AI agent
Planning a webinar is a lot of work. You'll need to decide on a topic, figure out an outline, and think about how to present it in an engaging way. You might want slides to support the content. Interactive elements like Q&A or polls can help keep the audience engaged. It's good to have a clear structure with an introduction, main content, and a conclusion. You might want to invite guest speakers or include demos if relevant. There's a lot to think through before going live.
Afterwith Webinar Run-of-Show & Script
WEBINAR PLAN: Microservices Deep Dive

FORMAT
Duration: 60 minutes live + 30 min Q&A
Target: Backend engineers, architects (mid-level to senior)
Registration goal: 200, expect 120 attendees

CURRICULUM OUTLINE

0-5 min: OPENING
- Brief bio + microservices in headlines (why it matters now)
- Agenda overview on slide

5-20 min: MONOLITH PROBLEMS (with visuals)
- Deployment friction: releasing one feature hits 10k lines
- Scaling inefficiency: scaled entire app for one bottleneck
- Tech debt: monolith language lock-in
- Real example: e-commerce platform scaling nightmare (company name omitted, generic)

20-40 min: MICROSERVICES PATTERNS
- Service boundaries (bounded contexts from domain-driven design)
- Communication (sync REST vs async queues, trade-offs)
- Data consistency (eventual consistency, saga pattern demo)
- Deployment: containers + orchestration (3-min Kubernetes primer)

40-45 min: LIVE DEMO
- Deploy 3 services in container cluster
- Show service-to-service calls + logging
- Simulate failure (kill one service, system recovers)

45-60 min: DESIGN DECISIONS & GOTCHAS
- When NOT to use microservices (team < 10 engineers)
- Testing complexity (integration tests harder)
- Latency (network hops have cost)
- Common mistake: micro-managing service versions

60+ min: Q&A + Slack channel for follow-ups

SLIDE STRUCTURE
→ 25 slides total (1 per 2-3 minutes + extra for Q&A)
→ Live code in Kubernetes manifest (not screen recordings)
→ Color scheme: dark background (eye strain prevention)

PROMOTION
Email list: 3 touches (1 week before, 2 days before, morning-of)
LinkedIn post: 1 week early

About this skill

Walk into your webinar with every minute planned. This skill writes the run of show, slide outline, and script so speakers and producer work from one document.

What it does

  • Structures the session with engagement beats every 8-10 minutes
  • Outlines slides one idea at a time with timings and speaker notes
  • Scripts the hook, transitions, CTA, and close word for word
  • Writes polls that segment the audience and seeds Q&A questions
  • Adds a producer cue sheet, demo backup plan, and rehearsal checklist

What you get

A complete run of show: timeline, slide-by-slide script, polls, seeded Q&A, CTA copy, producer cue sheet, rehearsal checklist, and post-session handoff list.

Best for

Marketers, founders, and customer education teams running live demos, masterclasses, or customer webinars.

SKILL.md preview

SKILL.md
---
name: webinar-run-of-show

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More marketing & growth skills

View all Marketing & Growth skills →