cxo-briefing-kit

I took a look at your cxo-briefing-kit skill and noticed you're trying to solve the executive communication problem—helping people distill technical complexity into talking points that actually land with leadership. The 73-point grade suggests the core idea is solid, but there are some structural gaps in how the skill guides users through that process.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

TL;DR

You're at 73/100, which is C-territory—adequate with some gaps. Your writing style is the strongest pillar (8/10), but Progressive Disclosure Architecture and Utility are dragging things down. The issue isn't the concept; it's that the skill tells people what to do but doesn't show them how to do it effectively.

What's Working Well

• Solid voice consistency – You're using imperative language throughout ("articulate risks," "specify decisions"), which keeps things directive and clear.
• Real use cases – Your "When to Use" section nails the actual scenarios (preparing sponsor briefings, logging decisions after reviews). That's the good stuff that makes people reach for a skill.
• Clean structure – A 32-line skill that doesn't bloat with unnecessary cruft. You respect the user's time.

The Big One: Template Examples Are Missing

Here's what's killing your utility score (14/20): You list three template types—the one-slide exec update, briefing memo outline, and decision log—but you don't show what they actually look like. Users can guess the structure, but guessing beats the whole point of a skill.

Fix this: Create a references/templates.md file with actual minimal examples. Show structure, not just concept:

## One-Slide Exec Update
**Headline:** [Deal name] – [Stage] – [Confidence %]
**Key Metric:** $[...