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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is highly actionable with concrete frameworks, tables, and timelines, but it is verbose for an overview and lacks explicit validation checkpoints in its workflows. Progressive disclosure is functional yet could be sharpened by moving detail into references and consolidating navigation.

Suggestions

Move the large commission-structure, clawback, and platform-comparison tables into references/ and keep SKILL.md as a tighter overview with a consolidated navigation block pointing to both reference files.

Add explicit validation checkpoints to the multi-step workflows (e.g., 'verify customer overlap via Crossbeam before approving the integration build' and 'confirm attribution tracking fires before launch').

Trim inline detail that restates what a GTM-experienced model already knows (e.g., rationale prose under each model-comparison row) to reduce token load while keeping the actionable tables.

Dimension	Reasoning	Score
Conciseness	The body mostly assumes Claude's competence and avoids explaining known concepts, but it carries substantial inline detail (large commission, clawback, and platform-comparison tables) that pushes the token budget and could partly live in references.	2 / 3
Actionability	Provides highly concrete, copy-paste-ready guidance: specific commission percentages, platform pricing, a scored decision tree, a weighted integration-prioritization model, and a week-by-week launch checklist with timelines.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced (integration onboarding steps 1-4, phased launch checklist), but no explicit validation or verification checkpoints are stated, leaving feedback loops implicit rather than enforced.	2 / 3
Progressive Disclosure	Two real one-level-deep references (implementation-guide.md, quick-reference.md) are present and signaled, but the body still holds large tables that could be externalized, and the reference pointers are buried mid/late rather than gathered into a tidy navigation block.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 specific, trigger-rich, and complete, clearly stating both what the skill does and when to use it while explicitly excluding adjacent domains to reduce conflict. It is a strong, well-scoped activation description.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('build a partner program, launch an affiliate program, design integration partnerships, or create distribution partnerships') plus a scoped range from recruitment through performance optimization, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers both what (partner and affiliate program design from recruitment through performance optimization) and when (an explicit 'Use when the user mentions...' clause), satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	Provides strong natural-language triggers users would actually say ('affiliate program,' 'referral program,' 'partner ecosystem,' 'reseller,' 'co-marketing,' 'PartnerStack,' 'revenue share'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear partner/affiliate niche with distinct triggers and adds an explicit 'Do NOT use for technical implementation, code review, or software architecture' exclusion, making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tech-leads-club/agent-skills
Commit: 9026164

Reviewed: 4 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.