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:** $[ARR] at [margin]%
**Top Risk:** [Risk + mitigation]
**Ask:** [Specific approval/resource needed]

## Decision Log Entry
| Date | Decision | Owner | Outcome | Next Review |
|------|----------|-------|---------|-------------|
| 2025-01-24 | Expand TAM from Mid-Market | VP Sales | Approved | Q1 earnings call |

This alone adds 4 points and suddenly your skill moves from "framework" to "actionable toolkit."

Other Things Worth Fixing

1. Add trigger phrases to your description – Right now it says "Use to package concise executive updates." Better: "Create CXO briefings and executive summaries. Use when preparing board updates, executive sponsor presentations, or C-suite stakeholder briefings." This helps discoverability and matches how people actually search.

2. Add a validation step – Your framework stops at "Action & Follow-up." Add: "Review & Validate – confirm executive priorities are addressed, verify numbers with finance, test the one-breath explanation." Quality feedback loops bump utility score.

3. Tighten the Tips section – "Pair with pursuit-governance to keep cadences consistent" is vague. Say: "Use pursuit-governance skill to schedule regular executive reviews and maintain consistent communication cadence." More specific = more useful.

4. Switch passive voice – "Preparing executive sponsor briefings" → "Prepare executive sponsor briefings." Small change, cleaner voice.

Quick Wins

• Add concrete template examples in references/templates.md (+4 points)
• Update description with trigger phrases (+2 points)
• Add validation/review step to framework (+2 points)
• Tighten cross-reference guidance (+1 point)

These four fixes get you to 82/100, firmly in B territory, with utility and ease of use both ticking up meaningfully.

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.