messaging-frameworks

I was checking out your messaging-frameworks skill and noticed you're taking a pragmatic approach to GTM messaging—the score landed at 70/100, which puts you in C territory. That tells me the fundamentals are solid, but there are some gaps in how you're delivering the value.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 70/100, graded against Anthropic's Claude Skills best practices. Your strongest area is Spec Compliance (12/15)—the YAML frontmatter and naming conventions are clean. Weakest is Utility (12/20)—you're describing a framework but not showing how to actually use it with examples and templates. Ease of Use and PDA both need work too (19/25 and 18/30).

What's Working Well

• Spec compliance is solid – Your frontmatter is valid, the hyphen-case naming follows convention, and the structure is clean
• Clear framework steps – The 5-step progression (Headline, Pillars, Proof Points, CTA, Guardrails) is logical and easy to follow
• Consistent terminology – You stick with "message house," "pillars," "proof points" throughout, which makes it cohesive
• Navigation is good – The sections are well-organized with clear headers; no confusion about what goes where

The Big One: Missing Templates and Examples

This is what's killing your Utility score. You mention templates in the skill but don't provide them:

"Templates: Message house diagram (headline, pillars, proof), FAQ builder (question, short answer, long answer, owner), Talking point checklist per spokesperson."

Here's the fix: Create a references/ directory at the skill's root level with actual template files:

• references/message-house-template.md – A blank template users can copy/paste
• `references/...