executive-briefing-kit

I took a look at your executive briefing kit skill and noticed you're trying to tackle a pretty broad problem—distilling complex information into executive-friendly formats. With a score of 64/100 (D grade), there's solid foundation here, but the spec compliance and progressive disclosure architecture could use some refinement to really make this sing for users juggling information overload.

Links:

• GitHub
• SkillzWave Marketplace

The TL;DR

You're at 64/100, which puts you in the "needs work" territory. This is based on Anthropic's progressive disclosure and skill best practices. Your Writing Style is your strongest pillar (8/10)—the language is clear and mostly objective. But Utility (9/20) and Progressive Disclosure Architecture (18/30) are dragging the score down, which means users can understand what you're saying but won't get a lot of practical value from it.

What's Working Well

• Writing is concise and instructional – You avoid marketing fluff and keep language direct ("Lead with business impact", "Frame as threat or opportunity")
• Clear section structure – The split between Framework, Templates, and Tips makes logical sense and is easy to navigate
• Real problem being addressed – Executive communication is a genuine pain point; you're not solving for a problem that doesn't exist
• Consistent terminology – Terms like "exec brief," "ELT," and "action register" are used consistently throughout

The Big One: Missing Reference Files & Templates

This is your biggest leverage point. Right now, everything lives in a single SKILL.md file, which kills your progressive disclosure architecture score (18/30). You mention templates ("One-page exec brief + appendix outline," "Slide template with signal cards") but don't actually provide them.

The fix: Create two reference files:

• references/templates.md – Actual markdown templates users can copy/paste and customize
• references/examples.md – Real sample executive briefs showing the framework in action

This alone should bump you +10 points to 74. Users will immediately see "oh, this is what a good brief looks like," instead of just reading abstract instructions.

Other Things Worth Fixing

1. Add trigger phrases to your description – Right now it's generic: "Framework for packaging competitive updates into executive-ready narratives..." Add specific triggers: "Use when preparing 'executive briefing', 'board update', 'QBR brief', or 'war room update'." This improves discoverability and hits your Spec Compliance (+2 points).

2. Your framework needs "how-to" steps, not just concepts – "Story Arc – context, signal summary..." is conceptual but not actionable. Rewrite as: "Start with Story Arc: Draft 2-3 sentence context statement. List 3-5 key signals. Frame as threat or opportunity. List 2-4 recommended plays." This clarifies Ease of Use (+5 points).

3. Add a quality checklist – No feedback loops means users can't validate whether their brief is actually executive-ready. Include: "Review checklist: [ ] Executive summary fits on one page [ ] Each recommendation has owner and due date [ ] Business impact quantified." This adds Utility value (+4 points).

4. Tighten voice consistency – You use gerund form ("Preparing board/ELT updates") when imperative is clearer ("Use when preparing board/ELT updates"). Small but visible across the skill.

Quick Wins

Most impactful first:

• Create references/templates.md with actual copyable templates → +10 points
• Create references/examples.md with sample briefs → +3 points
• Add trigger phrases to description → +2 points
• Rewrite framework steps as actionable instructions → +5 points

Hit those and you're looking at 84/100 pretty easily.

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.