positioning

I came across your positioning skill and noticed the spec compliance could use some attention—the core concepts are solid, but there's room to tighten up how the guidelines flow together to prevent confusion for users.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 62/100, firmly in D territory (needs work). This is based on Anthropic's agent skills best practices. Your strongest area is Spec Compliance (12/15) — the YAML structure is clean and the naming follows conventions. But Utility (10/20) is dragging you down hard. The framework reads high-level and abstract when it should give people actionable steps they can actually execute.

What's Working Well

• Solid YAML structure — Your frontmatter is valid with all required fields, which shows attention to detail
• Clear naming and organization — The skill name follows convention, and the 5-step framework (Audience → Problem → Differentiation → Proof → Messaging) has a logical flow
• Real GTM problem — You're solving something teams actually need (positioning statements and message houses aren't trivial)

The Big One: Missing Templates and Examples

Here's what's holding you back: you mention "templates" and "examples" throughout the skill, but you haven't actually provided them. When someone uses this skill, they get a framework but no concrete reference material to work from. That's a -7 point hit right there.

The fix: Create a references/ directory with actual, usable templates:

• references/positioning-canvas.md — A filled-in example showing Audience, Problem, Differentiation, etc.
• references/message-house.md — Template structure with sample content -...