growth-retention
Retention Manager Agent. 사용자 유지, 참여도 향상, 이탈 방지를 담당합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill growth-retention32
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
7%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, providing only a title and vague responsibility statement without concrete actions, trigger terms, or usage guidance. It fails to help Claude distinguish when to select this skill over others and lacks the specificity needed for effective skill selection from a large pool.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Analyzes user behavior patterns, identifies at-risk users, generates retention campaigns, calculates churn metrics')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when analyzing user churn, improving retention rates, identifying disengaged users, or creating re-engagement strategies')
Add file types, data sources, or specific outputs this skill works with to increase distinctiveness (e.g., 'Works with user activity logs, cohort data, engagement metrics')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like '담당합니다' (is responsible for) without listing any concrete actions. It mentions domains (retention, engagement, churn prevention) but no specific capabilities or methods. | 1 / 3 |
Completeness | Only vaguely addresses 'what' (responsible for retention/engagement) and completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided. | 1 / 3 |
Trigger Term Quality | Contains only high-level business jargon ('사용자 유지', '참여도 향상', '이탈 방지') without natural keywords users would actually say when needing this skill. Missing practical trigger terms like 'churn analysis', 'user engagement metrics', or specific actions. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Retention Manager Agent' title and focus on user retention/churn provides some domain specificity, but the vague description could overlap with analytics, marketing, or customer success skills. | 2 / 3 |
Total | 5 / 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 what a Retention Manager Agent should do but provides zero concrete instructions, examples, analysis frameworks, or templates for actually performing retention analysis or designing engagement strategies. Claude would have no additional capability from reading this skill.
Suggestions
Add concrete analysis frameworks with specific metrics (e.g., Day 1/7/30 retention calculation formulas, cohort analysis SQL templates)
Include executable examples showing how to perform retention analysis with sample data and expected outputs
Provide step-by-step workflows for key tasks like 'churn cause analysis' with validation checkpoints
Add templates or schemas for deliverables like re-engagement campaign designs or habit formation frameworks
| 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 'cohort retention analysis' and 'engagement improvement strategy' without any executable instructions on how to perform these tasks. | 1 / 3 |
Workflow Clarity | There are no workflows, sequences, or processes defined. The skill lists tasks but provides no steps for how to accomplish any of them, nor any validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content mentions an output location (`docs/growth/retention/`) which suggests some file organization, but there are no references to detailed guides, templates, or examples that would help Claude actually 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.