exec-briefing-kit

I took a look at exec-briefing-kit and noticed the skill tackles a genuinely practical problem—turning raw data into something an executive can actually digest. The 66/100 score suggests you've got the core idea solid, but there's room to tighten up how you're guiding developers through the implementation.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 66/100, solidly in D territory. This is graded against Anthropic's skill best practices. Your Spec Compliance (11/15) is the strongest pillar—the YAML structure and naming conventions are tight. But Progressive Disclosure Architecture (18/30) and Utility (12/20) are dragging the score down. The skill reads more like a framework outline than a usable guide with concrete examples and templates.

What's Working Well

• Valid structure: Frontmatter is clean, hyphen-case naming follows conventions perfectly
• Clear 5-step framework: The Story Spine → Metric Snapshot → Action Items flow is logical and addresses real exec communication needs
• Practical focus: No fluff—the tips section (Lead with actions, Include guardrails, Surface confidence) are genuinely useful
• Tight scope: At 31 lines, you're not over-explaining, which is good for token efficiency

The Big One: Missing Reference Files & Examples

This is your biggest blocker. Right now, templates are described but not actually provided:

- 3-slide deck outline (headline, KPI spine, action plan).
- Memo template with summary → insights → actions.

A developer reading this has to invent these templates themselves. You should create:

• references/deck-template.md – actual 3-slide structure with placeholders
• references/memo-template.md – sample memo showing summary→insights→actions format
• references/example-briefing.md – a complete worked example (e.g., "Here's how to brief the board on Q4 revenue growth")

This single fix could bump you +7 points (up to 73/100), moving from D to C territory.

Other Things Worth Fixing

1. No trigger phrases in the description – Replace generic "Template for packaging revenue analytics..." with specific activation phrases: "Use when asked to 'create exec briefing', 'prep board deck', 'build revenue readout', or 'write ELT presentation'". (+2 points)

2. Missing validation checklist – Add a "Quality Gate" section before delivery: "Can the exec decide in 5 minutes? Are owners/dates on all actions? Is confidence level explicit?" Gives developers a run→check→fix loop. (+3 points)

3. Inconsistent voice – You mix imperative ("Lead with actions") with nouns ("Story Spine – headline..."). Pick one: "Build story spine with headline, context..." reads more consistent. (+2 points)

4. Vague terminology – You say "execs" and "board" and "ELT" interchangeably without context. Clarify once: "Use 'exec briefing' for C-level, 'board narrative' for governance meetings, 'ELT readout' for executive leadership team." (+1 point)

Quick Wins

Hit these first for fast wins:

• Add trigger phrases to frontmatter description (easy, +2 pts)
• Create one solid example briefing in references/example-briefing.md (+4 pts)
• Build the three template files listed above (+3 pts)
• Add a validation checklist at the end (+3 pts)

Knock out the top two and you're looking at 72/100. Get all of them done and you're solidly in B territory (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.