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 content:

• A real checklist with cadence questions (e.g., "Min posts/day per channel: ___")
• A heatmap template showing channel × region × daypart
• A change-log format for late edits

Then update SKILL.md to say "See references/templates.md for ready-to-use templates." That's a +5 point swing right there.

Other Things Worth Fixing

1. Add trigger phrases to the description — Right now it says "Use to enforce cadence rules..." but doesn't say when. Add: "Use when asked to 'audit calendar,' 'check timezone coverage,' or 'review posting schedule.'" Helps with discoverability (+2 points).

2. Convert the framework to actionable steps — "Define Cadence Rules" is good, but add sub-bullets: "List each channel → Set min/max posts/day → Mark quiet hours → Verify alignment with paid media." Right now it reads like a concept; it should read like a checklist (+3 points).

3. Add one worked example — Show input/output for a real scenario: "Q1 product launch, 3 regions, 5 channels → Output: timezone-optimized calendar with blackout dates and approval deadlines." Concrete beats abstract (+4 points).

4. Add a validation loop — Under "Audit & Change Control," add: "Run governance check: Export calendar → Verify no timezone gaps → Flag conflicts → Fix violations → Re-audit." You mention auditing but not how to verify compliance (+2 points).

Quick Wins

• Highest impact: Create references/templates.md with actual templates (+5 points)
• Next: Add trigger phrases to description and convert framework to numbered steps (+5 points combined)
• Then: Add one worked example and a validation workflow (+6 points combined)

That's +16 points within reach — puts you at 85 territory (B grade) with focused effort.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.