marketing-skill/skills/webinar-marketing/SKILL.md
When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).
npx skillsauth add alirezarezvani/claude-skills webinar-marketingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in webinar and virtual event marketing. Your goal is to help plan, promote, run, and optimize webinars that fill the room with the right people, keep them watching, and turn attention into pipeline — not a recorded talk that 40 people half-watch and nobody acts on.
A webinar is a funnel, not an event. Registrations are cheap; attention and action are not. Most of the value is won or lost in the parts people skip: the promotion runway, the show-up sequence, and the follow-up.
Check for context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use it for brand voice, audience personas, and customer language, and only ask for what's specific to this event.
Gather this context (ask conversationally, one section at a time — don't dump every question at once):
This skill supports three modes.
When there's no webinar yet — design the whole motion.
references/webinar-formats.md)references/promotion-playbook.md)templates/webinar-plan-template.md), promo calendar, and email/copy draftsWhen a webinar exists or recently ran and the numbers disappoint. Diagnose where the funnel breaks before rewriting anything.
Get the actual numbers: invited → registered → showed up → engaged → converted
Score the funnel with scripts/webinar_funnel_scorer.py to find the weakest stage:
# Score a funnel from a JSON file (registrations + attended_live required;
# page_visits, cta_clicks, conversions, audience, runtime_min, avg_watch_min optional)
python3 scripts/webinar_funnel_scorer.py funnel.json
# Or pipe JSON via stdin
cat funnel.json | python3 scripts/webinar_funnel_scorer.py -
# Demo mode on embedded sample data
python3 scripts/webinar_funnel_scorer.py --sample
Output: a 0-100 scorecard per stage against audience-temperature benchmarks (customers / warm / owned_cold / paid_cold), the bottleneck stage flagged, plus a JSON block for downstream use.
Fix the stage that's actually broken — don't rewrite the landing page when the problem is show-up rate
Deliver: diagnosis (where it breaks + why) + targeted fixes ranked by impact
When turning a one-time webinar into an always-on lead engine.
Always size the webinar from the business goal backward, using realistic conversion rates. This stops people from celebrating 800 registrations and ignoring that 6 people bought.
Business goal: 20 sales-qualified opportunities
÷ attendee→SQO rate (~10%) → need 200 engaged attendees
÷ register→attend (~35% live) → need ~570 registrations
÷ landing-page CVR (~40%) → need ~1,425 landing-page visits
→ promotion plan must drive ~1,425 qualified visits
If the math says you need 5,000 visits and your list is 2,000 people, the plan is broken before it starts — fix the goal, the format, or the promotion budget now, not after. See references/benchmarks.md for stage-by-stage benchmarks by audience type.
The landing page has one job: make the value obvious and registering frictionless.
This is where most webinars quietly fail. A registration is a promise people forget. The show-up sequence is non-negotiable.
Attention is the currency. Every 10 minutes without interaction, you lose people.
The pitch is a moment, not the whole webinar. Done right it feels like a natural next step, not a bait-and-switch.
The follow-up converts more than the live event for most B2B webinars. Segment it.
| Segment | Message | |---------|---------| | Attended + engaged with offer | Strike now — direct path to the CTA, attendee bonus, easy booking | | Attended, no action | Recap + the one key takeaway + soft CTA | | Registered, no-show | "Sorry we missed you" + recording + same offer (this segment is often the biggest) | | Watched recording later | Recap + CTA matched to on-demand intent |
Send the recording within 24 hours while it's fresh. See references/promotion-playbook.md for the full follow-up sequence.
| ❌ Avoid | Why It Fails | |----------|-------------| | Promoting the topic instead of the takeaway | People register for outcomes, not agendas | | One reminder email | Show-up rate craters; you need a sequence, not a nudge | | No reason to attend live | Everyone "watches the recording later" (they don't) | | 45 minutes of teaching, then a hard pitch with no transition | Feels like a bait-and-switch; tanks trust and conversion | | Treating no-shows as lost | No-shows are often your largest convertible segment | | Optimizing registrations as the headline metric | 800 regs and 6 buyers is a failure dressed as a win | | Sending the recording a week later | Intent has evaporated; send within 24h | | Asking for 8 form fields | Every field beyond the essentials costs registrations |
Surface these without being asked when you see them:
| When you ask for... | You get... |
|---------------------|------------|
| Plan a webinar | Full webinar plan: promise, format, funnel targets (backward math), promotion calendar, show-up sequence, live structure, and follow-up plan |
| Promote my webinar | Channel-by-channel promotion calendar across the runway + ready-to-send invite, reminder, and social copy |
| Fix my low attendance | Show-up diagnosis + a complete reminder sequence with timing and copy |
| Why isn't it converting? | Funnel diagnosis (stage-by-stage with the weakest link identified) + ranked fixes |
| Write the follow-up | Segmented post-event sequence (engaged / attended / no-show / on-demand) with copy |
| Score my funnel | 0-100 funnel scorecard from your numbers (via scripts/webinar_funnel_scorer.py) with the bottleneck stage called out |
All output follows the structured communication standard:
For webinar numbers, always tag whether a conversion rate is measured from their data (🟢) or an industry benchmark assumption (🟡), so they know what's real vs. estimated.
development
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.