advocacy-programs

I just realized how much advocacy programs depend on consistent messaging across different channels—your skill seems to tackle that coordination problem head-on, though the execution feels like it's still finding its rhythm at 72/100.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 72/100, solidly in C territory. This is based on Anthropic's skill best practices framework. Your strongest area is Spec Compliance (12/15)—the YAML frontmatter and naming conventions are tight. The biggest drag? Utility (12/20) and Progressive Disclosure (20/30). You're describing a framework, but you're not giving people the actual scaffolding to execute it.

What's Working Well

• Spec compliance is solid. Your frontmatter has all required fields with valid YAML—that foundation is clean.
• Focused scope. At 32 lines, you're respecting token economy. No bloat, no rambling.
• Consistent terminology. You nail the language—"advocates," "advisory boards," "case studies"—it tracks throughout without wobbling.
• Logical structure. The numbered framework (Define → Build → Activate → Measure) gives people a mental model to hang onto.

The Big One

Templates are mentioned but not delivered. This is killing your utility score (-4 points easy).

You reference three things that would actually unlock this skill:

• Advocate scoring sheet + roster
• Program brief outline
• Activation checklist

But they don't exist. Right now, someone reading this gets a framework and has to invent the templates themselves. That's work they should do, not setup work.

Fix: Create a references/ folder with three concrete markdown templates:

• advocate-scoring-template.md — actual fields (Name, Company, Influence Score 1-1...