Mmcp.market

ad-campaign-analyzer skill

by github·github/awesome-copilot·39k stars·MIT

Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign planning or creative generation without performance data.

A100/100content scan

Is the ad-campaign-analyzer skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the ad-campaign-analyzer skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/github/awesome-copilot.git /tmp/awesome-copilot
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-copilot/skills/ad-campaign-analyzer ~/.claude/skills/ad-campaign-analyzer
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Ad Campaign Analyzer

Take raw campaign performance data and turn it into clear decisions. This skill doesn't just summarize metrics — it diagnoses problems, identifies winners, checks statistical significance, and tells you exactly what to cut, scale, and test next. Then it goes further: it compares channels on equal terms, finds where you're over-spending vs under-spending relative to results, and produces a concrete budget reallocation plan.

Core principle: Most startup founders check their ad dashboard, see a ROAS number, and either panic or celebrate. This skill gives you the nuanced analysis a paid media specialist would: what's actually significant, what's noise, and where your next dollar should go. It also solves the allocation problem — most startups either spread budget too thin across channels (no channel gets enough to learn) or dump everything into one channel (missing cheaper opportunities elsewhere).

When to Use

  • "Analyze my Google Ads performance"
  • "Which ads should I kill?"
  • "Is this campaign working?"
  • "Where am I wasting ad spend?"
  • "Optimize my Meta Ads"
  • "How should I split my ad budget?"
  • "Should I spend more on Google or Meta?"
  • "Reallocate my ad spend across channels"
  • "Where am I getting the best return?"
  • "I have $X/month for ads — how should I distribute it?"

