Creative performance analysis skill

Diagnose why a specific ad creative is winning or losing using the generalized hook-hold-click-convert funnel, applicable across any platform.

by gmmh1·MIT license·★ 0 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Creative Performance Analysis

> **Currency & scope note (last reviewed 2026-07-19):** Platform mechanics referenced here (character limits, campaign-type names, feature…

## Purpose
Provide the generalized diagnostic funnel — hook, hold, click, convert — for locating exactly where a specific ad creative is failing, so t…

## Trigger Conditions
- "Why is this ad underperforming"
- "Diagnose my creative performance"
- "Where in the funnel is this ad failing"

## Required Inputs
- Creative-level performance data appropriate to the platform: impressions, hook/thumbstop-style early-retention metric where available, ho…
- The angle/format/hook used, so findings map back to creative decisions
- Sufficient volume for the data to be meaningful (coordinate with `creative-testing-framework`)

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Creative performance analysis

gmmh1/main1 file shown
SKILL.md
Show the full text65 lines

Creative Performance Analysis

Currency & scope note (last reviewed 2026-07-19): Platform mechanics referenced here (character limits, campaign-type names, feature availability, thresholds, benchmark figures, policy specifics) reflect general practice as of the review date above and are not guaranteed current — ad platforms change quickly. Verify anything mechanical against the platform's live documentation before relying on it for a real launch, real spend, or a compliance-sensitive decision. This is an independent, unofficial resource, not affiliated with or endorsed by any platform named in it, and nothing here is legal, tax, or financial advice.

Purpose

Provide the generalized diagnostic funnel — hook, hold, click, convert — for locating exactly where a specific ad creative is failing, so the fix targets the actual problem instead of guessing.

Trigger Conditions

  • "Why is this ad underperforming"
  • "Diagnose my creative performance"
  • "Where in the funnel is this ad failing"

Required Inputs

  • Creative-level performance data appropriate to the platform: impressions, hook/thumbstop-style early-retention metric where available, hold/completion metric where available, CTR, CPA/conversion rate
  • The angle/format/hook used, so findings map back to creative decisions
  • Sufficient volume for the data to be meaningful (coordinate with creative-testing-framework)

Core Capabilities

The Universal Diagnostic Funnel
  • Hook (did it stop the scroll/earn the first look): measured as thumbstop rate, 3-second view rate, or early CTR depending on platform and format — a video/feed-native format's most measurable early-retention proxy
  • Hold (did it keep attention once earned): completion rate, average watch time, or scroll-depth on longer static/carousel formats
  • Click (did it convert attention into action): CTR, the most universally available metric across every platform in this library
  • Convert (did the click become the actual business outcome): CPA/ROAS/conversion rate — where the funnel meets the landing page/offer, no longer purely a creative-quality question
Locating the Failure Point
  • Weak hook, everything downstream unmeasurable: the fix is entirely upstream — new opening frame/line, not a downstream tweak
  • Strong hook, weak hold: pacing/structure problem in the middle of the asset — fixable without touching the opening
  • Strong hook and hold, weak click: the message/CTA isn't compelling enough to act on, even though attention was earned — a copy/offer problem, not an attention problem
  • Strong click, weak convert: the creative did its job; the problem has moved downstream to landing page, offer terms, or audience-offer mismatch — not a creative fix at all
Cross-Platform Metric Translation
  • Recognizing that each platform names and measures these funnel stages slightly differently (Meta's ThruPlay vs. TikTok's completion rate vs. Google's view-through metrics) but the underlying diagnostic logic transfers directly
  • Avoiding false comparison of raw metric values across platforms (a "good" CTR on Search is a very different number than a "good" CTR on Display) — the diagnostic funnel structure transfers, the absolute benchmarks don't
Comparative Analysis
  • Comparing only within matched test conditions (same audience/placement/budget), consistent with creative-testing-framework's variable-isolation principle
  • Distinguishing a sustained pattern from a novelty-driven spike, watching trend over the test's full duration rather than a single snapshot

Workflow

  1. Pull creative-level performance data for the asset(s) in question, confirming sufficient volume.
  2. Walk the funnel — hook, hold, click, convert — locating the specific stage where performance drops off relative to comparable assets.
  3. Map the failure point to the correct fix category: creative opening (hook), pacing/structure (hold), message/offer (click), or downstream landing page/audience fit (convert).
  4. Route the fix to the appropriate skill: platform creative-strategy skill for hook/hold issues, copywriting skill for click issues, landing-page-audit-equivalent skill for convert issues.

Outputs

  • Funnel breakdown per asset (hook/hold/click/convert performance)
  • Failure point diagnosis with the specific stage identified
  • Fix category and routing recommendation

Rules

  • Always locate the specific funnel stage where an asset is failing before recommending a fix — a hook problem and a landing page problem can produce identical-looking CPA numbers but need completely different fixes.

  • Never compare raw metric values across platforms as if they're on the same scale; compare the funnel-stage pattern, not the absolute numbers.

  • Distinguish sustained underperformance from noise, per creative-testing-framework's statistical discipline.

  • Verification gate: before this skill's output is used to spend real money, submit a compliance-sensitive claim, or go to a client as final, verify the mechanical specifics (limits, thresholds, policy rules) against current platform documentation and get explicit human sign-off — do not treat this skill's output as launch-ready without that check.

creative-testing-framework (statistical rigor behind this analysis), meta-ads-creative-analytics (platform-specific application), google-ads-landing-page-audit (convert-stage downstream fix), creative-fatigue-management (when a previously strong asset starts failing over time rather than from the start).

1---
2name: creative-performance-analysis
3description: "Diagnose why a specific ad creative is winning or losing using the generalized hook-hold-click-convert funnel, applicable across any platform. Triggers on 'why is this ad underperforming', 'diagnose my creative', or 'where in the funnel is this ad failing'. Platform-agnostic diagnostic framework — platform-specific versions (meta-ads-creative-analytics) apply this with platform-native metrics."
4---
5 
6# Creative Performance Analysis
7 
8> **Currency & scope note (last reviewed 2026-07-19):** Platform mechanics referenced here (character limits, campaign-type names, feature availability, thresholds, benchmark figures, policy specifics) reflect general practice as of the review date above and are **not guaranteed current** — ad platforms change quickly. Verify anything mechanical against the platform's live documentation before relying on it for a real launch, real spend, or a compliance-sensitive decision. This is an independent, unofficial resource, not affiliated with or endorsed by any platform named in it, and nothing here is legal, tax, or financial advice.
9 
10## Purpose
11Provide the generalized diagnostic funnel — hook, hold, click, convert — for locating exactly where a specific ad creative is failing, so the fix targets the actual problem instead of guessing.
12 
13## Trigger Conditions
14- "Why is this ad underperforming"
15- "Diagnose my creative performance"
16- "Where in the funnel is this ad failing"
17 
18## Required Inputs
19- Creative-level performance data appropriate to the platform: impressions, hook/thumbstop-style early-retention metric where available, hold/completion metric where available, CTR, CPA/conversion rate
20- The angle/format/hook used, so findings map back to creative decisions
21- Sufficient volume for the data to be meaningful (coordinate with `creative-testing-framework`)
22 
23## Core Capabilities
24 
25### The Universal Diagnostic Funnel
26- **Hook** (did it stop the scroll/earn the first look): measured as thumbstop rate, 3-second view rate, or early CTR depending on platform and format — a video/feed-native format's most measurable early-retention proxy
27- **Hold** (did it keep attention once earned): completion rate, average watch time, or scroll-depth on longer static/carousel formats
28- **Click** (did it convert attention into action): CTR, the most universally available metric across every platform in this library
29- **Convert** (did the click become the actual business outcome): CPA/ROAS/conversion rate — where the funnel meets the landing page/offer, no longer purely a creative-quality question
30 
31### Locating the Failure Point
32- Weak hook, everything downstream unmeasurable: the fix is entirely upstream — new opening frame/line, not a downstream tweak
33- Strong hook, weak hold: pacing/structure problem in the middle of the asset — fixable without touching the opening
34- Strong hook and hold, weak click: the message/CTA isn't compelling enough to act on, even though attention was earned — a copy/offer problem, not an attention problem
35- Strong click, weak convert: the creative did its job; the problem has moved downstream to landing page, offer terms, or audience-offer mismatch — not a creative fix at all
36 
37### Cross-Platform Metric Translation
38- Recognizing that each platform names and measures these funnel stages slightly differently (Meta's ThruPlay vs. TikTok's completion rate vs. Google's view-through metrics) but the underlying diagnostic logic transfers directly
39- Avoiding false comparison of raw metric values across platforms (a "good" CTR on Search is a very different number than a "good" CTR on Display) — the diagnostic funnel structure transfers, the absolute benchmarks don't
40 
41### Comparative Analysis
42- Comparing only within matched test conditions (same audience/placement/budget), consistent with `creative-testing-framework`'s variable-isolation principle
43- Distinguishing a sustained pattern from a novelty-driven spike, watching trend over the test's full duration rather than a single snapshot
44 
45## Workflow
461. Pull creative-level performance data for the asset(s) in question, confirming sufficient volume.
472. Walk the funnel — hook, hold, click, convert — locating the specific stage where performance drops off relative to comparable assets.
483. Map the failure point to the correct fix category: creative opening (hook), pacing/structure (hold), message/offer (click), or downstream landing page/audience fit (convert).
494. Route the fix to the appropriate skill: platform creative-strategy skill for hook/hold issues, copywriting skill for click issues, landing-page-audit-equivalent skill for convert issues.
50 
51## Outputs
52- Funnel breakdown per asset (hook/hold/click/convert performance)
53- Failure point diagnosis with the specific stage identified
54- Fix category and routing recommendation
55 
56## Rules
57- Always locate the specific funnel stage where an asset is failing before recommending a fix — a hook problem and a landing page problem can produce identical-looking CPA numbers but need completely different fixes.
58- Never compare raw metric values across platforms as if they're on the same scale; compare the funnel-stage pattern, not the absolute numbers.
59- Distinguish sustained underperformance from noise, per `creative-testing-framework`'s statistical discipline.
60 
61- **Verification gate:** before this skill's output is used to spend real money, submit a compliance-sensitive claim, or go to a client as final, verify the mechanical specifics (limits, thresholds, policy rules) against current platform documentation and get explicit human sign-off — do not treat this skill's output as launch-ready without that check.
62 
63## Related Skills
64`creative-testing-framework` (statistical rigor behind this analysis), `meta-ads-creative-analytics` (platform-specific application), `google-ads-landing-page-audit` (convert-stage downstream fix), `creative-fatigue-management` (when a previously strong asset starts failing over time rather than from the start).
65 

Discussion

Alternatives

Professional Full-Stack Developer for Network Mapping & Monitoring ApplicationAct as a professional full-stack developer tasked with building a web application for mapping and monitoring networks using Mikrotik Netwatch API. Implement multi-user role-based management to handle devices, monitor their status, and manage user subscriptions.Coding · CC0-1.0Constraint driven developmentEstablishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.Coding · MITObservability and instrumentationInstruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.Coding · MITPerformance optimizationOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Coding · MIT