battlecard-system

I took a look at your battlecard-system skill and noticed it's tackling a pretty niche problem—helping developers quickly synthesize competitive intelligence. With a score of 51, there's real potential here, but the execution needs some tightening up around how you're structuring the progressive disclosure and making the core value prop clearer upfront.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 51/100, which puts you in F territory—needs significant work. Based on Anthropic's best practices for skill design, here's the breakdown: Spec Compliance is your strongest pillar at 11/15, but Utility (8/20) and Progressive Disclosure Architecture (13/30) are dragging you down hard. The core issue is that you're describing a framework without actually providing the tools people need to execute it.

What's Working Well

• Clean spec compliance – Your frontmatter is valid YAML with all required fields, and the naming convention (hyphen-case) is spot-on.
• Logical organization – Headers are clear and the five-step framework flows reasonably well; it's easy to scan what the skill is about.
• Objective tone – You're avoiding marketing fluff and keeping the voice instructional, which is the right call for a skill that's supposed to be actionable.

The Big One: Missing Reference Files (High Priority)

This is your biggest lever for improvement. You mention three critical templates in the Templates section—Battlecard layout, Objection handling matrix, and Competitive win/loss capture form—but you haven't actually provided them. This is a massive utility gap. Someone reading your skill walks away with a conceptual framework but no actual starting point to build from.

Fix: Create a `re...