CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

referral-program

When the user wants to plan, implement, or optimize referral program strategy. Also use when the user mentions "referral program," "referral marketing," "user referral," "refer-a-friend," "word-of-mouth growth," "referral rewards," "referral tracking," "referral code," "referral incentives," or "viral loop." For referral landing copy, use landing-page-generator.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean strategy skill that delivers specific, quantified guidance rather than generic marketing advice, with a clear assessment-to-design-to-output flow. The main improvements are trimming the meta-preamble and confusing Contextus/{project}.md references, and moving exhaustive detail (tools, benchmarks) into reference files for better progressive disclosure.

Suggestions

Trim the 'When invoking' preamble and clarify or remove the 'root {project}.md' / Contextus instruction, which references an external context system that is not part of this skill bundle and may confuse invocation.

Move exhaustive detail (e.g., the Tools comparison and fraud-prevention specifics) into a references/ file, keeping SKILL.md as a tighter overview with well-signaled one-level-deep links.

Add a worked example of the expected output (e.g., a completed referral program design following the Output Format) to raise actionability from concrete guidance to fully copy-paste-able deliverables.

DimensionReasoningScore

Conciseness

The body is token-efficient: dense decision tables, specific benchmarks (3%-5% conversion, CAC 50%-70% lower), and named tools with almost no prose padding or explanation of concepts Claude already knows. Minor trimmable content remains (the 'When invoking' meta-preamble and the awkward aside 'Referral is necessity in overseas markets, not alternative'), keeping it below anchor 5.

4 / 5

Actionability

For an instruction-only strategy skill the guidance is concrete: quantified reward benchmarks (10%-30% of price), a worked tiered example ($10/$15/$20), specific attribution windows (30-90 days, 180 for subscription), named tools per use case, and a defined Output Format. It is not fully copy-paste ready (no templates or examples of finished output), which keeps it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

There is a coherent sequence (Initial Assessment -> 5-step Design Framework -> Output Format) and the tables provide per-option decision guidance. No validation checkpoints exist, but the skill is advisory rather than destructive/batch, so the feedback-loop cap does not apply; the missing checkpoints are the minor gap that holds it at 4.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized with clear section headers and self-contained at one level (no nested references). However, at ~130 lines it exceeds the simple-skill threshold, and detail like the Tools table and benchmark data could plausibly live in reference files, which is the minor organization gap of anchor 4.

4 / 5

Total

16

/

20

Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with excellent trigger coverage, explicit when-guidance, and active boundary disambiguation toward a sibling skill. The only weakness is that the capability verbs (plan/implement/optimize) are generic and don't hint at the skill's concrete scope (reward models, tracking, fraud prevention, tooling).

DimensionReasoningScore

Specificity

The description names the domain ('referral program strategy') and three actions ('plan, implement, or optimize'), but these verbs are generic and do not convey sub-capabilities like reward design, tracking, or fraud prevention. It sits between anchor 3 (1-2 concrete actions, not comprehensive) and anchor 4 (several specific actions), and the actions are too abstract to justify 4.

3 / 5

Completeness

It explicitly answers both 'what' ('plan, implement, or optimize referral program strategy') and 'when' ('When the user wants to...' and 'Also use when the user mentions...') with concrete trigger phrases, matching the anchor-5 example structure exactly. A 4 would require the 'when' to be less explicit, which is not the case here.

5 / 5

Trigger Term Quality

The trigger list is comprehensive with natural synonyms users would actually say: 'referral program,' 'referral marketing,' 'user referral,' 'refer-a-friend,' 'word-of-mouth growth,' 'referral rewards,' 'referral tracking,' 'referral code,' 'referral incentives,' and 'viral loop.' This matches the anchor-5 example of comprehensive natural-term coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

The referral niche is clearly staked with distinct trigger terms, and it even includes explicit disambiguation ('For referral landing copy, use landing-page-generator'), reducing conflict risk with adjacent skills. It does not trigger on generic marketing language, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

kostja94/marketing-skills

Path

skills/channels/partnerships/referral-program/SKILL.md

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.