---
name: affiliate-partner-operations
description: "Qualify partners and verify referral links without mixing commercial terms between clients. Use when the user requests affiliate and partner operations. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.1"
---

# Affiliate and Partner Operations

Qualify partners and verify referral links without mixing commercial terms between clients.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Approved partner criteria
- Program terms
- Product destinations
- Attribution requirements

## Methods

### Assess partner fit

Assess audience relevance, distribution quality and evidence of fit. Distinguish a researched prospect from an accepted partner.

### Resolve program terms

Resolve commissions, permitted claims, geography and disclosures from the current program terms. Do not reuse another program’s rates or promises.

### Verify tracking links

Construct links through the approved program mechanism. Test redirects, final destination and tracking parameters while avoiding test orders or fabricated conversions.

### Prepare the partner queue

Return a partner shortlist, outreach drafts and link-verification record. Enrolling partners, accepting terms and sending outreach remain separate authorized actions.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.

## Additional operational methods

Read [focused operational guidance](references/partner-pipeline.md) for affiliate partner operations decisions that require deeper reconciliation.