creative-ops
Skill1 starsChanged 6 months agoMITView on GitHub
LinkedIn ad creative testing and iteration engine. Use when: test new creative for [audience], generate linkedin ad variants for [campaign], design an a/b test for our [value prop] ads, why did our last linkedin test fail to declare a winner?, refresh ads - we’re seeing creative fatigue, score our linkedin ad performance.
In this repository12 other files it gives its agents.
- content-opsSkill
- conversion-opsSkill
- finance-opsSkill
- growth-engineSkill
- outbound-engineSkill
- podcast-opsSkill
- revenue-intelligenceSkill
- sales-pipelineSkill
- sales-playbookSkill
- seo-opsSkill
- team-opsSkill
- voice-guardSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Test new creative for [audience]
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Creative Ops
LinkedIn ad creative testing and iteration engine. Closes the loop performance marketers burn the most cycles on: generating fresh creative variants across multiple angles, structuring statistically valid A/B tests against realistic audience sizes, and learning from results so the next iteration is sharper than the last - not just different. Pairs naturally with Sales Pipeline (audience signals from intent scoring) and Revenue Intelligence (which messaging wins deals downstream).
When to Use
- Test new creative for [audience]
- Generate LinkedIn ad variants for [campaign]
- Design an A/B test for our [value prop] ads
- Why did our last LinkedIn test fail to declare a winner?
- Refresh ads - we're seeing creative fatigue
- Score our LinkedIn ad performance
Workflow
- Brief Intake - target audience description, value prop, optional current best-performing creative, audience size estimate, weekly budget
- 3-Angle Variant Generation - produce 6 creatives:
- 2 × Problem/Solution (lead with pain → product as resolution)
- 2 × Social Proof (lead with customer outcome → product as the cause)
- 2 × Contrarian (challenge conventional wisdom → product as the new way) Each variant includes: headline, intro line (first 150 chars), CTA, visual brief, and the single hypothesis it tests
- Test Structure Design:
- Map each variant to a budget split (typically equal allocation unless a control needs protection)
- Compute MDE for the audience size at 80% power, α = 0.05
- Pick stopping rule (Sequential / Bayesian / Fixed Horizon) based on weekly impressions
- Pre-Mortem - list the top 3 failure modes with mitigations (e.g., "Audience too narrow → MDE > 30% → relax interest filters or extend test 2 weeks")
- Live Monitoring Plan - daily KPIs to watch (CTR, CPL, frequency), early-stop triggers, and which variant gets cut first if budget reallocation is needed
- Post-Test Diagnostic:
- Winning variant + statistical confidence (posterior probability if Bayesian, p-value if frequentist)
- Angle-level signal: did one of the 3 strategic angles dominate? If yes, that's a learning, not just a win
- Segment cuts: did the win hold across job titles / company sizes, or was it driven by one segment?
- Next-iteration recommendation: which winning element to lock in and which dimension to test next
- Promote to Playbook - winning creative + full context archived so future iterations build on prior learnings instead of starting from scratch
Reference
Full methodology lives in README.md in this folder: configuration, scoring formulas, output formats, integration points, and worked examples. Read it before producing scored output.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

