growth-acquisition
User Acquisition Agent. 사용자 획득 전략, 채널 최적화, CAC 관리를 담당합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill growth-acquisition40
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (user acquisition) and lists relevant responsibilities, but lacks concrete actions and explicit trigger guidance. The Korean language mixed with English acronyms may limit discoverability, and the absence of a 'Use when...' clause significantly weakens its utility for skill selection.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'user acquisition', 'CAC', 'customer acquisition cost', 'growth channels', 'paid marketing', 'conversion optimization'
Replace abstract terms like '담당합니다' (is responsible for) with specific actions such as 'analyzes acquisition funnels', 'calculates CAC by channel', 'recommends channel budget allocation'
Include common user phrases in both Korean and English to improve trigger coverage, such as '마케팅 채널', 'growth strategy', 'acquisition metrics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (user acquisition) and mentions some actions (strategy, channel optimization, CAC management), but these are high-level concepts rather than concrete, specific actions like 'analyze acquisition funnels' or 'calculate customer acquisition costs'. | 2 / 3 |
Completeness | Describes what it does (handles user acquisition strategy, channel optimization, CAC management) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'User Acquisition', 'CAC', and '채널 최적화' (channel optimization), but misses common variations users might say such as 'growth', 'marketing channels', 'conversion', 'funnel', or 'paid acquisition'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to user acquisition domain, but could overlap with general marketing skills, growth skills, or analytics skills. The terms 'strategy' and 'optimization' are generic enough to cause potential conflicts. | 2 / 3 |
Total | 7 / 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 is essentially a role description rather than actionable guidance. It lists responsibilities and trigger keywords but provides zero concrete instructions on how to analyze channels, calculate CAC/LTV, or optimize marketing ROI. Claude would not know what specific actions to take when this skill is triggered.
Suggestions
Add concrete examples of channel analysis outputs with specific metrics and formats (e.g., a template for CAC/LTV calculations)
Include step-by-step workflows for key tasks like '채널별 성과 분석' with specific data sources and analysis methods
Provide executable code or formulas for calculating CAC, LTV, and marketing ROI
Reference specific templates or example files in the `docs/growth/acquisition/` directory that Claude should use or create
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief and doesn't over-explain concepts, but it's essentially just a list of responsibilities without actionable content - it's lean but empty rather than efficiently informative. | 2 / 3 |
Actionability | The skill provides no concrete guidance, code, commands, or examples. It only lists abstract responsibilities like '채널별 성과 분석' without explaining how to actually perform any of these tasks. | 1 / 3 |
Workflow Clarity | There is no workflow defined - no steps, no sequence, no validation checkpoints. The skill only lists what the agent does, not how to do it. | 1 / 3 |
Progressive Disclosure | The content mentions an output location (`docs/growth/acquisition/`) which suggests some structure, but there are no actual references to detailed materials, templates, or examples that would help Claude perform the tasks. | 2 / 3 |
Total | 6 / 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 | |
- Reviewed
Table of Contents
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.