Agent skill · Code Review & Quality

03-performance-eval-global

Diagnose marketing performance for global businesses — root cause analysis, 5-Whys, 48-hour action plan. Has 4 region variants for benchmarks (US/EU/SEA/LATAM). Reads `.agents/product-marketing-context-global.md`. INCLUDES Dropshipping KPI section (ROAS, BE-ROAS, profit margin, CAC). Trigger: 'performance review', 'ad performance', 'marketing diagnosis', 'KPI analysis', 'dropshipping ROAS'.

minhnv0807491★ · 1 repos on radarProfile →
claude-codecopilotcursorMIT
Install
npx skills add minhnv0807/ai-business-skills --skill 03-performance-eval-global --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 13 KB
Bundled scripts: none
Version: 1.0.0
Path: skills/en/03-performance-eval-global/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 521
Language: PowerShell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Performance Evaluation (Global) Diagnose marketing performance — paid ads, organic, funnel — find root cause, propose optimization with 48h action plan and weekly checklist. Region variants (US/EU/SEA/LATAM) provide localized benchmarks. --- ## For newbies — Read this first If you've never done a performance review: 1. **Performance evaluation = a structured health check** of your marketing. You collect numbers, compare against benchmarks, find the gap, and propose fixes. 2. **You don't need everything perfect to start.** Even rough data (last 30 days spend + leads + revenue) is enough for a first pass. 3. **The order matters:** measure first, diagnose second, fix third. Don't jump to "let's redo creative" before checking why CTR dropped. 4. **Benchmarks are regional.** A $10 CPM in the US is normal; in SEA it's expensive. Always pick the right region variant. 5. **One metric at a time.** Don't try to fix CPM, CTR, CPL, ROAS simultaneously — pick the bottleneck and fix that first. 6. **The 5-Whys method works.** Ask "why?" five times until you hit a root cause that's actionable (process, system, or skill gap — not a symptom). 7. **Health Score 0-100** gives you a single number to

What's inside
Steps it walks through
  1. For newbies — Read this first
  2. Step 0 — Read context + select region variant
  3. Information gathering
  4. Auto-pull via MCP (if connected)
  5. Universal diagnosis framework
  6. Part 0 — Ads Health Score (0-100)
  7. Part 1 — Diagnostic decision tree
  8. Part 2 — Root Cause Analysis (5 Whys)
  9. Part 3 — Creative fatigue indicators
  10. Part 4 — Audience saturation indicators
  11. Decision tree — which variant to use
  12. Dropshipping KPI section
  13. Core KPIs
  14. BE-ROAS formula
Ships with 4 files
  • variants/01-us.md
  • variants/02-eu.md
  • variants/03-sea.md
  • variants/04-latam.md
More from ai-business-skills
All skills →
About this skill
What does the 03-performance-eval-global skill do?

Diagnose marketing performance for global businesses — root cause analysis, 5-Whys, 48-hour action plan. Has 4 region variants for benchmarks (US/EU/SEA/LATAM). Reads `.agents/product-marketing-context-global.md`. INCLUDES Dropshipping KPI section (ROAS, BE-ROAS, profit margin, CAC). Trigger: 'performance review', 'ad performance', 'marketing diagnosis', 'KPI analysis', 'dropshipping ROAS'.

How do I install it?

Run `npx skills add minhnv0807/ai-business-skills --skill 03-performance-eval-global --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From minhnv0807/ai-business-skills, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going