Executive CMO Agent. 마케팅 전략, 브랜딩, GTM을 담당합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill executive-cmo44
Quality
30%
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-cmo/SKILL.mdDiscovery
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 lacks the specificity needed for effective skill selection. It names broad domains (marketing strategy, branding, GTM) without concrete actions and completely omits trigger guidance for when Claude should use this skill. The Korean language description may limit discoverability for English-speaking users.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about marketing plans, brand positioning, go-to-market strategies, or competitive analysis'
Replace vague domain terms with specific actions: 'Develops marketing strategies, creates brand positioning documents, designs GTM launch plans, analyzes market segments'
Include natural trigger terms users would say: 'marketing campaign', 'brand identity', 'product launch', 'target audience', 'market research'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague terms like '마케팅 전략, 브랜딩, GTM을 담당합니다' (handles marketing strategy, branding, GTM) without listing concrete actions. No specific capabilities like 'create marketing plans', 'analyze brand positioning', or 'develop go-to-market timelines' are mentioned. | 1 / 3 |
Completeness | Only partially addresses 'what' with vague domain areas, and completely lacks a 'when to use' clause. There is no explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant domain keywords (마케팅 전략/marketing strategy, 브랜딩/branding, GTM) but lacks natural variations users might say like 'market research', 'brand guidelines', 'launch strategy', 'competitive analysis', or 'marketing campaign'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'CMO' role and marketing focus provides some distinction, but 'marketing strategy' and 'branding' are broad enough to potentially overlap with other marketing, business strategy, or content creation skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
37%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 role description rather than actionable guidance. While it's concise and well-structured, it completely lacks the concrete instructions, frameworks, templates, or examples needed for Claude to actually perform CMO-level marketing work. The skill tells Claude what a CMO does but not how to do it.
Suggestions
Add concrete frameworks or templates for brand strategy development (e.g., brand positioning canvas, messaging hierarchy)
Include step-by-step workflows for GTM planning with specific deliverables and validation checkpoints
Provide example outputs or templates for marketing documents that should be created in `docs/marketing/`
Add links to reference materials for growth marketing tactics, ROI calculation methods, or customer acquisition frameworks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely brief and doesn't waste tokens explaining concepts Claude already knows. Every line serves a purpose. | 3 / 3 |
Actionability | The skill provides no concrete guidance, code, commands, or examples. It only lists abstract responsibilities without any executable instructions on how to perform them. | 1 / 3 |
Workflow Clarity | No workflow, process steps, or sequences are defined. The skill doesn't explain how to actually execute any of the listed responsibilities like brand strategy or GTM planning. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections and references an output location, but provides no links to detailed materials, templates, or examples that would help execute the role. | 2 / 3 |
Total | 7 / 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 | |
Table of Contents
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.