executive-cpo

Executive CPO Agent. 제품 전략, 로드맵, 사용자 가치를 담당합니다.

Install with Tessl CLI

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

What are skills?

Quality

22%

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-cpo/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 abstract and role-based rather than action-oriented. It identifies a domain (CPO/product leadership) but fails to specify concrete capabilities or when to use the skill. The Korean language description lacks the explicit trigger guidance needed for reliable skill selection.

Suggestions

Replace abstract responsibilities with concrete actions: e.g., 'Creates product roadmaps, prioritizes features, defines product requirements documents (PRDs), analyzes user feedback'

Add explicit 'Use when...' clause with trigger terms: e.g., 'Use when the user asks about product strategy, feature prioritization, roadmap planning, or product vision'

Include common user phrases and file types: e.g., 'product specs, feature requests, competitive analysis, user stories'

Dimension	Reasoning	Score
Specificity	The description uses vague language like '담당합니다' (is responsible for) without listing concrete actions. 'Product strategy, roadmap, user value' are abstract domains, not specific actions like 'create roadmaps' or 'analyze user feedback'.	1 / 3
Completeness	Only partially addresses 'what' (responsible for product areas) and completely missing 'when' - no 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('제품 전략/product strategy', '로드맵/roadmap', '사용자 가치/user value') but lacks common variations users might say like 'product planning', 'feature prioritization', 'PRD', or 'product requirements'.	2 / 3
Distinctiveness Conflict Risk	'Executive CPO Agent' provides some role distinction, but 'product strategy' and 'roadmap' could overlap with product management, project management, or strategic planning skills. Not clearly differentiated.	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 placeholder that defines a role title and lists responsibilities without providing any actionable guidance. It lacks concrete workflows, templates, examples, or specific instructions that would enable Claude to effectively act as a CPO agent. The content describes what the role does rather than instructing how to do it.

Suggestions

Add concrete templates or frameworks for product strategy documents (e.g., PRD template, roadmap format, prioritization matrix)

Include specific workflows with steps for common CPO tasks like roadmap planning, feature prioritization, or PMF assessment

Provide example outputs showing what deliverables should look like (e.g., sample roadmap structure, product metrics dashboard format)

Add references to detailed guides in docs/product/ for specific product management processes

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 role descriptions and bullet points without any concrete guidance, commands, templates, or executable examples for how to actually perform CPO tasks.	1 / 3
Workflow Clarity	No workflow or process is defined. The skill lists responsibilities but provides no sequence, steps, or validation checkpoints for any product management activities.	1 / 3
Progressive Disclosure	The content is appropriately brief and mentions an output location, but there are no references to detailed materials, templates, or examples that would help Claude execute the role effectively.	2 / 3
	Total	6 / 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.