exec-briefing

I took a look at your exec-briefing skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 93/100, solid A-grade territory. This is based on Anthropic's skill best practices. Your writing style is chef's kiss (10/10) — clean, imperative, no fluff. Progressive Disclosure Architecture is nearly perfect at 28/30. The weak spot is Spec Compliance at 11/15, mainly because your description is missing trigger phrases that help people discover and invoke the skill.

What's Working Well

• Writing Style is Excellent — You're using imperative form correctly and keeping things concise without marketing speak. That's harder than it looks.
• Progressive Disclosure — The SKILL.md overview with a referenced template file is the right call. You're not dumping everything on one page.
• Clear Framework — The numbered steps for QBR/EBR briefings give developers a concrete workflow to follow. The template examples matching documented needs shows thoughtful design.
• Consistent Terminology — Using "briefing" and "executive" consistently throughout makes the skill easy to understand at a glance.

The Big One: Add Trigger Phrases to Your Description

This is the one that'll move your needle. Right now your description says:

Use to craft concise executive updates, agendas, and follow-up logs for QBR/EBR sessions.

It needs actual trigger phrases so people can find and invoke it. Change it to something like:

Performs exec briefing operations. Use when asked to "exec briefing", "create exec briefing", "write executive briefing", "QBR briefing", or "EBR agenda".

This is a +2 point swing (takes you to 95/100) because it directly affects spec_compliance and discoverability. Trigger phrases are how agents know when to use your skill.

Other Things Worth Fixing

1. Add validation steps — Your "Feedback Loops" score was 3/4. Right now you recommend follow-ups, but you don't include explicit steps for validating the briefing worked. Add a quick validation checklist at the end of your template (e.g., "Does the agenda fit in 30 minutes? Are action items clear?").

2. Consider a brief TOC — Not a blocker at your file length, but if you expand the template section, a table of contents would help navigation (+1 potential point).

3. Lean into optional YAML fields — You're not using any optional fields in frontmatter. Adding category: "sales" or tags: ["briefing", "QBR", "executive"] could help with discoverability and organization.

Quick Wins

• Add trigger phrases to description → +2 points
• Add validation steps to template → +1 point
• (Optional) Add optional YAML fields → +0.5 points

You're really close to a 95+. The trigger phrases fix is the one that matters most.

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.