CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

70

1.68x
Quality

67%

Does it follow best practices?

Impact

86%

1.68x

Average score across 3 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/c-level/ceo-advisor-7d5c3bf3/SKILL.md

The canonical home for this skill is ceo-advisor in majiayu000/claude-skill-registry

SKILL.md
Quality
Evals
Security

Quality

Content

38%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-formatted and broad but functions as an inlined executive-leadership encyclopedia rather than a skill: much of it is generic knowledge Claude already has, the concrete hooks (scripts, reference frameworks) point to files missing from the bundle, and no validation or feedback loops anchor any workflow. Structure exists at the section level, but progressive disclosure is broken by dead references and heavy inlining.

Suggestions

Create the referenced files (references/executive_decision_framework.md, references/board_governance_investor_relations.md, references/leadership_organizational_culture.md) and scripts/strategy_analyzer.py, scripts/financial_scenario_analyzer.py — or remove the pointers — so every link in the body resolves to real bundle content.

Move generic-knowledge sections (Daily CEO Schedule, Succession Planning, Personal Development, Tools & Resources, book lists, pitch deck structure) out of SKILL.md into a one-level-deep reference file, keeping SKILL.md as a lean overview with clearly signaled links per topic.

Trim or delete content Claude already knows (stakeholder matrices, work-life integration tips, standard pitch-deck order) so the body carries only CEO-specific frameworks, and add explicit validation checkpoints to the decision and board-preparation workflows (e.g., 'confirm data gathered before Go/No-Go', 'verify board package completeness at T-1 week').

DimensionReasoningScore

Conciseness

The ~500-line body inlines large amounts of generic executive common knowledge Claude already has — a 'Daily CEO Schedule Template' (6:00 AM personal development), 'Pitch Deck Structure' (Problem/Solution/Market...), book recommendations ('Good to Great', 'High Output Management'), and work-life tips ('Protected family time', 'Exercise routine') — matching 'noticeably verbose; several unnecessary explanations or padded sections'. It is not a 3 because the padding is extensive and systematic rather than occasional: whole sections (Succession Planning, Personal Development, Tools & Resources) restate knowledge Claude needs no skill to provide.

2 / 5

Actionability

There is some concrete guidance (runnable commands 'python scripts/strategy_analyzer.py', a decision checklist, board prep timeline T-4/T-2/T-1/T-0), but the commands reference scripts that do not exist in the bundle and the 'Review references/executive_decision_framework.md' pointers lead to nonexistent files, leaving the reader without the actual frameworks. This matches 'some concrete guidance but incomplete; missing key details' rather than 4, where guidance would be mostly executable and self-contained.

3 / 5

Workflow Clarity

Sequences exist (Strategic Planning Cycle Q1-Q4, board preparation timeline, crisis response levels, decision checklist) but there are no validation checkpoints or feedback loops anywhere — e.g., the Go/No-Go checklist has criteria but no 'verify against data before deciding' step, and the board package timeline ends at distribution with no post-meeting follow-through. This matches 'steps listed but validation gaps' rather than 4, and the dead script/reference links further break the would-be workflow.

3 / 5

Progressive Disclosure

The body points to references/executive_decision_framework.md, references/board_governance_investor_relations.md, references/leadership_organizational_culture.md, and two scripts, but the bundle contains no references/, scripts/, or assets/ directories — the references are dead, so none of the promised detail is actually one level deep. Combined with an inlined ~500-line monolith covering a dozen topics that clearly belong in separate files, this matches 'minimal structure; content that clearly belongs in separate files is inlined'.

2 / 5

Total

10

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person, concrete about deliverables, and equipped with an explicit and rich 'Use when' trigger clause covering both scenarios and user-mentioned keywords. The main gaps are a few missing natural trigger terms (e.g., fundraising, pitch, earnings call) and some overly broad triggers that create minor overlap risk with adjacent leadership/strategy skills.

DimensionReasoningScore

Specificity

The description names the domain and several concrete deliverables ('strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks') in third person, matching 'lists several specific actions; minor gaps in coverage'. It falls short of a 5 because phrases like 'Executive leadership guidance for' are less concrete than executable actions, and it does not name file types or specific inputs/outputs.

4 / 5

Completeness

It explicitly answers 'what' ('Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer...') and 'when' with a concrete 'Use when' trigger clause listing specific scenarios and user-mentioned terms, matching the 5 anchor exactly. It is clearly above the 4 anchor because the 'when' is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

The 'Use when' clause covers many natural phrases ('planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions') plus explicit keywords ('CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy'), matching 'good keyword coverage; a few natural terms missing'. It is not a 5 because common variations like 'fundraising', 'pitch deck', 'earnings call', or 'succession planning' are absent despite being core topics in the body.

4 / 5

Distinctiveness Conflict Risk

The CEO/executive niche ('CEO, board meetings, investor updates, executive strategy') is mostly distinct with clear triggers, matching 'mostly distinct; minor overlap risk with closely related skills'. It is not a 5 because broad triggers like 'planning strategy', 'strategic decision-making', and 'organizational culture' could overlap with general leadership, COO, or strategy-planning skills.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (518 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 9 missing

Warning

Total

14

/

16

Passed

Repository

majiayu000/claude-skill-registry

Path

skills/c-level/ceo-advisor-7d5c3bf3/SKILL.md

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.