AF 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,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch-strategy.
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.
As a process F 39/100 · Will not run — References files that are not bundled: ../../tools/REGISTRY.md, ../../tools/integrations/rewardful.md, ../../tools/integrations/tolt.md
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../tools/REGISTRY.md - warning
missing-refreference to a missing file: ../../tools/integrations/rewardful.md - warning
missing-refreference to a missing file: ../../tools/integrations/tolt.md - warning
missing-refreference to a missing file: ../../tools/integrations/mention-me.md - warning
missing-refreference to a missing file: ../../tools/integrations/dub-co.md - warning
missing-refreference to a missing file: ../../tools/integrations/stripe.md
Process rating: all ten parameters 39/100
- 0Tools and files. 6 referenced file(s) missing: ../../tools/REGISTRY.md, ../../tools/integrations/rewardful.md, ../../tools/integrations/tolt.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Steps. 81 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1668 tokens
- low 11 top-level sections: this looks like several domains in one skill
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 495: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 81 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.