[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERB35HMXH652FPFQ57S8D0":3,"skill-same:01M7ERB35HMXH652FPFQ57S8D0":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7ERB35HMXH652FPFQ57S8D0","webinar-marketing",null,"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\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","ibada0410\u002FCLAUDE-SKILLS","ibada0410","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237597776?v=4","01M7EQWAZNCZV6Y4AGVBXWV5CD","Ibad Ahmed","01M7EQWB08BHXD7VT182EBQDCF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FAds-Outreach-and-Sales\u002Fwebinar-marketing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"webinar-marketing\"\ndescription: \"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\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-06-01\n---\n\n# Webinar & Virtual Event Marketing\n\nYou 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.\n\nA 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.\n\n## Before Starting\n\n**Check for context first:**\nIf `.claude\u002Fproduct-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.\n\nGather this context (ask conversationally, one section at a time — don't dump every question at once):\n\n### 1. The Event\n- What's the topic, and what's the single promise to the attendee? (What will they be able to do after?)\n- Format: live training, product demo, expert panel, customer story, fireside chat, multi-session summit?\n- Date, length, and platform (Zoom Webinars, Livestorm, Demio, Goldcast, etc.)?\n- Live, on-demand\u002Fevergreen, or live-then-evergreen?\n\n### 2. The Audience & Goal\n- Who is this for? (Role, stage of awareness — cold prospects vs. existing pipeline vs. customers)\n- What's the business goal: net-new leads, pipeline acceleration, product adoption, retention\u002Fexpansion, or brand\u002Fauthority?\n- What's the conversion action after the webinar? (Book a demo, start a trial, upgrade, attend a follow-up call)\n\n### 3. Reality Check\n- How big is the reachable list \u002F audience, and what channels can promote it? (Email list, paid, partners, social, sales)\n- How long is the runway before the event date?\n- Is there budget for paid promotion, or is this organic-only?\n\n---\n\n## How This Skill Works\n\nThis skill supports three modes.\n\n### Mode 1: Plan From Scratch\nWhen there's no webinar yet — design the whole motion.\n\n1. Lock the promise and pick the format that fits the goal (see `references\u002Fwebinar-formats.md`)\n2. Map the funnel targets backward from the business goal (see funnel math below)\n3. Build the promotion plan across the runway (see `references\u002Fpromotion-playbook.md`)\n4. Design the show-up sequence and the live-to-close moment\n5. Plan the segmented follow-up for attendees vs. no-shows\n6. Deliver: a full webinar plan (use `templates\u002Fwebinar-plan-template.md`), promo calendar, and email\u002Fcopy drafts\n\n### Mode 2: Optimize \u002F Rescue\nWhen a webinar exists or recently ran and the numbers disappoint. Diagnose where the funnel breaks before rewriting anything.\n\n1. Get the actual numbers: invited → registered → showed up → engaged → converted\n2. Score the funnel with `scripts\u002Fwebinar_funnel_scorer.py` to find the weakest stage:\n\n   ```bash\n   # Score a funnel from a JSON file (registrations + attended_live required;\n   # page_visits, cta_clicks, conversions, audience, runtime_min, avg_watch_min optional)\n   python3 scripts\u002Fwebinar_funnel_scorer.py funnel.json\n\n   # Or pipe JSON via stdin\n   cat funnel.json | python3 scripts\u002Fwebinar_funnel_scorer.py -\n\n   # Demo mode on embedded sample data\n   python3 scripts\u002Fwebinar_funnel_scorer.py --sample\n   ```\n\n   Output: a 0-100 scorecard per stage against audience-temperature benchmarks (`customers` \u002F `warm` \u002F `owned_cold` \u002F `paid_cold`), the bottleneck stage flagged, plus a JSON block for downstream use.\n3. Fix the stage that's actually broken — don't rewrite the landing page when the problem is show-up rate\n4. Deliver: diagnosis (where it breaks + why) + targeted fixes ranked by impact\n\n### Mode 3: Evergreen \u002F On-Demand\nWhen turning a one-time webinar into an always-on lead engine.\n\n1. Identify the segment of the webinar with the strongest live-to-close moment\n2. Set up the on-demand registration → watch → follow-up automation\n3. Decide live vs. \"just-in-time\" simulated-live framing (be honest with the audience — fake-live that's obviously fake erodes trust)\n4. Deliver: evergreen funnel map + automated follow-up sequence\n\n---\n\n## The Funnel Math (Plan Backward)\n\nAlways 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.\n\n```\nBusiness goal:        20 sales-qualified opportunities\n÷ attendee→SQO rate   (~10%)         → need 200 engaged attendees\n÷ register→attend     (~35% live)    → need ~570 registrations\n÷ landing-page CVR     (~40%)        → need ~1,425 landing-page visits\n→ promotion plan must drive ~1,425 qualified visits\n```\n\nIf 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\u002Fbenchmarks.md` for stage-by-stage benchmarks by audience type.\n\n---\n\n## The Five Stages\n\n### 1. Registration\nThe landing page has one job: make the value obvious and registering frictionless.\n\n- Lead with the *outcome and the takeaway*, not the agenda. \"Leave with a 90-day pipeline plan\" beats \"Join us to learn about pipeline.\"\n- Name and face of the host\u002Fspeaker — people register for people.\n- Ask for the minimum fields you'll actually use. Every extra field costs registrations.\n- Show the date\u002Ftime in the visitor's timezone, and make the time commitment explicit.\n- If B2B and gating matters, you can ask for company\u002Frole — but know it lowers CVR.\n\n### 2. Show-Up\nThis is where most webinars quietly fail. A registration is a promise people forget. The show-up sequence is non-negotiable.\n\n- Confirmation email immediately, with a one-click calendar add (this alone lifts attendance materially).\n- Reminders: 1 week, 1 day, 1 hour, and \"we're live now.\" The 1-hour and live reminders drive the most attendance.\n- Give a reason to show up *live* vs. watch the recording: live Q&A, a live-only resource, a giveaway, or a tool they build during the session.\n- Pre-event engagement (a question, a poll, a \"what do you want covered?\") increases commitment.\n\n### 3. Live Engagement\nAttention is the currency. Every 10 minutes without interaction, you lose people.\n\n- Hook in the first 2-3 minutes: state the promise and the agenda, then deliver a quick win fast.\n- Interaction every 5-10 minutes: polls, chat prompts, Q&A, live examples.\n- Teach something genuinely useful even if no one buys — earned trust converts later.\n- Watch the drop-off curve; the point where people leave tells you where the content sags.\n\n### 4. Live-to-Close (The Transition)\nThe pitch is a moment, not the whole webinar. Done right it feels like a natural next step, not a bait-and-switch.\n\n- Earn the right first: deliver real value before any offer.\n- Transition explicitly and confidently: \"Here's how to go further \u002F do this with us.\"\n- Make the offer time-bound to the event (attendee-only bonus, deadline) to create a reason to act now.\n- One clear CTA. Repeat it; don't bury it.\n\n### 5. Follow-Up\nThe follow-up converts more than the live event for most B2B webinars. Segment it.\n\n| Segment | Message |\n|---------|---------|\n| Attended + engaged with offer | Strike now — direct path to the CTA, attendee bonus, easy booking |\n| Attended, no action | Recap + the one key takeaway + soft CTA |\n| Registered, no-show | \"Sorry we missed you\" + recording + same offer (this segment is often the biggest) |\n| Watched recording later | Recap + CTA matched to on-demand intent |\n\nSend the recording within 24 hours while it's fresh. See `references\u002Fpromotion-playbook.md` for the full follow-up sequence.\n\n---\n\n## What to Avoid\n\n| ❌ Avoid | Why It Fails |\n|----------|-------------|\n| Promoting the *topic* instead of the *takeaway* | People register for outcomes, not agendas |\n| One reminder email | Show-up rate craters; you need a sequence, not a nudge |\n| No reason to attend live | Everyone \"watches the recording later\" (they don't) |\n| 45 minutes of teaching, then a hard pitch with no transition | Feels like a bait-and-switch; tanks trust and conversion |\n| Treating no-shows as lost | No-shows are often your largest convertible segment |\n| Optimizing registrations as the headline metric | 800 regs and 6 buyers is a failure dressed as a win |\n| Sending the recording a week later | Intent has evaporated; send within 24h |\n| Asking for 8 form fields | Every field beyond the essentials costs registrations |\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked when you see them:\n\n- **Show-up sequence has fewer than 3 reminders** → attendance will suffer. Flag and propose the full 1-week\u002F1-day\u002F1-hour\u002Flive cadence.\n- **No live-only incentive** → registrations will watch \"later\" and never convert. Recommend a live Q&A, attendee bonus, or build-along.\n- **Registration page leads with agenda\u002Flogistics** → reframe around the attendee outcome and takeaway.\n- **No follow-up plan for no-shows** → flag that the largest convertible segment is being ignored.\n- **Funnel goal implies more traffic than the reachable audience can supply** → the plan is mathematically broken; flag before execution and adjust goal\u002Fformat\u002Fbudget.\n- **The offer\u002FCTA appears with no value delivered first** → it will read as a bait-and-switch; recommend earning the transition.\n- **Webinar length over ~60 min for a cold audience** → drop-off risk; recommend tightening or splitting.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| Plan a webinar | Full webinar plan: promise, format, funnel targets (backward math), promotion calendar, show-up sequence, live structure, and follow-up plan |\n| Promote my webinar | Channel-by-channel promotion calendar across the runway + ready-to-send invite, reminder, and social copy |\n| Fix my low attendance | Show-up diagnosis + a complete reminder sequence with timing and copy |\n| Why isn't it converting? | Funnel diagnosis (stage-by-stage with the weakest link identified) + ranked fixes |\n| Write the follow-up | Segmented post-event sequence (engaged \u002F attended \u002F no-show \u002F on-demand) with copy |\n| Score my funnel | 0-100 funnel scorecard from your numbers (via `scripts\u002Fwebinar_funnel_scorer.py`) with the bottleneck stage called out |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n- **Bottom line first** — answer before explanation\n- **What + Why + How** — every finding has all three\n- **Actions have owners and deadlines** — no \"we should consider\"\n- **Confidence tagging** — 🟢 verified \u002F 🟡 medium \u002F 🔴 assumed\n\nFor 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.\n\n---\n\n## Related Skills\n\n- **launch-strategy**: For full product\u002Ffeature launches where a webinar is one tactic among many. Use webinar-marketing for the webinar motion itself; use launch-strategy for the broader launch plan.\n- **email-sequence**: For lifecycle and nurture emails to opted-in subscribers. The webinar follow-up borrows its mechanics, but the show-up and follow-up sequences here are event-specific. Use email-sequence for ongoing drips, not event flows.\n- **paid-ads**: For paid registration-driving campaigns. Use it to build the promotion traffic this skill's funnel math calls for. NOT for the funnel design itself.\n- **page-cro**: For optimizing the registration landing page conversion rate specifically. Pair it with this skill when the bottleneck is landing-page CVR.\n- **content-creator**: For producing the on-demand assets, recap posts, and clips that extend a webinar's life. Good follow-up reuses webinar content.\n- **campaign-analytics**: For measuring webinar performance against pipeline and revenue. Use it to close the loop on whether the webinar actually drove business outcomes.\n- **social-content**: For the organic social promotion of the event across the runway.\n","# Webinar & Virtual Event Marketing\n\nYou 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.\n\nA 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.\n\n## Before Starting\n\n**Check for context first:**\nIf `.claude\u002Fproduct-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.\n\nGather this context (ask conversationally, one section at a time — don't dump every question at once):\n\n### 1. The Event\n- What's the topic, and what's the single promise to the attendee? (What will they be able to do after?)\n- Format: live training, product demo, expert panel, customer story, fireside chat, multi-session summit?\n- Date, length, and platform (Zoom Webinars, Livestorm, Demio, Goldcast, etc.)?\n- Live, on-demand\u002Fevergreen, or live-then-evergreen?\n\n### 2. The Audience & Goal\n- Who is this for? (Role, stage of awareness — cold prospects vs. existing pipeline vs. customers)\n- What's the business goal: net-new leads, pipeline acceleration, product adoption, retention\u002Fexpansion, or brand\u002Fauthority?\n- What's the conversion action after the webinar? (Book a demo, start a trial, upgrade, attend a follow-up call)\n\n### 3. Reality Check\n- How big is the reachable list \u002F audience, and what channels can promote it? (Email list, paid, partners, social, sales)\n- How long is the runway before the event date?\n- Is there budget for paid promotion, or is this organic-only?\n\n---\n\n## How This Skill Works\n\nThis skill supports three modes.\n\n### Mode 1: Plan From Scratch\nWhen there's no webinar yet — design the whole motion.\n\n1. Lock the promise and pick the format that fits the goal (see `references\u002Fwebinar-formats.md`)\n2. Map the funnel targets backward from the business goal (see funnel math below)\n3. Build the promotion plan across the runway (see `references\u002Fpromotion-playbook.md`)\n4. Design the show-up sequence and the live-to-close moment\n5. Plan the segmented follow-up for attendees vs. no-shows\n6. Deliver: a full webinar plan (use `templates\u002Fwebinar-plan-template.md`), promo calendar, and email\u002Fcopy drafts\n\n### Mode 2: Optimize \u002F Rescue\nWhen a webinar exists or recently ran and the numbers disappoint. Diagnose where the funnel breaks before rewriting anything.\n\n1. Get the actual numbers: invited → registered → showed up → engaged → converted\n2. Score the funnel with `scripts\u002Fwebinar_funnel_scorer.py` to find the weakest stage:\n\n   ```bash\n   # Score a funnel from a JSON file (registrations + attended_live required;\n   # page_visits, cta_clicks, conversions, audience, runtime_min, avg_watch_min optional)\n   python3 scripts\u002Fwebinar_funnel_scorer.py funnel.json\n\n   # Or pipe JSON via stdin\n   cat funnel.json | python3 scripts\u002Fwebinar_funnel_scorer.py -\n\n   # Demo mode on embedded sample data\n   python3 scripts\u002Fwebinar_funnel_scorer.py --sample\n   ```\n\n   Output: a 0-100 scorecard per stage against audience-temperature benchmarks (`customers` \u002F `warm` \u002F `owned_cold` \u002F `paid_cold`), the bottleneck stage flagged, plus a JSON block for downstream use.\n3. Fix the stage that's actually broken — don't rewrite the landing page when the problem is show-up rate\n4. Deliver: diagnosis (where it breaks + why) + targeted fixes ranked by impact\n\n### Mode 3: Evergreen \u002F On-Demand\nWhen turning a one-time webinar into an always-on lead engine.\n\n1. Identify the segment of the webinar with the strongest live-to-close moment\n2. Set up the on-demand registration → watch → follow-up automation\n3. Decide live vs. \"just-in-time\" simulated-live framing (be honest with the audience — fake-live that's obviously fake erodes trust)\n4. Deliver: evergreen funnel map + automated follow-up sequence\n\n---\n\n## The Funnel Math (Plan Backward)\n\nAlways 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.\n\n```\nBusiness goal:        20 sales-qualified opportunities\n÷ attendee→SQO rate   (~10%)         → need 200 engaged attendees\n÷ register→attend     (~35% live)    → need ~570 registrations\n÷ landing-page CVR     (~40%)        → need ~1,425 landing-page visits\n→ promotion plan must drive ~1,425 qualified visits\n```\n\nIf 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\u002Fbenchmarks.md` for stage-by-stage benchmarks by audience type.\n\n---\n\n## The Five Stages\n\n### 1. Registration\nThe landing page has one job: make the value obvious and registering frictionless.\n\n- Lead with the *outcome and the takeaway*, not the agenda. \"Leave with a 90-day pipeline plan\" beats \"Join us to learn about pipeline.\"\n- Name and face of the host\u002Fspeaker — people register for people.\n- Ask for the minimum fields you'll actually use. Every extra field costs registrations.\n- Show the date\u002Ftime in the visitor's timezone, and make the time commitment explicit.\n- If B2B and gating matters, you can ask for company\u002Frole — but know it lowers CVR.\n\n### 2. Show-Up\nThis is where most webinars quietly fail. A registration is a promise people forget. The show-up sequence is non-negotiable.\n\n- Confirmation email immediately, with a one-click calendar add (this alone lifts attendance materially).\n- Reminders: 1 week, 1 day, 1 hour, and \"we're live now.\" The 1-hour and live reminders drive the most attendance.\n- Give a reason to show up *live* vs. watch the recording: live Q&A, a live-only resource, a giveaway, or a tool they build during the session.\n- Pre-event engagement (a question, a poll, a \"what do you want covered?\") increases commitment.\n\n### 3. Live Engagement\nAttention is the currency. Every 10 minutes without interaction, you lose people.\n\n- Hook in the first 2-3 minutes: state the promise and the agenda, then deliver a quick win fast.\n- Interaction every 5-10 minutes: polls, chat prompts, Q&A, live examples.\n- Teach something genuinely useful even if no one buys — earned trust converts later.\n- Watch the drop-off curve; the point where people leave tells you where the content sags.\n\n### 4. Live-to-Close (The Transition)\nThe pitch is a moment, not the whole webinar. Done right it feels like a natural next step, not a bait-and-switch.\n\n- Earn the right first: deliver real value before any offer.\n- Transition explicitly and confidently: \"Here's how to go further \u002F do this with us.\"\n- Make the offer time-bound to the event (attendee-only bonus, deadline) to create a reason to act now.\n- One clear CTA. Repeat it; don't bury it.\n\n### 5. Follow-Up\nThe follow-up converts more than the live event for most B2B webinars. Segment it.\n\n| Segment | Message |\n|---------|---------|\n| Attended + engaged with offer | Strike now — direct path to the CTA, attendee bonus, easy booking |\n| Attended, no action | Recap + the one key takeaway + soft CTA |\n| Registered, no-show | \"Sorry we missed you\" + recording + same offer (this segment is often the biggest) |\n| Watched recording later | Recap + CTA matched to on-demand intent |\n\nSend the recording within 24 hours while it's fresh. See `references\u002Fpromotion-playbook.md` for the full follow-up sequence.\n\n---\n\n## What to Avoid\n\n| ❌ Avoid | Why It Fails |\n|----------|-------------|\n| Promoting the *topic* instead of the *takeaway* | People register for outcomes, not agendas |\n| One reminder email | Show-up rate craters; you need a sequence, not a nudge |\n| No reason to attend live | Everyone \"watches the recording later\" (they don't) |\n| 45 minutes of teaching, then a hard pitch with no transition | Feels like a bait-and-switch; tanks trust and conversion |\n| Treating no-shows as lost | No-shows are often your largest convertible segment |\n| Optimizing registrations as the headline metric | 800 regs and 6 buyers is a failure dressed as a win |\n| Sending the recording a week later | Intent has evaporated; send within 24h |\n| Asking for 8 form fields | Every field beyond the essentials costs registrations |\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked when you see them:\n\n- **Show-up sequence has fewer than 3 reminders** → attendance will suffer. Flag and propose the full 1-week\u002F1-day\u002F1-hour\u002Flive cadence.\n- **No live-only incentive** → registrations will watch \"later\" and never convert. Recommend a live Q&A, attendee bonus, or build-along.\n- **Registration page leads with agenda\u002Flogistics** → reframe around the attendee outcome and takeaway.\n- **No follow-up plan for no-shows** → flag that the largest convertible segment is being ignored.\n- **Funnel goal implies more traffic than the reachable audience can supply** → the plan is mathematically broken; flag before execution and adjust goal\u002Fformat\u002Fbudget.\n- **The offer\u002FCTA appears with no value delivered first** → it will read as a bait-and-switch; recommend earning the transition.\n- **Webinar length over ~60 min for a cold audience** → drop-off risk; recommend tightening or splitting.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| Plan a webinar | Full webinar plan: promise, format, funnel targets (backward math), promotion calendar, show-up sequence, live structure, and follow-up plan |\n| Promote my webinar | Channel-by-channel promotion calendar across the runway + ready-to-send invite, reminder, and social copy |\n| Fix my low attendance | Show-up diagnosis + a complete reminder sequence with timing and copy |\n| Why isn't it converting? | Funnel diagnosis (stage-by-stage with the weakest link identified) + ranked fixes |\n| Write the follow-up | Segmented post-event sequence (engaged \u002F attended \u002F no-show \u002F on-demand) with copy |\n| Score my funnel | 0-100 funnel scorecard from your numbers (via `scripts\u002Fwebinar_funnel_scorer.py`) with the bottleneck stage called out |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n- **Bottom line first** — answer before explanation\n- **What + Why + How** — every finding has all three\n- **Actions have owners and deadlines** — no \"we should consider\"\n- **Confidence tagging** — 🟢 verified \u002F 🟡 medium \u002F 🔴 assumed\n\nFor 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.\n\n---\n\n## Related Skills\n\n- **launch-strategy**: For full product\u002Ffeature launches where a webinar is one tactic among many. Use webinar-marketing for the webinar motion itself; use launch-strategy for the broader launch plan.\n- **email-sequence**: For lifecycle and nurture emails to opted-in subscribers. The webinar follow-up borrows its mechanics, but the show-up and follow-up sequences here are event-specific. Use email-sequence for ongoing drips, not event flows.\n- **paid-ads**: For paid registration-driving campaigns. Use it to build the promotion traffic this skill's funnel math calls for. NOT for the funnel design itself.\n- **page-cro**: For optimizing the registration landing page conversion rate specifically. Pair it with this skill when the bottleneck is landing-page CVR.\n- **content-creator**: For producing the on-demand assets, recap posts, and clips that extend a webinar's life. Good follow-up reuses webinar content.\n- **campaign-analytics**: For measuring webinar performance against pipeline and revenue. Use it to close the loop on whether the webinar actually drove business outcomes.\n- **social-content**: For the organic social promotion of the event across the runway.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1780272000000,"1.0.0","marketing","main","26a049c61e6bda33cca8f5e7c1fcdcd20681221f","Ads-Outreach-and-Sales\u002Fwebinar-marketing","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS","https:\u002F\u002Fgithub.com\u002Fibada0410","2026-10-15 17:21:48",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ibada0410\u002FCLAUDE-SKILLS --skill webinar-marketing",{"tool":41,"command":42},"bunx","bunx skills add ibada0410\u002FCLAUDE-SKILLS --skill webinar-marketing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ibada0410\u002FCLAUDE-SKILLS --skill webinar-marketing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FAds-Outreach-and-Sales\u002Fwebinar-marketing\u002FSKILL.md",true,[49,55,59,63,67,73],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Fevals.json","REFERENCE","参考文档",2048,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FAds-Outreach-and-Sales\u002Fwebinar-marketing\u002Fevals\u002Fevals.json",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fbenchmarks.md",3332,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FAds-Outreach-and-Sales\u002Fwebinar-marketing\u002Freferences\u002Fbenchmarks.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fpromotion-playbook.md",5158,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FAds-Outreach-and-Sales\u002Fwebinar-marketing\u002Freferences\u002Fpromotion-playbook.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fwebinar-formats.md",3618,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FAds-Outreach-and-Sales\u002Fwebinar-marketing\u002Freferences\u002Fwebinar-formats.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fwebinar_funnel_scorer.py","SCRIPT","脚本",6837,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FAds-Outreach-and-Sales\u002Fwebinar-marketing\u002Fscripts\u002Fwebinar_funnel_scorer.py",{"path":74,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":75,"sourceHtmlUrl":76},"templates\u002Fwebinar-plan-template.md",2716,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FAds-Outreach-and-Sales\u002Fwebinar-marketing\u002Ftemplates\u002Fwebinar-plan-template.md",[78,88,96,104,112,120],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"01M7F0YW5WXY39G4W3203E8PHN","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":87},"01M7F0YGDEVB7BCSJX8V91XK15","eu-ai-act-reviewer","Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions. Use for EU AI Act issue-spotting, not final legal or compliance decisions.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":87},"01M7F0Y1GYY34HD1WM5EWYB80Z","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":87},"01M7F0W4SJJY8Z345JZH9901RD","academy-guide","Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: \"how do I\", \"how can I\", \"getting started with\", \"what can Claude do\", \"teach me\", \"learn to use\"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":87},"01M7F0W0X5YSTSFS77CFA5P5KJ","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":87},"01M7F0VV4P1HYHG44P0K48C4Q7","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]