CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

referrals

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,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' 'affiliate payout,' 'get more reviews,' 'G2 reviews,' 'review campaign,' or 'respond to a bad review.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.

72

Quality

91%

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

82%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.

The body is a well-organized, highly actionable overview that correctly delegates deep material to seven real reference files and includes concrete templates, numbers, and checklists. Weaker spots are mild redundancy in the question-gathering sections, a missing validation thread through the design workflow, and two second-level reference chains that slightly complicate navigation.

Suggestions

Merge "Before Starting" context questions and "Task-Specific Questions" into one section — they ask nearly the same things (program type, LTV/CAC, tools, budget, shareability) and duplicate each other.

Add explicit validation checkpoints to the program-design workflow (e.g., verify tracking and attribution data before launch, review funnel metrics before scaling incentives), extending the pre/post-launch checklist discipline into the design steps.

Flatten the two-level reference chains by linking review-program-operations.md directly from SKILL.md's Review Programs section and consolidating the six repeated viral-mechanisms.md pointers into one clearly labeled callout.

DimensionReasoningScore

Conciseness

The body is dense and free of basic-concept padding (ranked lists, tables, checklists, templates), but "Before Starting" context questions and "Task-Specific Questions" substantially duplicate each other (program type, LTV/CAC, tools, budget, shareability), and viral-mechanisms.md is pointed to six times — minor trimming opportunities that keep it below the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete, ready-to-use guidance throughout: "say '$10 off,' not '40% off,'" a copy-paste email template with subject line, a problem-to-fix table, ranked share mechanisms, and specific A/B test lists — specific examples cover the common cases for this instruction-only skill, matching the score-5 anchor rather than the minor-gaps anchor.

5 / 5

Workflow Clarity

Clear sequences exist (Step 1-3 design flow; Before Launch → Launch → Post-Launch checklists) with some checkpoints ("Test complete referral flow," "Review conversion funnel," "Fix friction points"), but the design workflow has no verification gates and the design → launch → optimize progression is implied rather than one coherent validated workflow — clear sequence with minor validation gaps fits the score-4 anchor.

4 / 5

Progressive Disclosure

References are well-signaled and content-labeled ("For examples and incentive sizing: See references/program-examples.md"), and all referenced files exist, but chains run two levels deep (SKILL.md → review-programs.md → review-program-operations.md; viral-mechanisms.md → program-examples.md), which breaks the strict one-level-deep requirement of the score-5 anchor — good structure with minor organization gaps fits score 4.

4 / 5

Total

17

/

20

Passed

Description

96%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.

The description is exemplary: explicit what-and-when structure, comprehensive natural trigger terms, and a scoping boundary to a sibling skill. The only weakness is that the bundled review/reputation triggers and partner terminology widen the surface into neighboring skill domains, creating minor conflict risk.

DimensionReasoningScore

Specificity

"create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy" lists multiple concrete verb-object actions spanning referral, affiliate, word-of-mouth, and review domains ("respond to a bad review"), matching the comprehensive-coverage anchor rather than the score-4 anchor's 'minor gaps'.

5 / 5

Completeness

Explicitly answers both what ("create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy") and when ("Also use when the user mentions..." and "Use this whenever someone wants existing users or partners to bring in new customers") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Fifteen natural trigger phrasings including synonyms and question forms users would actually say ("refer a friend," "how to get referrals," "affiliate payout," "G2 reviews," "respond to a bad review"), matching the comprehensive-coverage anchor; no file extensions apply to this domain.

5 / 5

Distinctiveness Conflict Risk

A clear niche with a deliberate boundary ("For launch-specific virality, see launch"), but the review-reputation triggers ("get more reviews," "review campaign") and broad partner terms ("partner program," "ambassador") overlap adjacent skill domains — minor overlap risk with closely related skills rather than the minimal conflict of the score-5 anchor.

4 / 5

Total

19

/

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

coreyhaines31/marketingskills

Path

skills/referrals/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.