Phase 0: Intake

  1. Campaign data — One of:
  • CSV export from Google Ads / Meta Ads Manager / LinkedIn Campaign Manager
  • Pasted performance table
  • Screenshots of dashboard (we'll extract the data)
  1. Platform(s) — Google / Meta / LinkedIn / All
  2. Time period — What date range does this cover?
  3. Monthly budget — Total ad spend in this period
  4. Primary goal — What conversion are you optimizing for? (Demos / Trials / Purchases / Leads)
  5. Target metrics — Do you have target CPA or ROAS? (If not, we'll benchmark)
  6. Any known changes? — Did you change creative, budget, or targeting during this period?
  7. Channels currently running — Google Ads, Meta Ads, LinkedIn Ads, Twitter/X Ads, TikTok Ads, other
  8. Funnel data (if available):
  • Lead → MQL rate
  • MQL → SQL rate
  • SQL → Close rate
  • Average deal size
  1. Channels you're considering but haven't tried — Want to test new channels?
  2. Constraints — Minimum spend on any channel? Platform you must stay on?

Phase 1: Data Ingestion & Normalization

Accepted Data Formats

Normalize all data into a standard analysis format:

Multi-Channel Normalization

When data spans multiple channels, also produce a channel-level rollup:

*CAC = Full customer acquisition cost if funnel data provided (CPA × close-rate adjustment)

Funnel-Adjusted CAC (If Funnel Data Available)

Channel CAC = CPA ÷ (MQL rate × SQL rate × Close rate)

This reveals which channels produce leads that actually close, not just convert.

Phase 2: Performance Diagnostics

2A: Campaign-Level Health Check

For each campaign:

2B: Budget Waste Detection

Identify spend that produced no or negative return:

2C: Winner Identification

Find what's actually working:

2D: Statistical Significance Check

For any A/B test (ad variants, audiences, landing pages):

Test: [Variant A] vs [Variant B]
Metric: [Conv Rate / CTR / CPA]
Variant A: [X%] (n=[sample_size])
Variant B: [Y%] (n=[sample_size])
Confidence level: [X%]
Verdict: [Statistically significant / Not enough data / Too close to call]
Recommended action: [Pick winner / Continue test / Increase budget to reach significance]

Minimum sample: 100 clicks per variant for CTR tests, 30 conversions per variant for CPA tests.

Phase 3: Funnel Analysis

Click → Conversion Path

Impressions: [N] (100%)
     ↓ CTR: [X%]
Clicks: [N] ([X%] of impressions)
     ↓ Landing page → Conversion: [X%]
Conversions: [N] ([X%] of clicks)
     ↓ Conversion → Revenue: $[X] avg
Revenue: $[N]

Funnel Drop-Off Diagnosis

Phase 4: Budget Reallocation

When data spans multiple channels, perform cross-channel budget optimization.

4A: Channel Efficiency Ranking

Efficiency Index:

  • > 1.0 = Under-invested (getting more than its share of conversions)
  • = 1.0 = Proportional (fair share)
  • < 1.0 = Over-invested (getting less than its share)

4B: Marginal Return Analysis

For each channel, estimate if additional spend would yield proportional returns:

4C: Funnel Stage Coverage

4D: Budget Shift Recommendations

4E: Scenario Modeling

Scenario 1: Conservative shift (+/- 20%)

  • Expected conversions: [N] (currently [N]) = [X%] improvement
  • Expected blended CPA: $[X] (currently $[X])
  • Risk: Low

Scenario 2: Aggressive shift (+/- 40%)

  • Expected conversions: [N] = [X%] improvement
  • Expected blended CPA: $[X]
  • Risk: Medium — less data on scaled channels

Scenario 3: Budget increase to $[Y]/mo

  • Recommended allocation: [table]
  • Expected conversions: [N]
  • New channels to test: [list]

Phase 5: Output Format

# Ad Campaign Analysis — [Product/Client] — [DATE]

Period: [Date range]
Total spend: $[X]
Platform(s): [Google / Meta / LinkedIn]
Primary goal: [Conversions / Revenue / Leads]

---

## Executive Summary

[3-5 sentences: Overall performance verdict, biggest win, biggest problem, top recommendation including any reallocation moves]

---

## Performance Dashboard

| Campaign | Spend | Impressions | Clicks | CTR | CPC | Conversions | CPA | ROAS | Verdict |
|----------|-------|------------|--------|-----|-----|-------------|-----|------|---------|
| [Name] | $[X] | [N] | [N] | [X%] | $[X] | [N] | $[X] | [X] | [Scale/Optimize/Pause] |

---

## Budget Waste Report

**Total estimated waste: $[X] ([X%] of total spend)**

### Wasted on zero-conversion items: $[X]
[List of keywords/ads/audiences with spend but no conversions]

### Wasted on high-CPA items: $[X]
[List of items with CPA > 3x target]

### Recommended saves: $[X]/month
[Specific items to pause]

---

## Winners to Scale

### Top Keywords/Audiences
| Item | CPA | Conv Rate | Current Spend | Recommended Spend |
|------|-----|----------|--------------|-------------------|

### Top Ads
| Ad | CTR | Conv Rate | Why It Works |
|----|-

Save to campaign-analysis-[YYYY-MM-DD].md in the current working directory (or user-specified path).

Cost

Tools Required

  • No external tools needed — pure reasoning skill
  • User provides campaign data as CSV, paste, or screenshot

Trigger Phrases

  • "Analyze my ad campaign performance"
  • "Which ads should I pause?"
  • "Where am I wasting ad budget?"
  • "Is my Google Ads campaign working?"
  • "Optimize my Meta Ads spend"
  • "How should I allocate my ad budget?"
  • "Should I spend more on Google or Meta?"
  • "Reallocate my ad spend"
  • "Where am I getting the best ROAS?"
  • "Optimize my multi-channel ad budget"

More skills from github/awesome-copilot

  • Aacquire-codebase-knowledgeUse this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
  • Aacreadiness-assessRun the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
  • Aacreadiness-generate-instructionsGenerate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
  • Aacreadiness-policyHelp the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
  • Aadd-educational-commentsAdd educational comments to the file specified, or prompt asking for file to comment if one is not provided.
  • Aadobe-illustrator-scriptingWrite, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model, coordinate system, measurement units, export workflows, and scripting best practices.
  • Aagent-architectureDesign AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents. Architecture only; excludes implementation and general code review.
  • Aagent-governancePatterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)
  • Aagent-owasp-complianceCheck any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"
  • Aagent-skill-stackFind, evaluate, and assemble the smallest compatible set of AI Agent Skills for an end-to-end natural-language goal. Use when a user wants Skills for a multi-step workflow, asks which Skills fit a project, needs an installed-Skill audit or conflict check, has low Skill recall, wants indirect helpers such as humanizers or compliance checks, or wants a project-specific Skill Stack with controlled installation. Search local Skills, registries, GitHub, and OpenCLI; compare adoption, verified fit, safety, and overlap. Do not use for locating one known or common Skill; use the generic find-skills workflow.
  • Aagent-supply-chainVerify supply chain integrity for AI agent plugins, tools, and dependencies. Use this skill when: - Generating SHA-256 integrity manifests for agent plugins or tool packages - Verifying that installed plugins match their published manifests - Detecting tampered, modified, or untracked files in agent tool directories - Auditing dependency pinning and version policies for agent components - Building provenance chains for agent plugin promotion (dev → staging → production) - Any request like "verify plugin integrity", "generate manifest", "check supply chain", or "sign this plugin"
  • Aagentic-evalPatterns and techniques for evaluating and improving AI agent outputs. Use this skill when: - Implementing self-critique and reflection loops - Building evaluator-optimizer pipelines for quality-critical generation - Creating test-driven code refinement workflows - Designing rubric-based or LLM-as-judge evaluation systems - Adding iterative improvement to agent outputs (code, reports, analysis) - Measuring and improving agent response quality

All agent skills → · MCP servers