CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

73

Quality

90%

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

86%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 comprehensive, well-structured GTM skill body with concrete frameworks, timelines, and a sensible split into reference files. The main improvement is trimming editorial intro prose and making validation checkpoints explicit in the launch/onboarding workflows.

Suggestions

Cut the editorial framing in section intros ('The partner landscape has shifted decisively...') and lead directly with the actionable comparison or framework.

Add explicit validation/checkpoint steps to the Affiliate Launch Checklist and Integration Onboarding process (e.g. 'Verify tracking attribution before scaling recruitment', 'Confirm beta integration passes QA before GTM launch').

Tighten the commission and platform tables by removing redundant prose so the tables carry the guidance.

DimensionReasoningScore

Conciseness

Mostly efficient structured tables and frameworks with concrete numbers, but contains editorial prose ('The partner landscape has shifted decisively...', 'Integration partnerships have become the fastest-growing partnership category because...') that explains context Claude largely already knows and could be trimmed.

4 / 5

Actionability

Highly concrete and executable: specific commission tiers (10-15%, 20-25%, 30-40%), platform pricing ($49/mo, $99/mo), a weighted scoring model, timeline-based checklists, and a decision tree that directly guide program design.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (Affiliate Launch Checklist with Week/Day timelines, Integration Onboarding Steps 1-4), but validation/feedback checkpoints are only weakly implied (e.g. 'Monitor first conversions, adjust tracking if attribution gaps appear') rather than explicit.

4 / 5

Progressive Disclosure

Well-organized sections with one-level-deep references to real bundle files ('read references/implementation-guide.md', 'read references/quick-reference.md'), pushing deep details (marketplace, recruitment, co-marketing, attribution, operations, playbook) out of the overview while keeping core frameworks inline.

5 / 5

Total

18

/

20

Passed

Description

95%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, well-structured description that clearly states capability, trigger terms, scope, and boundaries in third person. Minor room to vary the action verbs beyond build/launch/design/create.

DimensionReasoningScore

Specificity

Names the domain and several concrete program types ('build a partner program, launch an affiliate program, design integration partnerships, or create distribution partnerships') plus a lifecycle span ('from recruitment through performance optimization'), but the verbs are somewhat repetitive and could enumerate more distinct design actions.

4 / 5

Completeness

Explicitly answers both 'what' (partner and affiliate program design from recruitment through performance optimization) and 'when' (an explicit 'Also use when the user mentions...' clause with concrete trigger phrases), and adds a 'Do NOT use for...' boundary.

5 / 5

Trigger Term Quality

Comprehensive natural trigger list including synonyms and a tool name: 'partnerships,' 'affiliate program,' 'referral program,' 'partner ecosystem,' 'integration partner,' 'reseller,' 'co-marketing,' 'PartnerStack,' and 'revenue share.'

5 / 5

Distinctiveness Conflict Risk

Clear niche (partner/affiliate program design) with distinct triggers and an explicit exclusion clause ('Do NOT use for technical implementation, code review, or software architecture'), minimizing conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-skills
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.