Agent skill
ecom-learning-loop
Persist creatives + prompts + angles + performance tags so you can generate new variants from data (e.g., “make 20 new variants of our best angle”).
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/skill-walkerhi11-mediabuy-plugins-3
SKILL.md
Ecom Learning Loop (Creative Memory → Next Tests)
Goal: turn ad testing into a compounding system:
- store what you made (angle, prompt, format, creator)
- store what happened (spend, CTR, CPA, purchases)
- generate the next tests from data, not vibes
Required output (create this file)
Maintain a registry file (recommended):
outputs/meta-creative-registry.json
Each item should store:
id,type(image/video/copy),source_pathor URLtags:brand:*,product:*,angle:*,format:*,hook:*,stage:*performance: spend, impressions, ctr, cpa/cpp, roas, purchases, notes
Minimal tagging taxonomy
brand:<slug>product:<slug>angle:<angle_id>format:<ugclook|product|proof|comparison|howto|video>hook:<hook_type>stage:<unaware|problem|solution|product|most>
Winner → 20 variants workflow
- Pick the best creative for an angle (by CPA/ROAS) and document why it worked.
- Generate a “subtle change” prompt pack: 10–30 variants preserving the core mechanism.
- Launch and tag the variants with the same
angle:<angle_id>so you can attribute learnings.
Operating rhythm
- Daily: log every launched creative + copy variant
- Daily: write back results (wins and losses)
- Weekly: export top angles + mechanisms and plan a new creative sprint
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?