菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill to render affiliate-mcp's branded, screenshot-ready social cards (1080x1080) for the weekly launch and other marketing, from the repo design system. It produces card assets for review; the numbers on a card must be real anonymised data or clearly a demo, never invented client data presented as real. Trigger on: "make the weekly card", "render the earnings card", "build a social card", "design the launch artifact".
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".
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?".
Use this skill to prepare affiliate-mcp's find-users marketing in prepare-and-approve mode: the weekly branded LinkedIn card and post, directory and registry listing submissions, and free lead-magnet content. It applies the voice and ship-checks and queues everything as Buffer drafts; it never publishes or queues a live post. Trigger on: "prepare this week's launch post", "draft the marketing", "queue the weekly card", "prepare directory listings", "run the marketing loop".
Use this skill to prepare onboarding and lifecycle email for new and dormant hosted sign-ups in prepare-and-approve mode: a guided first-value message for a fresh sign-up, an activation nudge for someone who connected but has not run a report, and a re-engagement draft for a dormant account. It prepares Gmail drafts only; it never sends. Distinct from the agency `client-onboarding` skill, which records a client's advisory strategy. Trigger on: "prepare onboarding emails", "draft activation nudges", "welcome new sign-ups", "re-engage dormant hosted users", "run the onboarding loop".
Use this skill when an agency operator wants the Monday weekly note produced for every client in the book in one pass, each in the client's own recorded voice and escalation thresholds, rather than one brand at a time. This is the premium batch extension of the free `programme-performance-report` skill's weekly-client-note output profile, not a replacement for it. Trigger on: "Give me this week's client notes for the whole book", "Run the Monday reports for every client", "Batch the weekly notes for all clients", "Send-ready weekly notes for the book".
| name | affiliate-network-status |
| description | 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". |
You are reporting on the health of all configured affiliate networks. The single source of truth is affiliate_run_diagnostic.
Call affiliate_run_diagnostic with no arguments. It returns one NetworkCapabilities record per registered network:
{
network: "<slug>",
generatedAt: "<iso>",
operations: {
listProgrammes: { supported: true, latencyMs: 412, sampleSize: 25 },
getProgramme: { supported: true, latencyMs: 198 },
listTransactions: { supported: true, latencyMs: 980, sampleSize: 12 },
getEarningsSummary: { supported: true, latencyMs: 1020 },
listClicks: { supported: false, note: "not exposed by this network's public API" },
generateTrackingLink:{ supported: true, latencyMs: 230 },
verifyAuth: { supported: true, latencyMs: 140, note: "identity=pub-12345" }
},
knownLimitations: [...]
}
If affiliate_run_diagnostic itself returns an empty array, no networks are wired up — tell the user to run affiliate-networks-mcp setup.
For each network in the response, decide a status:
supported: true and latencyMs is reasonable (< 5000ms).verifyAuth is OK but one or more publisher operations failed unexpectedly (i.e. they're not in knownLimitations).verifyAuth.supported === false. Auth is broken; the rest is noise until that's fixed.An operation reported as unsupported when it appears in knownLimitations is not a failure — it's expected. Don't alarm the user about Awin's missing click data.
Two-part output:
| Network | Status | Auth | Ops failing unexpectedly | p95 latency |
|---|
Bullet list, one per affected network. Be specific:
<verbatim message>. Run affiliate-networks-mcp doctor awin for the full diagnostic JSON. Likely cause: rotated or revoked API token (regenerate at https://ui.awin.com under your publisher profile)."<verbatim>. Run affiliate-networks-mcp doctor cj to capture the full response body."If everything is green: a single line — "All N networks healthy as of <iso>."
affiliate-networks-mcp doctor <slug> (not raw curl commands) when the user wants the full JSON.affiliate_<slug>_verify_auth if the user wants to re-check a single network after rotating credentials.