Agent skill
ecom-meta-testing-os
Ecom-specific Meta testing operating system: naming conventions, creative matrix presets, pausing/scaling guardrails, and daily reporting.
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-6
SKILL.md
Ecom Meta Testing OS (Launch → Learn → Iterate)
This skill standardizes how you run Meta tests so learnings compound.
Inputs
ads/ads.csv(angle IDs, copy, creative prompts)- Baseline business truth: AOV, margin, shipping, inventory, target CPA/CAC
Naming conventions (do this or you can’t learn fast)
- Campaign:
ECOM-{brand}-{product}-{YYYYMMDD}-{test_id} - Ad set:
AUD-{audience_name} - Ad:
ANG-{angle_id}__IMG-{img_id}__COPY-{copy_id}
UTM minimums
utm_source=metautm_medium=paid_socialutm_campaign=<campaign_name>utm_content=angle:{angle_id}|img:{img_id}|copy:{copy_id}
Default test presets
Creative matrix (starter)
- 6–12 angles × 2–3 image variants × 3–5 primary text variants
- Broad audiences first; add 1–2 “intent proxy” audiences if needed
Spend-gated guardrails (starter)
- Don’t kill too early: require a spend threshold before pausing.
- Scale only after stable conversions and clean tracking.
Daily operator checklist
- Verify tracking (Pixel/CAPI events) before “creative changes”
- Identify winners by CPA/ROAS + volume
- Generate 10–30 variants for the best angle(s)
- Pause clear losers after spend threshold
- Log learnings into your creative registry (angle → prompt → KPI)
Measurement note (Pixel/CAPI)
If results are noisy, fix signal first:
- Event deduplication
- Purchase value accuracy
- Matching quality (CAPI / enhanced conversions)
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?