executive-briefs

I've analyzed the executive-briefs skill at a score of 63/100. Here's a developer-to-developer opening:

This skill tackles a real pain point—turning complex financial data into something executives can actually read in 5 minutes. The framework is solid and the use case is clear, but the implementation feels more like consulting advice than a Claude-specific skill. You're losing points on utility because there are no actual templates, examples, or validation steps to work with.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 63/100, landing in D territory. The good news: your Spec Compliance is solid at 11/15. The rough spots: Utility is dragging you down at 11/20, and your Progressive Disclosure Architecture needs restructuring (18/30). You've got the bones of something useful here—just needs meat on them.

What's Working Well

• Spec compliance is clean – Valid YAML, proper naming conventions, required fields all present
• Real-world problem – Addressing executive communication is a legitimate use case that teams actually need
• Logical framework structure – Your 5-step approach (Audience Lens → Story Arc → Numbers → Drivers → Actions) is sensible and teachable
• Grep-friendly layout – The structure is searchable and organized, which earned you a small bonus

The Big One: Missing Concrete Templates & Examples

Here's what's killing your utility score: You list templates ("One-slide executive summary", "Board memo outline") but never show what they actually look like. A user reads your skill and thinks "okay, what do I actually write?" and hits a wall.

The Fix: Create a references/ subdirectory with actual template files:

• `references/templates/executive-summary....