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.md – A real markdown template with placeholder sections
• references/templates/board-memo.md – Another actual example
• references/examples/ – Before/after pairs showing rough revenue data → finished brief

Then update your main SKILL.md to link to these and show one short example inline. This alone gets you +4 points and makes the skill actually usable.

Other Things Worth Fixing

1. No workflow steps – Your framework describes what to include but not how to execute. Add a numbered workflow: "1. Ask user for audience type (board vs ELT vs investor). 2. Pull variance data from forecast-modeling outputs. 3. Generate headline..." (+3 points)

2. Generic trigger phrases – Your description says "craft concise revenue updates" with no explicit triggers. Add: "Use when asked to 'create executive brief', 'write board memo', 'ELT update', 'revenue summary for leadership'" (+2 points)

3. No validation criteria – After generating a brief, how do you know it's good? Add a checklist: "Headline states forecast vs target in first sentence. Key metrics defined in footnotes. Action items have owners and dates." (+3 points)

4. Missing layered structure – Everything's in one 31-line file. Split into overview (main SKILL.md) + deep dives (references/) to save tokens and make it progressively disclosable (+3-4 points)

Quick Wins

• Add actual template files (biggest impact, +7 points if done right)
• Explicit trigger phrases in metadata (+2 points)
• Numbered workflow steps (+3 points)
• Validation checklist (+3 points)

Do these four and you're looking at 63 → 80+.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.