calendar-governance

I was curious how you'd approach calendar conflict resolution at scale — your skill tackles a genuinely tricky coordination problem, but the implementation feels like it's fighting against some design constraints that are dragging the score down to 69.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 69/100, solidly in D territory. This is based on Anthropic's progressive disclosure and skill design best practices. Your strongest area is Writing Style (8/10) — the prose is clean and consistent. The real drag is Progressive Disclosure Architecture (18/30) and Ease of Use (18/25) — you've got good concepts, but they're buried without the structural support to make them work.

What's Working Well

• Clear, consistent terminology — "cadence," "coverage," and "governance" are used precisely throughout, which helps readers stay oriented
• Solid foundational framework — The five-part structure (Cadence Rules, Timezone Coverage, Approval Workflow, Blackout Management, Audit & Change Control) is logically sound and addresses real GTM pain points
• Objective, instructional tone — No marketing fluff, no hand-waving. You're telling people what to do, not selling them on why

The Big One: Missing Reference Files

This is what's killing your PDA score. You mention templates three times — "Calendar governance checklist," "Timezone coverage heatmap," "Change-log template" — but don't actually provide them. They're just listed as text.

Why it matters: Templates are where the skill does something. Right now, someone reading this still has to invent the wheel. You've given them the blueprint but not the tools.

The fix: Create references/templates.md with actual, copy-paste-ready con...