save-play-library

I took a quick look at your save-play-library skill and noticed you're tackling a pretty common pattern—managing persistent state for interactive applications—but there's quite a bit of room to tighten up how you're presenting the solution to developers.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 58/100, which lands in F territory. This is based on Anthropic's Progressive Disclosure Architecture standards. Your strongest area is Spec Compliance (11/15)—the frontmatter and naming conventions are solid. But Utility is dragging you down hard at 10/20, and PDA is sitting at 15/30 because you're missing actual reference files and templates.

What's Working Well

• Valid YAML frontmatter - Your metadata structure is clean and follows conventions correctly
• Consistent terminology - Using "play" throughout keeps things coherent
• Reasonable conceptual framework - The 5-step structure (Signal Definition → Play Blueprint → Feedback Loop) makes logical sense for the workflow
• Appropriate scope - You're not overengineering; the skill focuses on a specific use case

The Big One: Missing Templates and Examples

This is your biggest blocker. You list three templates—"Play card", "Experiment tracker", "Post-play retrospective form"—but only as bullet points. Developers have no actual templates to reference, no fill-in-the-blank examples, no input/output pairs showing what a real save play looks like.

The fix: Create a references/ directory with three actual markdown files:

• references/play-card-template.md - A fillable template with fields like Trigger, Action Steps, Owner, KPI, Timeline
• references/experiment-tracker.md - Column headers and a sample row showing control vs. test cohor...