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
• references/validation-checklist.md — Concrete steps for testing messaging with customers

This immediately signals you've done the work, gives users something to copy and customize, and bumps your Utility score significantly.

Other Things Worth Fixing

1. Weak discovery triggers — Your description says "structuring positioning statements" but agents search for specific phrases like "create positioning" or "build message house." Add 5-6 specific trigger phrases to your description so it actually gets matched. (+4 points)

2. Swap gerunds for imperatives — Lines like "Kicking off new products" should be "Use when starting new products or entering markets." Imperatives are clearer and more actionable. (+2 points)

3. Turn the framework into instructions — Step 1 currently reads "Audience & Problem – ICP, pain, current workaround." Make it executable: "Define Audience: Interview 5-10 target users. Document ICP criteria (role, company size, pain points)..." This is the difference between a checklist and a roadmap. (+5 points)

Quick Wins

• Add those three reference files (~15 minutes of work, +7 points)
• Expand your description with specific trigger phrases (+4 points)
• Rewrite framework steps as imperative instructions, not bullet points (+5 points)
• Add a validation checklist so people know how to test their output (+3 points)

That's +19 points of low-hanging fruit. You'd jump to 81/100 and land solidly in B territory.

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.