CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

referrals

When the user wants referral and affiliate programs or word of mouth, or asks what to reward, how much to pay, or which loop to start with: refer-a-friend incentives, commissions and payouts, partner programs, 'made with' badges, review campaigns. For launch virality, see launch. For creator deals, see influencer-marketing.

Quality

85%

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-organized, information-dense skill body: concrete templates, ranked tactics, phased launch checklists, and clean reference signaling with no padding that teaches Claude things it already knows. The main gaps are minor — a duplicated question-gathering section, a few generic optimization bullets, one reference file hidden two levels deep, and the absence of structured validation/feedback loops.

Suggestions

Remove the "Task-Specific Questions" section — its six questions duplicate the "Before Starting" context-gathering (program type, LTV/CAC, tools, budget, shareability), saving tokens without losing information.

Replace generic optimization bullets ("Ask at better moments", "Test different incentive types") with concrete tactics or a pointer to program-examples.md for specific incentive variants and timings.

Link references/review-program-operations.md directly from the Review Programs section of SKILL.md so all bundle files are discoverable one level from the overview instead of requiring a hop through review-programs.md.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive throughout — ranked lists, tables, checklists, and specific numbers ("16-25% higher LTV", "say '$10 off,' not '40% off'") with no concept-teaching padding, matching the 'efficient; minor instances' anchor. Not 3 because there is no unnecessary library/concept explanation; not 5 because the "Task-Specific Questions" section duplicates the "Before Starting" context questions and a few bullets ("Ask at better moments", "Test different incentive types") are generic filler.

4 / 5

Actionability

Mostly concrete, executable guidance: copy-paste-ready email templates with placeholders, share mechanisms ranked by effectiveness, specific value-presentation rules, a problems/fixes table, and a tool table mapping named tools to use cases. Not 5 because some optimization guidance stays high-level ("Ask at better moments", "Improve landing experience") and incentive sizing is deferred entirely to a reference file.

4 / 5

Workflow Clarity

A clear lifecycle sequence is present — context gathering, virality diagnostic, referral-vs-affiliate choice, a 3-step design process, then a phased Before Launch / Launch / Post-Launch checklist with checkpoints like "Test complete referral flow" and "Review conversion funnel". Not 5 because there are no explicit error-recovery or re-validation loops (the post-launch review is implicit rather than a structured feedback loop); not 3 because the phased checklists provide real, ordered checkpoints.

4 / 5

Progressive Disclosure

The overview is well-structured with six clearly signaled references, each annotated with its contents ("For examples and incentive sizing: See [references/program-examples.md]"), all verified to exist and one level deep. Not 5 because review-program-operations.md is only reachable via a second hop through review-programs.md (orphaned from the SKILL.md overview), and the Tool Integrations section routes implementation guides to external GitHub URLs rather than the bundle.

4 / 5

Total

16

/

20

Passed

Description

87%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: explicit and specific trigger phrasing, concrete capability enumeration, good synonym coverage, and explicit routing to sibling skills for adjacent needs. The only gaps are the absence of action verbs in the capability list and a few missing common trigger variants (ambassador, referral code).

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "refer-a-friend incentives, commissions and payouts, partner programs, 'made with' badges, review campaigns" plus "what to reward, how much to pay, or which loop to start with" — matching the 'several specific actions; minor gaps' anchor. Not 5 because capabilities are stated as topics rather than explicit actions, and coverage is not comprehensive.

4 / 5

Completeness

Explicitly answers both: what ("refer-a-friend incentives, commissions and payouts, partner programs, 'made with' badges, review campaigns") and when ("When the user wants referral and affiliate programs or word of mouth, or asks what to reward, how much to pay") with concrete trigger phrases — structurally identical to the anchor-5 example. Not 4 because the when-clause is fully explicit rather than merely present-but-imprecise.

5 / 5

Trigger Term Quality

Good natural keyword coverage with synonyms — "referral and affiliate programs", "word of mouth", "refer-a-friend", "commissions and payouts", "partner programs", "review campaigns" — phrases users would actually say. Not 5 because common variants like "ambassador program", "referral code/link", or "customer referral" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct domain-specific triggers, and it actively de-conflicts the closest siblings: "For launch virality, see launch. For creator deals, see influencer-marketing." This exceeds the anchor-5 example (which achieves minimal conflict risk without any disambiguation); only trivial overlap remains around "review campaigns" and "word of mouth".

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

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.