partner-affiliate

When the user wants to build a partner program, launch an affiliate program, design integration partnerships, or create distribution partnerships. Also use when the user mentions 'partnerships,' 'affiliate program,' 'referral program,' 'partner ecosystem,' 'integration partner,' 'reseller,' 'co-marketing,' 'PartnerStack,' or 'revenue share.' This skill covers partner and affiliate program design from recruitment through performance optimization. Do NOT use for technical implementation, code review, or software architecture.

Quality

76%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./packages/skills-catalog/skills/(gtm)/partner-affiliate/SKILL.md

Quality

Content

62%

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

This skill provides exceptionally actionable and well-structured strategic guidance for partner program design, with concrete numbers, decision frameworks, and clear workflows. However, it is significantly over-verbose—explaining industry trends and concepts Claude doesn't need explained, and inlining detailed reference material that should live in the referenced supporting files. Trimming the narrative framing and moving detailed tables to the referenced files would dramatically improve token efficiency.

Suggestions

Remove narrative/explanatory paragraphs like 'The partner landscape has shifted decisively...' and 'Integration partnerships have become the fastest-growing partnership category...' — these explain concepts rather than instruct action.

Move the detailed tier tables, commission structures by revenue model, and platform comparison into `references/quick-reference.md` and keep only a summary with tier names, key percentages, and a pointer to the reference file.

Trim the 'Before Starting' discovery questions to a compact bulleted list without the explanatory sub-text (e.g., 'Even informal word-of-mouth counts' is unnecessary).

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines. It explains concepts Claude already knows (e.g., 'The partner landscape has shifted decisively', 'Integration partnerships have become the fastest-growing partnership category because...'), includes extensive narrative framing, and the model comparison table explains traditional vs. co-creation in a way that pads rather than instructs. Many sections could be cut by 50%+ without losing actionable value.	1 / 3
Actionability	The skill provides highly concrete, specific guidance: exact commission percentages by tier and revenue model, a platform decision tree with specific products and price points, a week-by-week launch checklist, a weighted scoring model for integration prioritization, and specific clawback policies. The examples section shows clear input→output patterns. This is copy-paste-ready strategic guidance.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with timelines: the affiliate launch checklist has day-by-day actions across 3 months, the integration partner onboarding has a clear 4-step process with weekly timelines, and the platform decision tree provides an unambiguous selection workflow. The troubleshooting section provides clear cause→fix patterns for common failure modes.	3 / 3
Progressive Disclosure	The skill references `references/implementation-guide.md` and `references/quick-reference.md` for detailed content, which is good progressive disclosure structure. However, no bundle files were provided to verify these exist, and the main SKILL.md itself contains a large amount of content that could be offloaded (e.g., the full platform comparison table, the complete tier details, the integration scoring model). The related skills table at the end is well-organized but the body is still quite monolithic.	2 / 3
	Total	9 / 12 Passed

Description

89%

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

This is a strong skill description with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it, including negative boundaries. The main weakness is that the specificity of concrete actions could be improved—rather than saying it 'covers partner and affiliate program design from recruitment through performance optimization,' it could list specific deliverables or actions like 'design commission structures, create partner onboarding flows, build referral tracking frameworks.'

Suggestions

Improve specificity by listing concrete actions/deliverables, e.g., 'design commission structures, create partner tiers, build onboarding playbooks, define referral tracking metrics' instead of the broad 'from recruitment through performance optimization.'

Dimension	Reasoning	Score
Specificity	The description names the domain (partner/affiliate programs) and mentions some actions like 'build,' 'launch,' 'design,' and 'create,' but the core capability statement ('covers partner and affiliate program design from recruitment through performance optimization') is fairly broad rather than listing multiple specific concrete actions.	2 / 3
Completeness	Clearly answers both 'what' (partner and affiliate program design from recruitment through performance optimization) and 'when' (explicit trigger terms and use-case scenarios listed). It also includes a helpful negative boundary ('Do NOT use for technical implementation, code review, or software architecture').	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'partnerships,' 'affiliate program,' 'referral program,' 'partner ecosystem,' 'integration partner,' 'reseller,' 'co-marketing,' 'PartnerStack,' 'revenue share.' These are terms users would naturally use when seeking help with partnership programs.	3 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche around partnership and affiliate program design with distinct trigger terms like 'PartnerStack,' 'reseller,' 'co-marketing,' and 'revenue share.' The explicit exclusion of technical implementation further reduces conflict risk with engineering-focused skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: tech-leads-club/agent-skills
Commit: 5f9b25d

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.