executive-ebr-kit

I found your executive brief report generator while reviewing skills in the grading pipeline—the concept of automating EBR templates is solid, but the current implementation has some structural gaps that are keeping it from reaching its potential.

Links:

• GitHub
• SkillzWave Marketplace

The TL;DR

You're at 44/100, which is an F grade. This is based on Anthropic's 5-pillar skill rubric covering token efficiency, ease of use, spec compliance, writing clarity, and practical utility. Your strongest area is Spec Compliance (11/15), but you're really struggling with Progressive Disclosure Architecture (8/30)—that's where the most opportunity lives.

What's Working Well

• Valid frontmatter structure – Your YAML is clean and follows conventions correctly
• Clear naming conventions – Using hyphen-case properly (executive-ebr-kit)
• Focused scope – The skill has a clear purpose around EBR/QBR frameworks rather than trying to do too much

The Big One: Missing Templates and References

This is your biggest blocker. You mention six-slide decks, memos, and action logs in the "Templates" section (lines 21-24), but they don't actually exist anywhere. You're describing what the skill could do without providing the actual assets that make it work.

The fix: Create a references/ directory with:

• references/ebr-deck-template.md – Actual 6-slide outline with talking point placeholders
• references/ebr-memo-template.md – Async EBR memo format
• references/action-log-template.md – Decision/action tracker template

Then update your SKILL.md to reference these files directly. This alone would jump you +10 points because it transforms the skill from conceptual to actually usable.

Other Things Worth Fixing

1. No execution workflow – Your "Framework" section lists five concepts but no step-by-step process. Add a "Workflow" section with numbered steps: gather metrics → identify risks → draft narrative → customize → deliver. This fixes the "how do I actually use this?" problem. (+8 points)

2. Vague trigger phrases – Your description says "template pack for executive business reviews" but doesn't include actual triggers like "create EBR", "prepare QBR", or "build business review deck". Specific triggers make skills discoverable. (+6 points)

3. Zero examples – Create references/example-ebr.md showing a complete input (customer context, metrics) and output (filled template). Developers need to see what success looks like. (+5 points)

4. Inconsistent voice – You mix gerunds ("Preparing quarterly reviews") with imperatives ("Lead with outcomes"). Pick one and stick with it throughout. (+2 points)

Quick Wins

• Add trigger phrases to description field immediately
• Create the three template files in references/
• Add a numbered workflow section
• Include one complete example with sample data
• Standardize to imperative voice throughout

These changes would realistically get you to ~72/100 with relatively straightforward additions. The templates are the load-bearing wall here—everything else scales off that foundation.

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.