executive-coo

Executive COO Agent. 운영 효율화, 프로세스 개선, 리소스 관리를 담당합니다.

Quality

11%

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

Quality

Content

22%

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 abstract responsibilities without providing any actionable guidance. It tells Claude what a COO does conceptually but gives no concrete instructions, workflows, examples, or tools for actually performing operational tasks. The content would need substantial expansion to be useful.

Suggestions

Add concrete workflows for at least one core responsibility (e.g., step-by-step process for conducting an operational efficiency review)

Include specific examples of deliverables with templates or formats (e.g., what an operations document in docs/operations/ should contain)

Provide actionable checklists or decision frameworks for common COO tasks like resource allocation or process improvement

Reference or create detailed guides for each responsibility area (e.g., PROCESS_IMPROVEMENT.md, QUALITY_MANAGEMENT.md) with executable guidance

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 only vague categories (운영 효율화, 품질 관리) without any concrete guidance, commands, examples, or executable instructions on how to actually perform COO tasks.	1 / 3
Workflow Clarity	No workflow is defined at all. There are no steps, sequences, or processes described—just abstract responsibility areas without any operational guidance.	1 / 3
Progressive Disclosure	The content mentions an output location (docs/operations/) suggesting some structure, but provides no actual references to detailed materials or navigation to learn more about any of the listed responsibilities.	2 / 3
	Total	6 / 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 too abstract and lacks actionable specificity. It reads like a job title description rather than a skill that helps Claude understand when and how to use it. The Korean language description provides no concrete actions, trigger terms, or explicit usage guidance.

Suggestions

Add specific concrete actions Claude can perform, e.g., 'Analyzes workflow bottlenecks, creates process documentation, tracks KPIs, generates operational reports'

Include a 'Use when...' clause with natural trigger terms users would say, such as 'Use when user asks about workflow optimization, operational metrics, team capacity planning, or process documentation'

Add distinctive file types, tools, or domains to differentiate from generic business skills, e.g., 'Works with operational dashboards, capacity spreadsheets, SOP documents'

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like '운영 효율화' (operational efficiency), '프로세스 개선' (process improvement), and '리소스 관리' (resource management) without listing any concrete actions Claude would perform.	1 / 3
Completeness	While it vaguely describes 'what' (operational areas), there is no 'Use when...' clause or explicit guidance on when Claude should select this skill. Both what and when are very weak.	1 / 3
Trigger Term Quality	Contains only high-level business jargon ('COO', 'operational efficiency', 'process improvement') that users are unlikely to naturally say when requesting help. No specific trigger terms or common variations are provided.	1 / 3
Distinctiveness Conflict Risk	Extremely generic business terms like 'process improvement' and 'resource management' could overlap with virtually any business, project management, or operations-related skill.	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.