Affiliate Marketing

Design and optimize affiliate programs with partner scoring, commission economics, tracking QA, fraud controls, and compliance reviews.

Security Scan

This instruction-only affiliate marketing skill is internally consistent with its stated purpose and requests no unusual permissions, binaries, or credentials.

Purpose & Capability

Name and description match the included content (program design, partner ops, tracking QA, fraud controls, reporting). The skill requires no binaries, env vars, or installs — appropriate for a guidance/operating-playbook skill.

Instruction Scope

Runtime instructions are limited to advisory workflows and optional local persistence in ~/affiliate-marketing/ with explicit user consent. The SKILL.md also suggests saving an activation preference in the agent's main memory; this is reasonable for convenience but is a form of persistent state the user should be aware of.

Install Mechanism

No install spec and no code files — lowest-risk model (instruction-only). Nothing is downloaded or written unless the user consents to create an optional local folder.

Credentials

No environment variables, credentials, or config paths are required. The only configPaths metadata references an optional user workspace under ~/affiliate-marketing/ which the documentation frames as opt-in and limited to program context, partners, and incidents.

Persistence & Privilege

The skill is not marked 'always' and allows autonomous invocation (the platform default). It may store optional local files and suggested activation preference in the agent's main memory; these are normal but constitute persistent state the user should approve and can later remove.

Assessment

This skill is a guidance/playbook for running affiliate programs and appears coherent and low-risk. Before enabling: 1) Confirm you are comfortable with optional local files (~/affiliate-marketing/) and only allow creation if you want persistent program state. 2) Avoid storing sensitive credentials, PII, or financial secrets in the skill's memory files — the docs advise keeping only high-signal program decisions. 3) Be aware the skill may register an activation preference in agent memory so it appears when relevant; you can revoke or delete that memory later if desired. 4) Because this is instruction-only, no code will run or be installed, but review any local files the skill creates and periodically delete them if you no longer want persistence.

Setup

On first use, read setup.md for integration guidelines. This skill works without local storage. Only create ~/affiliate-marketing/ if the user wants persistent partner and program continuity.

When to Use

User needs affiliate marketing, affiliate program management, partner recruitment, affiliate tracking, or affiliate operations. Agent handles program design, partner scoring, outreach packs, commission economics, tracking QA, attribution conflicts, fraud review, and reporting.

Use this when the problem is operating an affiliate channel end to end, not just generating links or listing networks. The goal is to turn partner revenue into a controlled acquisition engine with better unit economics and lower compliance risk.

This skill is especially strong for ecommerce, SaaS, creators with affiliate offers, and brands running publishers, coupon partners, creators, or referral-style affiliates under one program.

Architecture

Local workspace is optional and only created with user consent.

~/affiliate-marketing/
├── memory.md        # Program context, approved rules, active constraints
├── partners.md      # Pipeline, status, offer history, next actions
├── economics.md     # Commission ceilings, margins, payout scenarios
└── incidents.md     # Fraud flags, attribution disputes, compliance notes

Quick Reference

Topic	File
Setup and activation	setup.md
Optional continuity memory	memory-template.md
Program design and offer structure	program-design.md
Partner sourcing and outreach pipeline	partner-pipeline.md
Commission economics and payout logic	economics.md
Tracking, attribution, and compliance	tracking-compliance.md
Fraud detection and payout QA	fraud-qa.md
Lifecycle management and reporting	lifecycle-reporting.md
Launch and recovery playbooks	playbooks.md

Core Rules

1. Design the program before recruiting partners

• Define partner types, payout model, approval rules, attribution window, restricted traffic sources, and clawback rules first.
• Recruitment without governance creates low-quality growth, conflict with other channels, and messy payouts.
• Use program-design.md before approving partner outreach or commissions.

2. Score partners on fit, economics, and risk together

• Evaluate audience fit, traffic quality, historical credibility, commission appetite, and brand safety at the same time.
• A partner with reach but bad economics or compliance risk is not a win.
• Use partner-pipeline.md to rank who should be recruited, activated, paused, or rejected.

3. Protect margin before scaling payouts

• Model gross margin, refund rate, AOV, LTV, clawbacks, and cannibalization before recommending higher commissions.
• Raw affiliate revenue can hide unprofitable traffic or orders that would have converted anyway.
• Use economics.md to set commission ceilings and bonus rules.

4. Treat tracking QA as launch-critical

• Validate links, coupon mapping, attribution logic, landing destinations, and UTM naming before traffic goes live.
• Broken tracking destroys trust with partners and makes optimization impossible.
• Use tracking-compliance.md whenever a campaign, offer, or payout structure changes.

5. Block fraud and leakage early

• Watch for self-referrals, trademark bidding, cookie stuffing, coupon leakage, bot traffic, fake leads, and suspicious payout spikes.
• Do not wait for finance or legal to discover abuse after the budget is gone.
• Use fraud-qa.md before approving payouts or scale decisions.

6. Run affiliate lifecycle as an operating system

• Manage recruitment, onboarding, activation, creative refresh, performance coaching, reactivation, and offboarding as one loop.
• The skill should always know the next best action for each partner and segment.
• Use lifecycle-reporting.md for weekly reviews and partner portfolio decisions.

7. Escalate claims, disclosures, and restricted actions

• Treat trademark use, hard earnings claims, regulated verticals, SMS/email consent, and geo-specific disclosure rules as approval moments.
• Never invent proof, hide incentive relationships, or recommend deceptive urgency.
• Use tracking-compliance.md and playbooks.md for review gates before launch.

Operating Rhythm

Before launch

• Lock partner type, offer structure, landing path, attribution method, and disclosure rules.
• Validate links, payouts, and restricted terms before any partner goes live.

Weekly

• Review recruitment pipeline, activations, partner quality, conversion quality, reversals, and payout exposure.
• End each week with keep, fix, scale, pause, and remove decisions.

Monthly

• Re-price commissions, reclassify partner tiers, and audit whether affiliate revenue is incremental or cannibalized.
• Refresh creative, landing pages, and partner enablement before adding more partners.

Common Traps

• Recruiting everyone with traffic -> partner count rises while quality and margin collapse.
• Paying high commissions without incrementality checks -> revenue grows on paper but profit weakens.
• Letting coupons, creators, and content affiliates share one sloppy attribution model -> channel conflict and payout disputes.
• Ignoring disclosure and trademark rules -> legal exposure and program trust damage.
• Launching with broken links or weak landing pages -> partner confidence drops and traffic is wasted.
• Looking only at clicks or affiliate-attributed revenue -> hides refunds, fraud, leakage, and cannibalization.

Security & Privacy

Data that stays local when the user opts in:

• Program rules, partner notes, commission assumptions, and payout concerns in ~/affiliate-marketing/
• Fraud flags, compliance notes, and reporting summaries in local markdown files

This skill does NOT:

• Automatically create affiliate accounts, send outreach, or change payouts
• Create local files without explicit user consent
• Access networks, ESPs, analytics tools, or payment systems unless the user explicitly requests a separate approved tool workflow
• Make undeclared network requests

Guardrails:

• Treat sensitive partner data, payout details, and customer-level data as restricted
• Escalate legal or policy-sensitive promotions for review before launch

Related Skills

Install with clawhub install <slug> if user confirms:

• market-research — Partner landscape, vertical mapping, and competitor analysis
• growth-hacker — Acquisition experiments and growth loops
• cmo — Channel strategy, demand generation, and marketing leadership
• email-marketing — Nurture sequences and owned-audience conversion
• content-marketing — Content partner enablement and repurposing systems

Feedback

• If useful: clawhub star affiliate-marketing
• Stay updated: clawhub sync