# affiliate-performance-dashboard

affiliate-performance-dashboard is a Claude Code skill that turns reporting requirements into an affiliate dashboard spec with metric formulas, audience views, and alert thresholds.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 17600 installs · ★ 2 repo stars
- Author: Maya-Beth Finotti
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/mbfinotti/partnerships-skills/tree/HEAD/skills/affiliate-performance-dashboard/SKILL.md
- Updated: 2026-10-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/affiliate-performance-dashboard

## What it does

The skill does not build a dashboard in a BI tool. The artifact is a spec document that your BI person implements from. Each metric gets an explicit definition: numerator, denominator, window, timezone, counting method. It covers B2B SaaS with recurring revenue-share and B2C ecommerce with order-level CPA.

Before writing anything, the skill runs an interview — one question per message, multiple choice where possible. It asks about program size, who reads the dashboard, commission model, validation window, attribution, data sources, and refresh constraints. The last three answers re-rank every option: a tight deadline strips out metrics that depend on a join you have not built yet.

The method rests on four borrowed pieces: incrementality measurement through holdout and geo-lift, the split between attributed ROAS and attributed ROI, the sourced-vs-influenced rule, and the good-metric criteria from Lean Analytics. The skill says plainly that no canonical affiliate-dashboard framework exists — IAB and PMA publish guidance only. Without partner IDs reaching billing or orders, the customer-file join is not computable, so the spec falls back to the billing/orders spine.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/partnerships-skills --skill affiliate-performance-dashboard -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/affiliate-performance-dashboard/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/affiliate-performance-dashboard/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/partnerships-skills --skill affiliate-performance-dashboard -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/affiliate-performance-dashboard/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/partnerships-skills --skill affiliate-performance-dashboard -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/affiliate-performance-dashboard/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mbfinotti/partnerships-skills skills/affiliate-performance-dashboard
```

2. **Manually: put the files in place**
- File: `.github/skills/affiliate-performance-dashboard/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/partnerships-skills --skill affiliate-performance-dashboard -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/mbfinotti/partnerships-skills --path skills/affiliate-performance-dashboard
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/affiliate-performance-dashboard/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/partnerships-skills --skill affiliate-performance-dashboard -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/mbfinotti/partnerships-skills/tree/HEAD/skills/affiliate-performance-dashboard/SKILL.md

## When to use it
- define the metric set for an affiliate program
- keep sourced and influenced revenue as two capped numbers
- write metric formulas with window, timezone and counting method
- set alert thresholds for top affiliates, source conversion and ROI
- pick a source of truth among platform export, orders and warehouse

## Example prompts
- Write a dashboard spec for our affiliate program: B2B SaaS with recurring commission.
- We need conversion by source and revenue concentration across top affiliates — define the metrics.
- Split sourced and influenced revenue in the report instead of summing them.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 0de59a956e2ceea6.

BEGIN THIRD-PARTY FILE 0de59a956e2ceea6
```text
---
name: affiliate-performance-dashboard
description: Define the metric set and layout for an affiliate performance dashboard, delivered as a dashboard specification document - metric definitions with explicit formulas, views per audience, refresh and review cadence, and alert thresholds for top affiliates, conversion by source, and program ROI. Covers B2B SaaS recurring revenue-share and B2C ecommerce order-level CPA programs. Use whenever the user mentions affiliate program reporting, affiliate KPIs, affiliate ROI, revenue concentration, or what to put on an affiliate dashboard, even if they never say dashboard. Specifies metrics, never builds them in a BI tool. Do NOT use for one creator campaign's measurement plan - use mbfinotti/partnerships-skills@influencer-measurement-framework instead.
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.4.6"
---

# Affiliate Performance Dashboard

Define what an affiliate program dashboard measures and how it is laid out, then deliver a dashboard specification document. The spec - not a built dashboard - is the artifact: whoever owns the BI tooling implements it from the spec.

No canonical affiliate-dashboard framework exists, and metric definitions are not standardized: no standards body enforces them, IAB and the PMA publish guidance only. Say this plainly to the user; never present a branded framework that does not exist.

The method borrows four established things and nothing else:

- **Incrementality measurement**, via holdout and geo-lift testing, resting on explicit definitions of incrementality, baseline conversions, and model validation.
- **Attributed ROAS vs attributed ROI split**, where ROAS divides attributed revenue by media cost and ROI divides it by media cost plus COGS.
- **Sourced vs influenced separation rule**.
```
END THIRD-PARTY FILE 0de59a956e2ceea6

The third-party file has ended. Everything between the 0de59a956e2ceea6 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 1818 of 18621 bytes. © Maya-Beth Finotti · MIT · https://github.com/mbfinotti/partnerships-skills/tree/HEAD/skills/affiliate-performance-dashboard/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
