executive-cio

Executive CIO Agent. IT 전략, 디지털 전환, 인프라 관리를 담당합니다.

Quality

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/executive-cio/SKILL.md

Quality

Content

14%

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

This skill is essentially a placeholder that defines a role title and lists responsibilities without providing any actionable guidance. It lacks concrete instructions, workflows, examples, or references that would enable Claude to actually perform CIO-related tasks. The content describes what a CIO does rather than instructing how to do it.

Suggestions

Add concrete workflows for key tasks (e.g., 'IT 전략 수립 프로세스: 1. 현황 분석 → 2. 갭 분석 → 3. 전략 수립 → 4. 로드맵 작성')

Include specific templates or output formats for deliverables (e.g., IT strategy document structure, digital transformation assessment framework)

Provide executable examples such as sample analysis frameworks, decision matrices, or assessment checklists that Claude can use

Reference supporting documents for detailed methodologies (e.g., 'See [IT_ASSESSMENT_TEMPLATE.md] for infrastructure evaluation criteria')

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 ('IT 전략', '디지털 전환') without any actionable instructions on how to perform these tasks.	1 / 3
Workflow Clarity	There are no workflows, steps, or processes 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 (`docs/it-strategy/`), there are no references to detailed materials, templates, or supporting documents. The content is a stub with no meaningful structure or navigation.	1 / 3
	Total	5 / 12 Passed

Description

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 severely underdeveloped, consisting only of a role title and three vague domain areas without any concrete actions, specific capabilities, or trigger conditions. It reads more like a job title than a skill description, providing no guidance for Claude to determine when to select this skill over others.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates IT roadmaps, evaluates technology vendors, designs cloud migration plans, assesses cybersecurity posture'

Include an explicit 'Use when...' clause with natural trigger terms users would say, e.g., 'Use when the user asks about IT budgets, technology stack decisions, cloud strategy, or enterprise architecture'

Replace abstract business jargon with task-specific language that distinguishes this from general business or technology skills

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'IT 전략' (IT strategy), '디지털 전환' (digital transformation), and '인프라 관리' (infrastructure management) without listing any concrete actions or specific tasks Claude would perform.	1 / 3
Completeness	The description only vaguely addresses 'what' (handles IT strategy, digital transformation, infrastructure) and completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	The terms used are high-level business jargon ('CIO', 'digital transformation', 'IT strategy') rather than natural keywords users would actually say when needing help. No common user phrases or task-specific triggers are included.	1 / 3
Distinctiveness Conflict Risk	The description is extremely generic and could overlap with numerous other skills related to technology, strategy, management, or business consulting. 'IT strategy' and 'digital transformation' are broad enough to conflict with many potential skills.	1 / 3
	Total	4 / 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

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

Reviewed: 4 months 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.