ceo-advisor
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 trigger term coverage and completeness, with a clear 'Use when...' clause containing numerous 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 presentations, structures investor updates, develops strategic roadmaps, designs org charts and reporting structures' instead of 'organizational development and stakeholder management'.
Add differentiating language to reduce overlap with general business or management skills, e.g., 'Specifically for C-suite and founder-level decisions, not general project management or team-level planning.'
| 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 advisory skill with good progressive disclosure and useful frameworks (metrics dashboard, output artifacts, proactive triggers, C-suite integration matrix). However, it leans more toward conceptual guidance than concrete, executable instructions — there are no worked examples of actual outputs, and the workflows lack explicit validation steps. Some content could be trimmed where it states things Claude would already know.
Suggestions
Add a concrete worked example for at least one output artifact (e.g., a sample strategic options matrix or board narrative skeleton) to improve actionability.
Define explicit step-by-step workflows with validation checkpoints for key processes like board meeting prep or fundraising readiness assessment, rather than just referencing them.
Trim explanatory framing that Claude already knows (e.g., 'Culture is what people do when you're not in the room', 'Your board can be your greatest asset or your biggest liability') to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some content that Claude already knows or could infer (e.g., 'Culture is what people do when you're not in the room', the list of key questions, and some explanatory framing). The tables and lists are efficient, but the overall document could be tightened by ~20-30%. | 2 / 3 |
Actionability | The skill provides structured frameworks (metrics dashboard, output artifacts table, proactive triggers) which are useful, but most guidance is conceptual rather than executable. The two bash commands at the top reference scripts that may or may not exist, and there's no concrete example of actually producing an artifact (e.g., a sample strategic options matrix or board narrative template). | 2 / 3 |
Workflow Clarity | There are implicit workflows (strategic planning cycle, communication quality loop, proactive triggers) but no explicit step-by-step sequences with validation checkpoints. The board prep flow is mentioned but not detailed. The communication section references a quality loop but delegates it to another file without showing the actual steps. | 2 / 3 |
Progressive Disclosure | The skill effectively uses progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to specific resource files (executive_decision_framework.md, board_governance_investor_relations.md, leadership_organizational_culture.md) and related skill directories (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 | |
- Repository
- alirezarezvani/claude-skills
- Commit
967fe01
- Reviewed
Table of Contents
Is this your skill?
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.