webinars

I checked out your webinars skill and noticed you've got a pretty solid foundation here—the 73/100 score reflects some real strengths in the core concept, but there are a few gaps that, if addressed, could push this into stronger territory for developers actually looking to build webinar content.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 73/100, solid C territory. This is based on Anthropic's best practices for agentic skills. Your strongest pillar is Spec Compliance (12/15)—the YAML frontmatter is clean and valid. The biggest drag is Progressive Disclosure Architecture (20/30) and Utility (14/20). You're leaving points on the table in practical guidance and examples.

What's Working Well

• Spec compliance is tight — Your frontmatter is valid and naming conventions are correct. The single-file structure works fine for this scope.
• Clear framework — The event blueprint with numbered steps (Event Blueprint → Content Flow → Engagement Tools → Optimization) gives users a real roadmap.
• Consistent terminology — "Webinar" stays consistent throughout; no confusion about what you're teaching.
• Actionable timeline — You provide concrete numbered steps like "Run a full tech rehearsal" rather than vague abstractions.

The Big One: Missing Template Examples

This is what's holding you back most. Your Templates section lists five template types—landing page copy, speaker briefing, run-of-show—but provides zero actual examples. Users have to guess what you want.

Why it matters: Templates are supposed to be plug-and-play shortcuts. Without examples, they're just ideas. This tanks your Utility score and forces developers to reverse-engineer what you meant.

The fix: Create a `references/templat...