mood-board-builder

I took a look at your mood-board-builder skill and noticed the PDA score pulled things down significantly—you've got solid foundational logic, but the way you're structuring the examples and guidance could be way more token-efficient for users actually building with this.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 58/100, which lands you in F territory. This is based on Anthropic's best practices for progressive disclosure architecture and utility. Your strongest pillar is Spec Compliance (11/15)—the YAML frontmatter is solid—but Utility (10/20) and PDA (15/30) are dragging the overall score down. The skill addresses a real problem, but it reads more like a concept than something Claude can actually execute.

What's Working Well

• Valid structure: Your frontmatter is clean and follows conventions correctly
• Clear workflow intent: The 5-step framework (Inspiration → Direction → Refinement → Feedback → Finalization) makes conceptual sense
• Real use case: Mood boards are genuinely useful for creative alignment in teams
• Navigation: Sections are well-labeled and easy to scan

The Big One: No Actual Templates or Examples

This is killing your Utility score. You mention "Figma/Canva board layout, PDF deck template" but provide zero actual artifacts. When Claude uses this skill, it has no concrete reference for what a "mood board" output should actually look like.

Fix: Create a references/ directory with:

• references/sample-mood-board.md - A fully formatted markdown example showing vision statement, 3 color palettes (with hex codes), typography selections, and annotated reference images
• references/feedback-template.md - Actual stakeholder feedback form users can paste
• `re...