performance-review

Installation
SKILL.md

Performance Review

Generators make bets: a ★ Quick Pick, a priority-1 cluster, a recommended A/B. This skill checks the bets against real numbers, writes what held up into ./brand/learnings.md as priors every generator reads and applies, and names the one bottleneck worth fixing next. Done means a diagnosis a skeptic would sign, priors a generator can apply without interpretation, and 3-5 next actions ranked by expected impact, never a wall of charts. The pipeline below is a floor, not a ceiling. Better judgment for the data in hand wins, stated in one line. The two hard rules below are not defaults.

Two hard rules govern everything below:

  1. Read-only. API access is GET and report-query endpoints only. This skill never modifies a campaign, a contact, a property, or a setting on any connected platform.
  2. Learnings come from data. Every learnings entry carries n= and source:. A finding without a sample size and a provenance is a remark in the report, not a prior.

Context

Only if ./brand/, ./brands/ or MARKETING.md exists (nothing to load otherwise), run: python3 ${CLAUDE_SKILL_DIR}/../start-here/scripts/brand_context.py --for performance-review (${CLAUDE_SKILL_DIR} is this skill's folder; outside Claude Code use the folder this file was read from, e.g. .agents/skills/performance-review. If the script or python3 is unavailable, read the brand folder directly: ./brands/<slug>/ when ./brands/active names one, else ./brand/; then MARKETING.md, preferences.md and the files in reads: (assets.md, learnings.md, brand.yaml, keyword-plan.md#cluster-priorities). If none exist, proceed standalone: the user's pasted data is still reviewable, and entity matching degrades to whatever the data itself names.)

Also check .env (and the campaign dirs referenced by brand.yaml) for the optional keys above. They determine which live pulls are available in Phase 1.

Modes

Installs
203
GitHub Stars
767
First Seen
6 days ago