Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.
82
69%
Does it follow best practices?
Impact
90%
1.28xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./c-level-advisor/ceo-advisor/SKILL.mdQuality
Discovery
82%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 solid description that excels in completeness and trigger term coverage, with a clear 'Use when...' clause and many natural keywords. Its main weakness is that the capability descriptions remain at a high/abstract level rather than listing concrete actions, and some terms could overlap with adjacent business skills. The description uses proper third-person voice throughout.
Suggestions
Replace abstract category nouns with concrete actions, e.g., 'Drafts board presentation outlines, structures investor update narratives, builds organizational culture frameworks, evaluates strategic trade-offs' instead of 'strategic decision-making, organizational development'.
Add differentiating specifics that separate this from general business/management skills, such as mentioning C-suite-specific concerns like 'executive compensation decisions, board governance, cap table management, or Series A/B fundraising strategy'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (executive leadership) and mentions several areas like strategic decision-making, organizational development, and stakeholder management, but these are still fairly high-level categories rather than concrete, specific actions. It doesn't list discrete tasks like 'draft board presentations' or 'create investor update decks' — instead it uses abstract nouns. | 2 / 3 |
Completeness | Clearly answers both 'what' (executive leadership guidance for strategic decision-making, organizational development, stakeholder management) and 'when' with an explicit 'Use when...' clause listing multiple trigger scenarios and terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'CEO', 'strategic planning', 'board meetings', 'investor updates', 'organizational leadership', 'executive strategy', 'fundraising', 'board presentations', 'managing investors'. These are terms a user would naturally use when seeking this type of guidance. | 3 / 3 |
Distinctiveness Conflict Risk | While the executive/CEO focus provides some distinctiveness, terms like 'strategic planning', 'organizational development', and 'stakeholder management' could overlap with general business consulting, project management, or HR-focused skills. The niche is moderately defined but not razor-sharp. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured strategic advisory skill with strong progressive disclosure and good organizational frameworks (metrics dashboard, C-suite integration matrix, output artifacts). Its main weaknesses are moderate verbosity with some content Claude already knows (general leadership wisdom) and a reliance on external reference files for the actual executable workflows, leaving the main skill somewhat abstract in terms of concrete step-by-step actionability.
Suggestions
Trim general leadership truisms Claude already knows (e.g., 'Culture is what people do when you're not in the room', basic stakeholder prioritization) to improve conciseness.
Include at least one concrete, step-by-step workflow inline (e.g., board meeting prep or fundraising readiness assessment) with explicit validation checkpoints rather than deferring all detail to reference files.
Make the Quick Start scripts more actionable by showing expected input/output or noting prerequisites, since referencing scripts without context reduces their utility.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some content that's general leadership knowledge Claude already possesses (e.g., 'Culture is what people do when you're not in the room', the list of key questions, stakeholder priority ordering). The tables and frameworks add value but some sections could be tightened. | 2 / 3 |
Actionability | The skill provides structured frameworks (metrics dashboard, output artifacts table, proactive triggers) and references scripts, but most guidance is strategic/conceptual rather than executable. The bash commands at the top reference scripts that may not exist, and the actual decision-making processes are delegated to reference files rather than being concretely specified here. | 2 / 3 |
Workflow Clarity | The strategic planning cycle and stage-adaptive horizons provide some sequencing, and the proactive triggers section adds useful checkpoints. However, multi-step processes like fundraising, board prep, and strategic planning lack explicit step-by-step workflows with validation checkpoints — they mostly point to reference files for the actual procedures. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to specific documents (executive_decision_framework.md, board_governance_investor_relations.md, leadership_organizational_culture.md) and related skills (culture-architect/, board-deck-builder/). Navigation is straightforward. | 3 / 3 |
Total | 9 / 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 |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
f567c61
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.