ceo-advisor
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.
Install with Tessl CLI
npx tessl i github:majiayu000/claude-skill-registry-data --skill ceo-advisor79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 86%
↑ 1.79xAgent success when using this skill
Validation for skill structure
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-based and keyword-based 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 for strategic decision-making, organizational development, and stakeholder management' plus specific tools) AND when with explicit 'Use when...' clause covering multiple trigger scenarios. | 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
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive CEO advisory framework but suffers from verbosity and lack of actionable specificity. While it references useful scripts and external documents, the main content is largely conceptual frameworks and checklists that Claude could generate without instruction. The skill would benefit from significant trimming and moving detailed content to reference files.
Suggestions
Reduce the main file to a concise overview (under 100 lines) with quick-start commands and clear pointers to reference files for detailed frameworks
Move detailed content like the daily schedule template, weekly rhythm, stakeholder matrix, and book recommendations to separate reference files
Add validation steps to multi-step workflows (e.g., 'After running strategy_analyzer.py, verify output contains X before proceeding')
Remove obvious leadership concepts Claude already knows (vision development definitions, basic stakeholder categories) and focus on project-specific tooling and unique frameworks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extensive and includes some useful frameworks, but is overly verbose with many sections that state obvious leadership concepts Claude already knows (e.g., 'Vision Development: Define 10-year aspirational future', basic stakeholder definitions). The daily schedule template and weekly rhythm sections add bulk without unique value. | 2 / 3 |
Actionability | Provides some concrete guidance with script commands and references to specific files, but most content is high-level frameworks and checklists rather than executable instructions. The Python script calls are actionable, but the bulk of the content describes concepts rather than providing copy-paste ready guidance. | 2 / 3 |
Workflow Clarity | Multi-step processes like the Strategic Planning Cycle and Board Meeting Preparation Timeline are listed but lack validation checkpoints or feedback loops. The crisis management section has levels but no explicit verification steps. Decision checklist is present but doesn't specify how to validate completion. | 2 / 3 |
Progressive Disclosure | References external files appropriately (executive_decision_framework.md, board_governance_investor_relations.md, leadership_organizational_culture.md), but the main file is a monolithic wall of text with 400+ lines that could be better split. Much content that should be in reference files is inline. | 2 / 3 |
Total | 8 / 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 | |
- 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.