Search: "affiliate"

|

Review an affiliate-mcp pull request for correctness, architecture, tests, product and customer-journey clarity, documentation, and merge readiness. Use when asked to review, re-review, supervise, or unblock a PR.

Use this skill when an operator wants to record, review, or change a client's affiliate strategy and KPI targets so reports can be judged against the client's own plan. Capture is conversational: the operator pastes an existing brief, deck, or email, or just describes the client in their own words, and this skill drafts the strategy and KPI files, reads them back in plain English, and saves them only after the operator confirms. Thereafter it edits them through chat. Trigger on: "set up a strategy for Acme", "record Acme's KPIs", "onboard a new client", "what are we aiming for with Acme?", "raise Acme's Q3 revenue target to 400k", "Acme prefers premium partners, no coupon sites", "save this client brief".

Use this skill when the user wants to contribute to the affiliate-mcp project — adding a new affiliate network adapter, fixing a broken network adapter, adding a new Claude Code skill, or improving the documentation. Trigger on: "add [network] to affiliate-mcp", "contribute a network", "fix the [network] adapter", "the [network] adapter is broken", "add a skill to affiliate-mcp", "improve the docs for [network]".

Use this skill to run affiliate-mcp's day-to-day company operations on a schedule in prepare-and-approve mode: gather everything waiting for the operator's approval (across GitHub, Buffer, and Gmail), collect new inbound feedback and headline metrics, and assemble one daily brief. It prepares drafts and surfaces decisions; it never sends, posts, or merges anything itself. Trigger on: "run the daily company brief", "what needs my approval today", "run company ops", "prepare today's operations brief", "daily ops run".

Premium pack. Use this to prepare a full quarterly business review for a brand across its affiliate networks: quarter-over-quarter performance, top and declining partners, reversal and pending exposure, and a narrative with recommended actions. Trigger on: "prep the QBR for Acme", "quarterly business review for this brand", "build the Q3 review deck notes".

Use this skill when the user wants to verify that the affiliate links on their site, in a draft, or in a sitemap are still pointing at active programmes. Trigger on: "audit my affiliate links", "check my links still work", "find broken affiliate links", "verify my links track properly".

Use this skill to measure the gap between partnerships on the books and partnerships producing anything, on either side of the market. For a publisher: how many programmes they have joined, how many actually earned in a period, and which are dead weight. For an advertiser or agency: how many publishers are on the programme's roster, how many produced a transaction, and how concentrated the revenue is among the few that did. The output is a read-only worklist; it never applies to, leaves, approves, or contacts anyone. Trigger on: "how many programmes have I joined?", "which of my affiliate programmes are dead?", "how many of our publishers actually sell anything?", "which publishers have never produced a sale?", "audit my joined programmes", "dormant programme sweep", "how concentrated is our partner revenue?".

Use this skill to spot week-over-week anomalies across an agency's portfolio of brands and networks — revenue drops, reversal spikes, dead links, publishers that fell out of the top 10. Designed to run on a schedule via Claude's own scheduling so the agency learns about problems before clients do. Trigger on: "Are there any problems with the affiliate programmes this week?", "Anomaly check", "Anything weird in the affiliate data?".

Use this skill to triage inbound customer and user feedback for affiliate-mcp in prepare-and-approve mode: read new and updated GitHub issues and the support inbox, draft grounded replies from the repo's own docs, propose triage labels, and escalate anything ambiguous, tense, or money-related to the operator. It drafts replies and proposes labels; it never posts a public comment or sends an email itself. Trigger on: "triage the support queue", "draft replies to new issues", "any new user feedback?", "handle customer service", "what did users report today?".

Steward affiliate-mcp implementation, documentation, and pull-request delivery end to end. Use when asked to implement or plan a repo change, advance work from an issue or user outcome, manage multiple PRs, repair or refresh branches, monitor CI, address review findings, prepare merges, or accelerate delivery while keeping product and architecture decisions with the appropriate human.

Use this skill when the user wants a health check of their configured affiliate networks — auth, reachability, supported operations. Trigger on: "is my affiliate setup working", "check my affiliate networks", "are all my networks responding", "network health".