CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cs-webinar

/cs:webinar — Webinar & virtual-event marketing workflow. Plan a webinar from scratch (sized backward from the business goal), rescue one whose numbers disappointed (score the funnel, fix the broken stage), or turn a past webinar into an evergreen on-demand lead engine. Covers the full funnel: registration, promotion runway, show-up, live engagement, live-to-close, and segmented follow-up. Treats a webinar as a funnel, not an event.

60

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/cs-webinar/SKILL.md
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, lean command entry point whose diagnostic half (score/rescue) is genuinely executable thanks to concrete commands, sample JSON, and benchmark tables. Its weaknesses are externalized substance — the plan template and the scorer script are pointed at but not bundled or inlined — and prose-implied rather than explicit sequencing for the plan mode.

Suggestions

Ship the scorer script (or its essential logic) inside the skill's bundle, or inline the scoring formula/benchmark logic in SKILL.md so the score/rescue workflow works when the external marketing-skill repo is absent.

Add one sample scorer output block (per-stage rates vs. benchmark + named bottleneck) so Claude knows exactly how to interpret results and what the ranked fixes should look like.

Convert the `plan` mode's prose description into an explicit numbered sequence (intake → lock promise/format → backward sizing → runway → show-up/live-to-close/follow-up → deliverable via template), including the 'required visits > reachable audience' checkpoint as an explicit validation step.

DimensionReasoningScore

Conciseness

The body is dense and purposeful — intake as a 3-row table, benchmarks as a table, a worked funnel-math example, and runnable commands with no space wasted explaining what a webinar is. Minor trimmable padding exists: the 7-line 'Trigger Phrases' section largely restates the frontmatter description, and 'Anti-Patterns Rejected' slightly overlaps the funnel-math rationale. It sits above anchor 3 (which tolerates genuinely unnecessary explanation) but below anchor 5 because a few sections restate the same idea ('Treats a webinar as a funnel' appears in both the framing and the anti-patterns).

4 / 5

Actionability

The scorer workflow gives copy-paste-ready commands ('python3 marketing-skill/skills/webinar-marketing/scripts/webinar_funnel_scorer.py funnel.json', stdin piping, no-args demo) plus a complete sample input JSON with required/optional fields, and the backward funnel math is a concrete worked example (20 SQOs → ~1,425 visits). It is not a 5 because the `plan` and `evergreen` modes stay abstract ('Walks the intake, locks the promise + format...') and defer entirely to a template file that is not in the bundle, and no sample scorer output is shown despite it being described as the diagnostic centerpiece.

4 / 5

Workflow Clarity

Modes are enumerated with exact invocations, a 3-question intake defines the entry decision, and the workflow section sequences score/rescue correctly (run scorer → read per-stage rates vs. benchmark → named bottleneck → ranked fixes). The funnel math includes a real checkpoint ('If the required visits exceed the reachable audience, fix the goal, format, or promotion budget now'). Not a 5: the plan mode's multi-step flow (intake → promise/format → sizing → runway → deliverable) is implied in prose rather than explicitly sequenced, and there is no validate-and-retry loop around the scorer output (e.g., what to do when input JSON is malformed or a stage rate is missing).

4 / 5

Progressive Disclosure

Section organization is clean (When To Run / When NOT To Run / Modes / Intake / Workflow / Benchmarks), but the skill has no bundle at all: the entire workflow depends on external files — the scorer script, the webinar plan template, and the sibling `webinar-marketing` SKILL.md — none of which exist under any referenced path in this bundle, and none of the core scorer logic or template structure is inlined as a fallback. That is 'structure present but the content that should back the references is absent,' fitting anchor 3 rather than anchor 4 (where references are mostly clear AND the supporting placement works).

3 / 5

Total

15

/

20

Passed

Description

71%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.

A strong, specific description that names three concrete workflow modes with their mechanics and the full funnel scope. Its main gap is the missing explicit 'Use when...' trigger clause — usage situations are only implied — and a few natural trigger synonyms are absent.

Suggestions

Add an explicit trigger clause, e.g., 'Use when planning or promoting a webinar/virtual event, when registrations or show-up disappointed, or when converting a past webinar into an on-demand asset.'

Fold one or two missing natural synonyms ('webcast', 'virtual summit', 'live demo', 'masterclass') from the body's Trigger Phrases into the description so users who don't say 'webinar' still match.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with parenthetical mechanics: 'Plan a webinar from scratch (sized backward from the business goal)', 'rescue one whose numbers disappointed (score the funnel, fix the broken stage)', 'turn a past webinar into an evergreen on-demand lead engine', then enumerates the covered funnel stages (registration, promotion runway, show-up, live engagement, live-to-close, segmented follow-up). Coverage within the domain is comprehensive and every verb is concrete, matching anchor 5; it is not anchor 4 because there are no meaningful gaps in the capability listing.

5 / 5

Completeness

The 'what' is explicit and detailed (three workflow modes plus funnel scope), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by phrases like 'rescue one whose numbers disappointed'. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3, which also matches anchor 3 ('clear what but when is missing or only weakly implied') rather than anchor 4 ('when' explicitly stated).

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'webinar', 'virtual-event', 'evergreen', 'on-demand', 'registration', 'promotion', 'follow-up', 'lead engine' — terms a user would actually say when needing this skill. A few natural variants are missing (e.g., 'webcast', 'online seminar', 'virtual summit', 'live demo', 'masterclass' — several of which appear only in the body's Trigger Phrases, not the description), which fits anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and webinar-specific ('webinar & virtual-event marketing workflow', funnel-stage vocabulary), so it is unlikely to trigger for unrelated skills. Minor overlap risk remains with closely related marketing skills (email nurture for 'follow-up', general lead-gen for 'lead engine', and the launch-strategy skill the body itself cross-references), which fits anchor 4 rather than anchor 5's minimal-conflict carve-out.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/cs-webinar/SKILL.md

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.