community-program-matrix

I've been looking at how you're structuring community programs—the matrix approach is clever for mapping stakeholder needs to program benefits, but I'm noticing the skill itself could use some refinement to make it genuinely useful for teams actually building these programs.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 63/100, solidly in D territory. This is based on Anthropic's skill best practices around architecture and usability. Your strongest area is Spec Compliance (11/15)—the YAML frontmatter is solid. The real drag is Progressive Disclosure Architecture (16/30) and Utility (11/20). You've got the right bones here, but the skill needs more meat on them.

What's Working Well

• Valid YAML structure – Your frontmatter is correct, which is the foundation everything else sits on
• Clear framework thinking – The 5-step approach (persona grid, channels, cadence, measurement, iterations) shows you understand the problem space
• Consistent terminology – "Persona," "channel," "cadence" are used uniformly throughout, which makes it easy to follow
• Realistic scope – You're not trying to solve everything; you've picked a focused problem

The Big One: Missing Reference Files and Templates

Here's what's killing your PDA score: you mention templates—spreadsheet/Notion templates, slide decks, resource planning worksheets—but they don't actually exist. They're just listed as bullet points. This violates the whole idea of Progressive Disclosure Architecture, which is about layering content efficiently.

Fix: Create a references/ directory with actual templates:

• references/program-grid-template.md – A Markdown table showing a 3x4 matrix (3 personas × 4 channels) with exa...