executive-cdo

Executive CDO Agent. 데이터 전략, 데이터 거버넌스, AI/ML 전략을 담당합니다.

Install with Tessl CLI

npx tessl i github:shaul1991/shaul-agents-plugin --skill executive-cdo

What are skills?

Quality

18%

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-cdo/SKILL.md

SKILL.md

Review

Evals

Discovery

22%

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 is too vague and abstract to effectively guide skill selection. It names high-level domains but fails to specify concrete actions the skill performs and completely lacks trigger guidance for when Claude should select it. The Korean language is fine, but the content needs substantial improvement in specificity and completeness.

Suggestions

Add a 'Use when...' clause with specific trigger scenarios, e.g., 'Use when users ask about data governance policies, data strategy planning, or AI/ML roadmap development'

Replace abstract responsibility language with concrete actions, e.g., 'Creates data governance frameworks, develops data strategy roadmaps, designs AI/ML implementation plans'

Include natural user trigger terms in both Korean and English variations that users would actually say, such as '데이터 정책', 'data policy', 'AI 전략 수립', 'ML governance'

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like '담당합니다' (is responsible for) without listing concrete actions. It names domains (data strategy, data governance, AI/ML strategy) but doesn't specify what actions the skill actually performs.	1 / 3
Completeness	The description only vaguely addresses 'what' (responsible for data/AI strategy) and completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent instruction.	1 / 3
Trigger Term Quality	Contains some relevant domain keywords like '데이터 전략' (data strategy), '데이터 거버넌스' (data governance), 'AI/ML 전략' but lacks natural user trigger terms and common variations users would actually say when needing this skill.	2 / 3
Distinctiveness Conflict Risk	The 'CDO Agent' framing provides some distinctiveness, but the broad domains of 'data strategy' and 'AI/ML strategy' could easily overlap with other data-related or AI-related skills without clear boundaries.	2 / 3
	Total	6 / 12 Passed

Implementation

14%

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 placeholder that defines a role title and lists responsibilities without providing any actionable guidance. It lacks concrete instructions, examples, workflows, or references that would enable Claude to actually perform CDO-related tasks. The content reads more like a job description than a functional skill.

Suggestions

Add concrete, actionable guidance for at least one core responsibility (e.g., a step-by-step process for creating a data strategy document with specific sections and considerations)

Include executable examples or templates, such as a data governance framework outline or AI/ML strategy assessment checklist

Define clear workflows with validation checkpoints for key deliverables (e.g., 'Before finalizing data strategy: 1. Validate alignment with business objectives, 2. Review with stakeholders, 3. Check compliance requirements')

Add references to detailed materials for each responsibility area (e.g., 'For data governance frameworks: See [GOVERNANCE.md](GOVERNANCE.md)')

Dimension	Reasoning	Score
Conciseness	The content is brief and doesn't over-explain concepts Claude knows, but it's so minimal that it lacks substance rather than being efficiently dense with useful information.	2 / 3
Actionability	The skill provides no concrete guidance, executable code, commands, or specific examples. It only lists abstract responsibilities without any actionable instructions on how to perform them.	1 / 3
Workflow Clarity	There are no workflows, processes, or steps defined. The skill merely lists topic areas without explaining how to approach any of them or what sequence of actions to take.	1 / 3
Progressive Disclosure	While it mentions an output location, there are no references to detailed materials, no structured navigation, and the content is too sparse to constitute a useful overview pointing to deeper resources.	1 / 3
	Total	5 / 12 Passed

Validation

90%

Warnings & errors only

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: 15 days ago

Table of Contents

Discovery Implementation Validation

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.