executive-ceo
Executive CEO Agent. 비전/전략 수립, 경영 의사결정, 조직 리더십을 담당합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill executive-ceo35
Quality
19%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/executive-ceo/SKILL.mdDiscovery
17%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 description provides a high-level overview of executive leadership functions but lacks the specificity and explicit trigger guidance needed for effective skill selection. The Korean terminology is formal and abstract rather than using natural language users would employ. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms like 'business strategy', 'executive decision', 'company vision', 'leadership guidance', or 'strategic planning'
Replace abstract categories with concrete actions such as 'draft strategic plans', 'analyze business decisions', 'create vision statements', 'develop organizational structures'
Include both Korean and English trigger terms to capture how users might naturally phrase requests related to executive leadership tasks
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CEO/executive leadership) and lists some actions (비전/전략 수립, 경영 의사결정, 조직 리더십), but these are high-level categories rather than concrete, specific actions like 'create strategic plans' or 'draft board presentations'. | 2 / 3 |
Completeness | Describes what it does (담당합니다 - 'handles') but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The 'when' component is entirely missing. | 1 / 3 |
Trigger Term Quality | Uses formal Korean business terminology (비전/전략 수립, 경영 의사결정, 조직 리더십) that users are unlikely to naturally say. Missing common trigger terms users might actually use like 'business strategy', 'leadership advice', 'executive decision', or 'company vision'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Executive CEO Agent' framing provides some distinctiveness, but terms like '전략 수립' (strategy development) and '의사결정' (decision-making) could easily overlap with general business consulting, strategy, or management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a role description rather than actionable guidance. It lists what a CEO agent should do but provides zero concrete instructions on how to do it. The content would be equally useful as a job posting - it tells Claude the responsibilities but not how to execute them.
Suggestions
Add concrete examples of strategy documents with templates or formats Claude should produce (e.g., a sample vision statement structure, decision framework template)
Define a clear workflow for strategic decision-making with specific steps (e.g., 1. Gather context from X, 2. Analyze using Y framework, 3. Document decision in Z format)
Include specific output formats and examples for each deliverable type (vision documents, strategic plans, stakeholder communications)
Add links to reference materials or templates in the `docs/strategy/` directory that Claude should use or follow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but lacks substance - it's concise by being vague rather than by being efficient. The bullet points are short but don't provide actionable value. | 2 / 3 |
Actionability | Extremely vague with no concrete guidance, commands, examples, or executable instructions. Lists abstract responsibilities ('전략적 의사결정', '조직 리더십') without explaining how to actually perform them. | 1 / 3 |
Workflow Clarity | No workflow, sequence, or process defined. Simply lists responsibilities without any steps, validation checkpoints, or guidance on how to execute CEO-level tasks. | 1 / 3 |
Progressive Disclosure | References an output location (`docs/strategy/`) but provides no links to detailed materials, templates, or examples. The structure exists but lacks meaningful navigation to supporting content. | 2 / 3 |
Total | 6 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 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.