creating-skills

I was curious how you approached the skill creation workflow—there's a lot of implicit knowledge that's hard to document, but your rubric breaks it down in a way that actually makes sense for builders.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 84/100, solid B-grade territory. This is graded against Anthropic's skill architecture standards—specifically how well you structure information layering, discoverability, and practical utility. Your strongest area is actually Utility (18/20)—the skill solves real problems with good feedback loops. Weakest is Spec Compliance (12/15), mainly because your description only includes 1-2 trigger phrases when it could be more specific.

What's Working Well

• Reference architecture is chef's kiss—you're using the references/ directory exactly right (design-patterns.md, skill-activation.md, two-stage-review.md) to keep SKILL.md focused. That's the PDA sweet spot most skills miss.
• Discoverability is tight—"Use when: create skill, update skill, SKILL.md format, verify.py" in your description means agents will actually activate this at the right time. Trigger terms are specific, not vague.
• Verification workflow actually loops—Step 6 includes iteration (run→check→fix), and you reference verify.py for diagnostics. That's a feedback loop that actually works instead of just "here's a checklist."

The Big One: Missing Complete End-to-End Example

This is what's costing you the most utility points (could gain ~3 points here). Right now you have scattered examples—frontmatter format at lines 184-198, skill anatomy at lines 51-62—but no complete working skill example showing all pieces together.

A builder reading this needs to see: "Here's a real, minimal skill with SKI...