Skip to content
Back to skills

Lichtenstein Creative Testing

ASecurity

Build a Meta Ads creative testing plan with separate exploration and iteration, weekly production waves, actionable creator briefs, and evidence-based review rules. Use when planning tests, refreshing fatigued ads, or turning creative results into the next production cycle.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 2, 2026
ai-agentstestingperformance

Security analysis

A100/100

Pro scans all 8 files and shows the line behind each finding

Scanned October 2, 2026

npx -y skills add getedgehq/skills --skill lichtenstein-creative-testing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lichtenstein Creative Testing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Lichtenstein Creative Testing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/getedgehq-lichtenstein-creative-testing/badge)](https://www.skillsdirectory.com/skills/getedgehq-lichtenstein-creative-testing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: lichtenstein-creative-testing
description: "Build a Meta Ads creative testing plan with separate exploration and iteration, weekly production waves, actionable creator briefs, and evidence-based review rules. Use when planning tests, refreshing fatigued ads, or turning creative results into the next production cycle."
---

# Lichtenstein Creative Testing

Based on Denys Lichtenstein's public method. Not affiliated with or endorsed by Denys Lichtenstein.

## When to use

Use this skill to turn an account's creative bottleneck into a repeatable testing and production cycle. It supports a new testing agenda, a refresh plan for fatigued campaigns, UGC creator briefs, and a review of results that should inform the next wave. Produce a practical plan using [templates/output-template.md](templates/output-template.md), with hypotheses, briefs, measurement rules, responsibilities, and a learning log.

The core distinction is between Exploration, which discovers substantially different concepts, and Iteration, which improves an evidenced winner. Keep both visible. A backlog of cosmetic variations cannot substitute for new ideas, and continually replacing everything cannot substitute for exploiting what already works.

Treat the published volume ranges as starting points: 8 to 12 substantively distinct creatives per campaign, replenished through weekly waves of 3 to 5 variants. Adjust explicitly to budget, production capacity, and the signal each test can realistically receive. These are different counts, not requirements to launch 12 new ads every week. No universal budget split, CPA threshold, or conversion minimum is supplied by the public method.

## Procedure

1. **Establish the decision and evidence.** Read the attribution boundaries in [references/method.md](references/method.md#1-scope-and-evidence). Record the product, offer, objective, existing results, capacity, and missing inputs. Separate account facts from assumptions. Use [references/sources.md](references/sources.md) to check the origin of methodological claims, especially when adding a numerical rule.

2. **Check measurement and economics.** Follow [references/method.md](references/method.md#2-measurement-and-business-context). Identify the conversion event, attribution window, CPA or other business target, and tracking gaps. Put account-level MER and contribution margin beside platform results. A measurement problem makes the test inconclusive rather than proving the creative failed.

3. **Classify the creative inventory.** Apply [references/method.md](references/method.md#3-two-separate-testing-lanes). Label each asset as exploratory, an iteration of a named winner, or unproven. Count genuine concepts separately from exports and hook variants. Preserve parent asset IDs so learnings remain traceable.

4. **Build a ranked hypothesis backlog.** Use [references/method.md](references/method.md#4-hypotheses-and-substantive-diversity). State the customer situation, expected response, and reason. Cover Emotion, Funktion, and Social Proof where appropriate. Rank by useful uncertainty and production feasibility; do not fill a quota with unsupported messages.

5. **Specify what each test can teach.** Follow [references/method.md](references/method.md#5-discovery-versus-variable-isolation). For exploration, compare clearly named concept packages and limit conclusions to those packages. For iteration, select one lever, starting with the hook, and hold the rest stable. Record unavoidable confounders before launch.

6. **Fix the cadence and feasible volume.** Use [references/method.md](references/method.md#6-cadence-volume-and-capacity) to schedule production, release, and review. Reserve room for both lanes without inventing a mandatory ratio. If budget cannot support useful signal, narrow the simultaneous batch and explain the adjustment.

7. **Write briefs creators can execute.** Fill the brief fields in [templates/output-template.md](templates/output-template.md). Specify one angle, a concrete opening shot and hook, a problem-to-solution-to-action structure, evidence, and creative freedom. Batch related footage in one session while preserving distinct concept IDs.

8. **Set decisions before seeing results.** Apply [references/method.md](references/method.md#8-predeclared-review-and-routing). Define sufficient evidence, attribution maturation, winner and loser conditions, spending boundaries, and a bounded retest for borderline results. Mark missing thresholds as unresolved account choices, never as Lichtenstein's defaults.

9. **Review performance and fatigue together.** Follow [references/method.md](references/method.md#9-fatigue-and-the-next-wave). Examine CPM trends with frequency and CTR, then check market or account changes. Route supported winners into iteration, evidenced losers into the learning log, and ambiguous results into a defined follow-up.

10. **Deliver the next executable cycle.** Complete [templates/output-template.md](templates/output-template.md), compare the plan with [examples/worked-examples.md](examples/worked-examples.md), and run [checklists/review-checklist.md](checklists/review-checklist.md). Include owners, dates, decisions, and uncertainties. Delivering this plan does not itself authorize publishing ads or changing spend.

## Files in this skill

- [SLUG.txt](SLUG.txt): Package identifier matching the front matter name.
- [SKILL.md](SKILL.md): Entry point, usage boundaries, and execution procedure.
- [references/method.md](references/method.md): Detailed principles, decision rules, warnings, and edge cases with source citations.
- [references/sources.md](references/sources.md): Numbered public sources fetched with curl and their specific contributions.
- [examples/worked-examples.md](examples/worked-examples.md): Invented illustrations showing weak drafts, corrected plans, and resulting decisions.
- [templates/output-template.md](templates/output-template.md): Fill-in deliverable with field guidance for the full testing cycle.
- [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail review criteria and repairs for common mistakes.

Files in this skill

  • DERIVATION.json2.8 KB
  • LICENSE10.5 KB
  • SKILL.md6 KB
  • checklists/review-checklist.md4.9 KB
  • examples/worked-examples.md8.5 KB
  • references/method.md14.7 KB
  • references/sources.md5.5 KB
  • templates/output-template.md6.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.