CtrlK
BlogDocsLog inGet started
Tessl Logo

webinar-marketing

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).

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is webinar-marketing in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, actionable body with a strong backward-funnel model and clear three-mode workflows. The main defect is bundle integrity: all five referenced references/scripts/templates files are absent, so the progressive-disclosure layer the skill depends on does not actually exist.

Suggestions

Ship the missing bundle files the body points to — references/webinar-formats.md, references/promotion-playbook.md, references/benchmarks.md, templates/webinar-plan-template.md, and scripts/webinar_funnel_scorer.py — or remove the references and inline the essential detail so no link dangles.

Collapse the overlap between 'The Five Stages', 'What to Avoid', and 'Proactive Triggers' so each point appears once; keep one as the reference and have the others point to it, trimming the recap redundancy.

Add an explicit validate-then-proceed checkpoint to the Plan From Scratch and Evergreen modes (e.g., 'run the funnel math; if reachable audience < required visits, stop and adjust goal/format/budget before drafting copy') to match the Optimize mode's feedback loop.

DimensionReasoningScore

Conciseness

Mostly lean and punchy with no basic-concept padding ('A webinar is a funnel, not an event'), but the 'What to Avoid' table and 'Proactive Triggers' section recap guidance already stated in 'The Five Stages', which could be trimmed. Minor recap redundancy — not verbose enough for a 3, not pristine enough for a 5.

4 / 5

Actionability

Concrete, specific guidance throughout: a quantified backward funnel-math model, exact show-up cadence (1 week/1 day/1 hour/live), a segmented follow-up table with messages, and a copy-paste script block with --sample and stdin usage. Not a 5 because some steps are directional ('design the show-up sequence') without inline templates.

4 / 5

Workflow Clarity

Three clearly numbered modes (Plan, Optimize, Evergreen) with a diagnose-then-fix sequence and a funnel-math reality-check checkpoint ('If the math says you need 5,000 visits and your list is 2,000... fix the goal now'). Not a 5 because not every mode has an explicit validate-then-proceed feedback loop with error-recovery steps.

4 / 5

Progressive Disclosure

The body is well-sectioned and signals references clearly with backtick paths ('see references/promotion-playbook.md', 'scripts/webinar_funnel_scorer.py', 'templates/webinar-plan-template.md'), but none of the five referenced files exist in the bundle — every reference is a dead end, so the second detail level is missing and navigation fails.

3 / 5

Total

15

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: third-person voice, concrete actions, an explicit 'Use when' trigger clause with many natural synonyms, and clear distinctiveness/NOT boundaries against neighboring skills. No meaningful gaps; every dimension lands at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('plan, promote, run, or improve a webinar or virtual event to generate and convert demand', 'diagnose and fix it') plus the explicit funnel stages (registration, promotion, show-up, live engagement, live-to-close, post-event nurture), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers what (the funnel motion and its stages) and when (a 'Use when the user mentions...' clause with concrete trigger phrases, plus a 'Also use when they have a webinar that isn't converting' diagnostic case).

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms users actually say ('webinar', 'virtual event', 'workshop', 'masterclass', 'fireside chat', 'roundtable', 'show-up rate', 'on-demand webinar'), well beyond a single keyword.

5 / 5

Distinctiveness Conflict Risk

Clear niche with explicit boundary statements ('Distinct from launch-strategy... and email-sequence', 'NOT for in-person field events logistics, and NOT for generic lifecycle email'), minimizing wrong-skill triggering.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 9 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.