Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.
74
Quality
67%
Does it follow best practices?
Impact
86%
1.68xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/c-level/ceo-advisor/SKILL.mdQuality
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 a well-crafted skill description that excels across all dimensions. It provides specific capabilities (strategy analyzer, financial modeling, governance frameworks), uses natural executive-level terminology, and includes a comprehensive 'Use when...' clause with both action triggers and keyword triggers. The description clearly carves out an executive leadership niche that distinguishes it from general business or management skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: 'strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks' along with specific use cases like 'planning strategy, preparing board presentations, managing investors, developing organizational culture.' | 3 / 3 |
Completeness | Clearly answers both what (executive leadership guidance with specific tools like strategy analyzer, financial modeling, governance frameworks) AND when with explicit 'Use when...' clause covering multiple trigger scenarios and keywords. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'CEO, strategic planning, board meetings, investor updates, organizational leadership, executive strategy, board presentations, managing investors.' These are terms executives and their teams would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear executive/C-suite niche with distinct triggers like 'CEO, board meetings, investor updates, board governance.' Unlikely to conflict with general business or project management skills due to specific executive-level terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is significantly over-engineered and verbose, explaining concepts Claude already understands (CEO responsibilities, stakeholder management basics, generic scheduling). While it does reference external tools and files appropriately, the main document should be a concise overview pointing to detailed references rather than a comprehensive CEO handbook. The actionable elements (script commands, file references) are buried in excessive explanatory content.
Suggestions
Reduce the main skill to ~50-75 lines focusing only on: Quick Start commands, when to use each tool/reference, and project-specific conventions Claude wouldn't know
Move all framework content (stakeholder matrices, decision frameworks, board management details) into the referenced files rather than duplicating inline
Remove generic CEO knowledge (scheduling templates, book recommendations, basic definitions) that Claude already possesses
Add validation steps to workflows - e.g., after running strategy_analyzer.py, specify how to verify the output is correct before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with extensive content Claude already knows (what a CEO does, basic stakeholder management concepts, book recommendations, generic scheduling templates). The Keywords section is redundant with frontmatter, and most frameworks are common knowledge that don't need explanation. | 1 / 3 |
Actionability | Provides some concrete guidance with script commands and file references, but most content is descriptive frameworks and checklists rather than executable instructions. The Python script calls are actionable, but the bulk of content describes concepts rather than providing specific implementation steps. | 2 / 3 |
Workflow Clarity | Some workflows are sequenced (Strategic Planning Cycle, Board Meeting Preparation Timeline), but they lack validation checkpoints and feedback loops. The decision checklist is present but doesn't specify what to do if validation fails or how to verify success. | 2 / 3 |
Progressive Disclosure | References external files appropriately (references/executive_decision_framework.md, etc.), but the main file contains far too much inline content that should be split into reference documents. The Quick Start section is good, but the 400+ lines following it should be distributed across referenced files. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (518 lines); consider splitting into references/ and linking | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
6213d1a
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.