editorial-calendar

I checked out your editorial-calendar skill and the content management angle is solid, but I'm curious why the spec focuses more on workflow than on the actual calendar data model—seems like there's room to tighten that connection for users trying to understand what they're getting into upfront.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

TL;DR

You're at 74/100, solid C-grade territory. This is based on Anthropic's skill best practices. Your strongest area is Spec Compliance (12/15)—the YAML is clean and valid. Weakest is Utility (13/20)—you've got the framework down but missing the actual templates and validation logic that would make this genuinely useful.

What's Working Well

• Spec compliance is tight – Valid YAML frontmatter, correct kebab-case naming, required fields all there. That's the foundation done right.
• Clear workflow stages – The five-step framework (map → assign → document → groom → remind) is intuitive and shows you've thought through the cadence governance problem.
• Good trigger coverage – "pillar calendars," "approvals," "cadence governance" activates for the right use cases. People will find this when they need it.
• Concise writing – At 31 lines, you're not wasting words. Every section adds signal without filler.

The Big One: Missing Template Artifacts

This is what's holding you back from a B. You list templates (calendar view, intake brief, board schema) but don't provide them. No references/ directory, no actual field definitions, no examples.

Why it matters: A user reads "Monday/Asana/Notion board schema for pipeline tracking" and has zero idea what fields you're talking about or how to set it up. They have to guess or go ask Monday's docs instead of your ...