Produce a read-only, evidence-based paid-media performance

Paid ads review

by nowork-studio · MIT license · ★ 3,853 on GitHub · updated Sep 24

Produce a read-only, evidence-based paid-media performance review across connected platforms or supplied exports. Use for weekly or monthly reports, scorecards, performance, CPA, ROAS, CTR, spend trends, pacing, or conversion-tracking…

---
name: paid-ads-review
description: Produce a read-only, evidence-based paid-media performance review across connected platforms or supplied exports. Use for weekly or monthly reports, scorecards, performance, CPA, ROAS, CTR, spend trends, pacing, or conversion-tracking health.
argument-hint: "<date range, platform, or 'weekly review'>"
---

# Paid Ads Review

Read `../shared/operating-contract.md` and `../shared/measurement-framework.md`. This is read-only.

## Assemble comparable evidence

Check which sources are actually connected, request the missing export rather than reporting a failed call, and use the most recent complete equivalent window. For every source, keep currency, conversion definition, attribution window, and reporting lag visible. Verify tracking before treating CPA, ROAS, or revenue as a decision-grade metric.

For live platform accounts, hand data collection and diagnostics to `/notfair:google-ads`, `/notfair:meta-ads`, `/notfair:paid-ads-x`, `/notfair:paid-ads-linkedin`, `/notfair:paid-ads-reddit`, or `/notfair:paid-ads-tiktok`. Keep Amazon and ChatGPT Ads review grounded in a verified connector or supplied platform export.

## Report the decision, not a dashboard transcription

Overview

Read ../shared/operating-contract.md and ../shared/measurement-framework.md. This is read-only.

Manual install (npx, ZIP)

Claude Codenpx skills add nowork-studio/notfair-plugin --skill paid-ads-review -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/nowork-studio/notfair-plugin/tar.gz/5229d2163795 \
  | tar -xz -C ~/.claude/skills --strip-components=2 notfair-plugin-5229d2163795/paid-ads/paid-ads-review

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/45b9725f798cfb45c4a5/paid-ads-review.zip" -OutFile "$env:TEMP\paid-ads-review.zip"; Expand-Archive "$env:TEMP\paid-ads-review.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.0 KB
agents/1 file · 212 B

Read the files here

nowork-studio/5229d212 files

SKILL.md2.0 KB

Shared references2SKILL.md reads these from elsewhere in the repo. Not in the ZIP.

Get them on GitHub ↗

SKILL.md

Show the full text24 lines

paid-ads-review/SKILL.md24 lines · 2.0 KB

PreviewCode

Outline

RawView on GitHub

Paid Ads Review

Read ../shared/operating-contract.md and ../shared/measurement-framework.md. This is read-only.

Assemble comparable evidence

Check which sources are actually connected, request the missing export rather than reporting a failed call, and use the most recent complete equivalent window. For every source, keep currency, conversion definition, attribution window, and reporting lag visible. Verify tracking before treating CPA, ROAS, or revenue as a decision-grade metric.

For live platform accounts, hand data collection and diagnostics to /notfair:google-ads, /notfair:meta-ads, /notfair:paid-ads-x, /notfair:paid-ads-linkedin, /notfair:paid-ads-reddit, or /notfair:paid-ads-tiktok. Keep Amazon and ChatGPT Ads review grounded in a verified connector or supplied platform export.

Report the decision, not a dashboard transcription

Lead with the strongest contributor, the largest risk, and one recommended next action. Include a platform scorecard with spend, qualified conversions, CPA, attributable revenue/ROAS where available, link CTR, and pace against the declared budget. Compare each row to the preceding equivalent period and name the likely driver only when data supports it.

Do not present an unqualified blended CPA or ROAS. If a cross-channel aggregate is useful, label the consistent conversion definition, attribution source, spend-weighted formula, and included channels. Separate confirmed facts from inference and mark absent tracking or data as a blocking limitation.

End with hold, investigate, or one proposed action; route mutations to /notfair:paid-ads-optimize or the relevant platform operator skill.

1	---
2	name: paid-ads-review
3	description: Produce a read-only, evidence-based paid-media performance review across connected platforms or supplied exports. Use for weekly or monthly reports, scorecards, performance, CPA, ROAS, CTR, spend trends, pacing, or conversion-tracking health.
4	argument-hint: "<date range, platform, or 'weekly review'>"
5	---
6
7	# Paid Ads Review
8
9	Read `../shared/operating-contract.md` and `../shared/measurement-framework.md`. This is read-only.
10
11	## Assemble comparable evidence
12
13	Check which sources are actually connected, request the missing export rather than reporting a failed call, and use the most recent complete equivalent window. For every source, keep currency, conversion definition, attribution window, and reporting lag visible. Verify tracking before treating CPA, ROAS, or revenue as a decision-grade metric.
14
15	For live platform accounts, hand data collection and diagnostics to `/notfair:google-ads`, `/notfair:meta-ads`, `/notfair:paid-ads-x`, `/notfair:paid-ads-linkedin`, `/notfair:paid-ads-reddit`, or `/notfair:paid-ads-tiktok`. Keep Amazon and ChatGPT Ads review grounded in a verified connector or supplied platform export.
16
17	## Report the decision, not a dashboard transcription
18
19	Lead with the strongest contributor, the largest risk, and one recommended next action. Include a platform scorecard with spend, qualified conversions, CPA, attributable revenue/ROAS where available, link CTR, and pace against the declared budget. Compare each row to the preceding equivalent period and name the likely driver only when data supports it.
20
21	Do not present an unqualified blended CPA or ROAS. If a cross-channel aggregate is useful, label the consistent conversion definition, attribution source, spend-weighted formula, and included channels. Separate confirmed facts from inference and mark absent tracking or data as a blocking limitation.
22
23	End with `hold`, `investigate`, or one proposed action; route mutations to `/notfair:paid-ads-optimize` or the relevant platform operator skill.
24