Content
56%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a comprehensive, genuinely actionable reference for referral/affiliate program design with strong formulas, benchmarks, and templates, but it is padded with knowledge Claude already has and redundant sections. Its monolithic structure inlines template libraries and tool comparisons that belong in one-level-deep reference files.
Suggestions
Cut or compress sections Claude already knows: the referral-vs-affiliate characteristics lists, the Dropbox/Uber/Morning Brew/Notion case studies, and the duplicate 'Questions to Ask' section (merge into 'Before Starting').
Move email templates, the outreach template, and the Tools & Platforms listings into references/ files (e.g. EMAIL_TEMPLATES.md, TOOLS.md) linked from the body, keeping SKILL.md as an overview.
Delete the vacuous 'When to Use' closing line and the repeated persona paragraph at the top of the body — the frontmatter description already carries this.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~600-line body repeats the frontmatter persona verbatim, re-explains widely known material (what referral vs. affiliate programs are, the Dropbox and Uber case studies), duplicates 'Before Starting' questions in a later 'Questions to Ask' section, and ends with filler ('This skill is applicable to execute the workflow or actions described in the overview'). This matches 'noticeably verbose; several unnecessary explanations or padded sections' rather than the mostly-efficient anchor 3. | 2 / 5 |
Actionability | For an instruction-only skill, the guidance is mostly concrete and executable: the incentive-sizing formula with a worked example ('($1,200 × 0.70) - $200 = $640'), K-factor math, benchmark ranges, commission and cookie-duration tables, copy-paste outreach and email templates, and named tools. It is not a 5 because some optimization advice stays abstract ('Shorten the path to value', 'Make the referral prominent in product'). | 4 / 5 |
Workflow Clarity | A clear sequence runs from context gathering through program-type selection, design Steps 1-3, a phased launch checklist (Before/Launch/Post-Launch), and measurement/optimization. Not a 5 because there are no explicit validation checkpoints or feedback loops (e.g., when to re-check K-factor after changes), though no destructive/batch operations exist that would impose a cap. | 4 / 5 |
Progressive Disclosure | The single ~600-line file is well-sectioned with headers and tables, but content that clearly belongs in separate reference files — email templates, tool/platform comparisons, example program case studies — is fully inlined, and no references exist at all. This matches 'some structure but... content that should be separate is inline' rather than anchor 2, which requires minimal structure. | 3 / 5 |
Total | 13 / 20 Passed |