webinar-plan

webinar-plan is a skill for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 30 tokens per session (1,487 once invoked), scanned A, original, MIT.

An end-to-end plan for running a webinar or online event. It covers the agenda, registration copy, promotion, presenter guidance, audience interaction, follow-up, and event-day tasks.

In plain words
What is it for?
Use it to organise educational events, product demonstrations, lead-generation sessions, or other virtual events from initial idea through follow-up.
Why use it?
It puts the preparation and follow-up work in one plan instead of treating the live event as the only task. It also includes measures for judging whether the event met its goals.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

Part of the digital-marketing-pro plugin — 164 skills, 5 commands, 24 agents shipped together

Good fit Use it to organise educational events, product demonstrations, lead-generation sessions, or other virtual events from initial idea through follow-up.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/digital-marketing-pro/webinar-plan
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add indranilbanerjee/digital-marketing-pro --skill webinar-plan
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 164 skills, 5 commands, 24 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for webinar-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/webinar-plan/github.svg)](https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/webinar-plan)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/webinar-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/webinar-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for webinar-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/webinar-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/webinar-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,487 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.01487
Opus 5.5 $0.00012 $0.00595
Sonnet 5.5 $0.00006 $0.00297
Haiku 4.5 $0.00003 $0.00149

Measured 4d ago against content hash b4254835341b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

webinar-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/webinar-plan/SKILL.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/digital-marketing-pro:webinar-plan

Purpose

Plan a webinar or virtual event from concept to post-event follow-up, including content structure, promotion strategy, registration optimization, engagement tactics, and measurement framework. Produces a complete execution package that a team can implement without further strategic planning.

Input Required

The user must provide (or will be prompted for):

  • Topic/theme: Subject matter and angle for the webinar — what specific problem or opportunity will be addressed
  • Target audience: Who should attend — role, seniority, industry, company size, experience level, and pain points
  • Objectives: Primary goal — lead generation, education, product demo, thought leadership, customer retention, or partner enablement
  • Preferred platform: Webinar tool in use or under consideration (Zoom, Teams, Webex, GoToWebinar, Livestorm, StreamYard, etc.)
  • Date/time: Proposed date and time with timezone (or ask for optimal scheduling recommendation based on audience)
  • Speakers: Presenters, panelists, or hosts — internal team members and/or external guests with their expertise areas
  • Budget for promotion: Available spend for driving registrations — paid ads, sponsorships, influencer partnerships, etc.
  • Expected attendance: Target registration and attendance numbers for goal-setting and promotion planning
  • Content assets available: Existing slide decks, research reports, demos, or content that can be repurposed for the webinar
  • Follow-up goals: What should happen after the webinar — sales meetings booked, free trial signups, content downloads, community joins

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
  2. Define webinar format: Select the best format based on objectives, audience preferences, and speaker strengths — presentation, panel discussion, interactive workshop, product demo, AMA, fireside chat, or hybrid format with multiple segments
  3. Create content outline with timing: Build a minute-by-minute run of show — opening hook, speaker introductions, content segments with transitions, audience interaction points (polls, Q&A breaks), and closing CTA with time allocations for each block
  4. Design registration page copy: Write headline, subheadline, 3-5 key takeaway bullets, speaker bios with credibility markers, urgency elements (limited spots, countdown), and social proof (past attendee quotes, company logos) optimized for conversion
  5. Build multi-channel promotion plan: Create a coordinated promotion strategy across email sequences, organic social posts, paid ads (LinkedIn, Meta, Google), partner/speaker cross-promotion, blog/website banners, community outreach, and internal employee advocacy
  6. Create presenter prep materials: Develop speaker brief with key talking points, slide structure recommendations, audience profile context, brand voice reminders, Q&A preparation, and technical setup/rehearsal checklist
  7. Design attendee engagement strategy: Plan interactive elements — specific poll questions tied to content, Q&A facilitation approach, chat prompts to spark discussion, breakout room activities (if applicable), live resource sharing, and real-time feedback mechanisms
  8. Plan post-event sequence: Design the complete follow-up funnel — recording availability timeline, segmented email sequences for attendees vs. no-shows, lead scoring criteria based on engagement, sales handoff process for high-intent leads, and content repurposing plan (blog post, social clips, podcast episode, infographic)
  9. Define success metrics: Set targets for registrations, show-up rate, engagement rate (poll participation, questions asked, chat activity), leads generated, pipeline influenced, and attendee satisfaction — with industry benchmark comparisons
  10. Create day-of checklist: Build a comprehensive run-of-day timeline covering tech setup and testing, dry run schedule, backup plans for speaker or tech failures, moderator duties minute-by-minute, recording confirmation, and immediate post-event actions

Read the full file on GitHub · 64 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago Changed · -115 tokens per session b4254835341b
  2. 9d ago First seen · 64 lines · 145 tokens per session scan A 03967c4ff15b

Subscribe to this mod's changes

webinar-plan is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (882 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,487 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-05.