metis-strategy/executive-slide-builder
Narrative-first skill for building executive-quality strategy presentations. Operates in two modes: Narrative Mode for story structure, sequencing, and executive copy; and Elevation Mode for translating systems-level or technical content into C-Suite-ready business language using a structured workflow (value stream framing, naming conventions, time horizons, traceability). Hands off to metis-pptx for brand-compliant .pptx generation. Triggers on executive storytelling, narrative arc, strategic framing, or technical-to-executive translation requests.
78
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that covers all key dimensions thoroughly. It provides specific capabilities, extensive natural trigger terms, clear 'what' and 'when' guidance, two operational modes, and even explicit negative triggers to prevent conflicts with related skills. The only minor note is the use of second-person 'Use this skill' at the start, but the rubric penalizes first/second person voice under specificity, and the phrasing here is more instructional to Claude than conversational, so the impact is minimal.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: executive storytelling, narrative structure, strategic framing, translating technical content into C-Suite-ready language. Also specifies two distinct modes (Narrative Mode and Elevation Mode) with clear descriptions of what each does. | 3 / 3 |
Completeness | Clearly answers both 'what' (executive storytelling, narrative structure, strategic framing, translating technical to business language, two modes) and 'when' (explicit trigger phrases listed, plus a 'Use this skill for...' opening clause). Also includes negative triggers ('Do NOT trigger on') to prevent misuse, which adds to completeness. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'executive overview,' 'narrative arc,' 'structure the business case,' 'make this more executive,' 'elevate for the C-Suite,' 'translate to business language,' 'too technical,' 'systems-level to executive-level,' and the slash command /executive-slide-builder. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (executive-level narrative and framing). Explicitly disambiguates from a related skill (metis-pptx) by stating 'Do NOT trigger on create a deck or build slides,' which directly reduces conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has excellent workflow clarity with well-defined modes, sequenced steps, validation checkpoints, and a clear scope boundary with metis-pptx. However, it is severely over-long and verbose, explaining many concepts Claude already understands (executive communication principles, active voice, what acronyms are). The content would benefit enormously from aggressive compression and splitting detailed reference material into separate files.
Suggestions
Compress the Five-Layer Model, Common Failure Modes table, Writing Style section, and So What Test to 2-3 lines each — Claude already understands executive communication principles and doesn't need them explained at length.
Move the entire Elevation Pre-Processing section (Client Setup + Steps E1-E6) into a separate reference file like `references/elevation-workflow.md` and link to it from the main skill, keeping only a brief summary inline.
Remove advisory/philosophical guidance like 'separate content truth from presentation truth' and 'let the visual do the heavy lifting' — these describe mindset, not actions, and Claude can infer them from the concrete steps.
Consolidate the three quality gate sections (Standard Quality Bar, Completeness Check, So What Test) into a single concise checklist rather than three separate prose sections with overlapping concerns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~400+ lines. It extensively explains concepts Claude already understands (what executive communication is, what 'active voice' means, what a value stream is). Many sections could be compressed to a fraction of their size — e.g., the Five-Layer Model table, the Common Failure Modes table, and the Writing Style section all explain things Claude inherently knows. The 'So What Test' and quality gates sections belabor points that could be stated in 2-3 lines each. | 1 / 3 |
Actionability | The skill provides a structured workflow with named steps and a concrete build brief format, which is genuinely actionable. However, much of the guidance is advisory/philosophical rather than executable ('separate content truth from presentation truth,' 'let the visual do the heavy lifting'). The build brief template is the strongest actionable element, but many steps describe what to think about rather than what to do. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with two distinct modes (Elevation and Narrative), explicit branching logic, numbered steps (E1-E6 for elevation, 1-10 for the main workflow), quality gates as validation checkpoints, and a clear stop point at Step 9 with explicit instructions not to proceed further. The Completeness Check and So What Test serve as feedback loops before finalizing output. | 3 / 3 |
Progressive Disclosure | The skill references external files appropriately (references/elevation-reference.md for detailed templates, metis-pptx for execution) and has clear section headers. However, the main file itself is monolithic — much of the elevation pre-processing detail, the common failure modes table, and the quality gates could be split into reference files. The inline content is far too long for a SKILL.md overview. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (634 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents