referral-program
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization.
60
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/referral-program/SKILL.mdQuality
Discovery
89%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 is a well-structured skill description with strong trigger term coverage and clear 'when to use' guidance. Its main weakness is that the capability descriptions are somewhat high-level—listing 'program design, incentive structure, and growth optimization' rather than more granular concrete actions. Overall it would perform well in skill selection scenarios.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'design tiered reward structures, calculate referral economics, draft referral messaging, benchmark conversion rates' instead of the general 'program design, incentive structure, and growth optimization.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (referral/affiliate programs) and mentions some actions ('create, optimize, or analyze') along with areas covered ('program design, incentive structure, and growth optimization'), but these are somewhat high-level rather than listing multiple concrete, specific actions like 'design tiered reward structures, calculate referral conversion rates, draft referral email templates.' | 2 / 3 |
Completeness | Clearly answers both 'what' (create, optimize, or analyze referral/affiliate programs; covers program design, incentive structure, growth optimization) and 'when' (explicit 'Use when' clause with specific trigger terms and scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program.' These are terms users would naturally use when seeking help with referral programs. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around referral and affiliate programs with highly specific trigger terms like 'viral loop,' 'refer a friend,' and 'ambassador' that are unlikely to conflict with other skills such as general marketing or growth strategy skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a moderately well-structured consulting-style skill that covers referral and affiliate program design comprehensively. Its main weaknesses are verbosity (explaining concepts Claude already understands), lack of truly executable/concrete implementation guidance, and missing validation checkpoints in its workflows. The progressive disclosure structure is reasonable in intent but the main file retains too much content that should be in referenced files, and the referenced files don't exist in the bundle.
Suggestions
Trim conceptual explanations (referral vs affiliate characteristics, 'typical findings' statistics) that Claude already knows, and focus the main file on decision frameworks and actionable steps.
Add concrete implementation examples—e.g., actual code snippets for setting up Rewardful/Tolt webhooks, tracking attribution with UTM parameters, or configuring referral link generation.
Add explicit validation checkpoints to the launch checklist workflow, such as 'Test complete referral flow end-to-end and verify reward triggers correctly BEFORE announcing to customers.'
Move the email templates and the full referral vs affiliate comparison to reference files to keep the main SKILL.md as a concise overview with clear pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanatory content (e.g., explaining what referral vs affiliate programs are, typical findings statistics, characteristics lists) that Claude would already know. The email templates and some of the conceptual framing could be tightened significantly. However, the tables and checklists are reasonably efficient. | 2 / 3 |
Actionability | The skill provides structured guidance with checklists, tables, and email templates, but lacks truly executable artifacts—no code for implementing tracking, no specific API calls, no concrete configuration examples for the referenced tools. The advice is practical but remains at a strategic/consulting level rather than copy-paste ready implementation. | 2 / 3 |
Workflow Clarity | The referral loop and launch checklist provide decent sequencing, and the 'Before Launch → Launch → Post-Launch' progression is clear. However, there are no validation checkpoints or feedback loops—no steps like 'verify tracking is working before announcing' or 'if conversion rate is below X%, revisit step Y.' The optimization section lists fixes but doesn't sequence them into a diagnostic workflow. | 2 / 3 |
Progressive Disclosure | The skill references several external files (references/program-examples.md, references/affiliate-programs.md, tools registry, tool integration guides) which is good structure, but no bundle files are provided to verify these exist. The main file itself is quite long (~200+ lines) with content like email templates and the full referral vs affiliate comparison that could be offloaded to reference files. | 2 / 3 |
Total | 8 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
3974caa
- 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.