ad-spend-optimizer
정보
이 스킬은 Google Ads 및 Meta와 같은 플랫폼 간 광고 성과 데이터를 분석하여 광고 지출 수익률(ROAS)을 극대화하고 고객 획득 비용(CAC)을 최소화하는 예산 재배분을 권장합니다. 개발자들은 이를 통해 분기별 계획 수립, 저조한 채널 진단, 성과 변동 후 미디어 믹스 재조정에 활용할 수 있습니다. 핵심 기능은 한계 ROI를 계산하여 지출 확대 또는 축소에 관한 데이터 기반 의사결정을 지원하는 것입니다.
빠른 설치
Claude Code
추천npx skills add guia-matthieu/clawfu-skills -a claude-code/plugin add https://github.com/guia-matthieu/clawfu-skillsgit clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/ad-spend-optimizerClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Ad Spend Optimizer
Analyze paid advertising performance across channels and recommend budget reallocation to maximize ROAS and minimize CAC.
When to Use This Skill
- Quarterly budget planning — reallocate spend based on performance data
- Channel mix optimization — find the right balance across platforms
- Performance troubleshooting — diagnose why CAC is rising or ROAS declining
- Scaling decisions — determine if a channel has headroom to scale
- New channel testing — structure test budgets with clear success criteria
Methodology Foundation
| Aspect | Details |
|---|---|
| Source | Marginal ROI optimization + portfolio theory for marketing |
| Core Principle | Allocate each dollar where the marginal return is highest — shift spend from diminishing-returns channels to underspent ones |
| Framework | 70/20/10 — 70% proven channels, 20% optimization tests, 10% new channel experiments |
What Claude Does vs What You Decide
| Claude Does | You Decide |
|---|---|
| Calculates ROAS, CAC, and CPL per channel and campaign | Total budget constraints |
| Identifies diminishing returns and reallocation opportunities | Risk tolerance for new channels |
| Models projected outcomes for different allocation scenarios | Business priorities and brand considerations |
| Creates monitoring dashboards and alert thresholds | Platform selection and creative direction |
Instructions
Step 1: Audit Current Performance
Collect these metrics per channel and campaign:
| Metric | Formula | Healthy Range |
|---|---|---|
| ROAS | Revenue ÷ Ad Spend | >3:1 for most B2B/B2C |
| CAC | Ad Spend ÷ New Customers | <LTV ÷ 3 |
| CPL | Ad Spend ÷ Leads | Varies by industry |
| CTR | Clicks ÷ Impressions | >1% search, >0.5% social |
| Conv Rate | Conversions ÷ Clicks | >2% landing pages |
Validation checkpoint: If data is missing for any channel, flag it — incomplete data leads to wrong reallocations.
Step 2: Attribution Analysis
Choose the model that matches the business:
| Model | Best For | Trade-off |
|---|---|---|
| Last Click | Direct response, short cycles | Ignores awareness |
| First Click | Awareness campaigns | Ignores conversion assist |
| Linear | Balanced multi-touch view | Dilutes signal |
| Time Decay | Shorter sales cycles | Biases toward bottom-funnel |
| Position-Based | Balanced with emphasis | May miss mid-funnel |
| Data-Driven | Sophisticated, enough data | Requires volume |
Step 3: Calculate Marginal ROI
For each channel, answer: Where does the next $1 produce the most return?
| Signal | Meaning | Action |
|---|---|---|
| CAC well below target | Headroom to scale | Increase spend 50%, monitor weekly |
| CAC at target | Optimized | Maintain, test creative |
| CAC above target | Diminishing returns | Reduce spend, reallocate |
| Low volume, good CAC | Underinvested | Scale cautiously (2x) |
| High volume, rising CAC | Hitting ceiling | Cap spend, diversify |
Step 4: Model Reallocation Scenarios
Build 3 scenarios (conservative, moderate, aggressive) showing projected leads, CAC, and ROAS at each budget level. Include:
- Per-channel breakdowns with expected performance
- Warning thresholds — CAC levels that trigger spend cuts
- Implementation timeline — weekly changes, not all at once
Step 5: Implement and Monitor
Weekly monitoring checklist:
- Spend pacing vs. plan
- CAC by channel vs. target
- Lead volume vs. forecast
- Any channel crossing warning threshold?
Scaling rule: If CAC stays 15%+ below target for 2 consecutive weeks, increase spend by 25%. If CAC exceeds target for 2 weeks, reduce by 25%.
Examples
Example: B2B SaaS Budget Reallocation
Input: $100K/month — Google ($50K), Meta ($30K), LinkedIn ($15K), Other ($5K). Target: $200 CAC, 500 leads/month. Current: 395 leads, $253 CAC.
Diagnosis:
- Google Display ($15K → 30 leads, $500 CAC) — cut entirely
- Meta Lookalike ($15K → 85 leads, $176 CAC) — star performer, scale
- LinkedIn Lead Gen ($5K → 10 leads, $500 CAC) — cut
Proposed reallocation:
| Channel | Current | Proposed | Expected CAC |
|---|---|---|---|
| Google Ads | $50K | $35K | $206 |
| Meta | $30K | $50K | $196 |
| $15K | $8K | $286 | |
| Testing | $5K | $7K | Variable |
Projected result: 473 leads (+20%), $211 CAC (-17%).
Skill Boundaries
What This Skill Does Well
- Analyzing multi-channel ad performance from provided data
- Recommending budget shifts based on marginal ROI
- Modeling reallocation scenarios with projected outcomes
- Creating monitoring frameworks with alert thresholds
What This Skill Cannot Do
- Access ad platform accounts or pull live data
- Make real-time bid adjustments or campaign changes
- Evaluate creative quality (headlines, images, video)
- Account for brand lift or offline conversion effects
References
- Google Ads Optimization Guide
- Meta Business Suite Best Practices
- LinkedIn Marketing Solutions
- Common Thread Collective — ad spend allocation methodology
Related Skills
google-ads-expert— Google-specific campaign optimizationaarrr-metrics— Full funnel view beyond paid acquisitiongrowth-loops— Sustainable growth beyond paid channels
GitHub 저장소
연관 스킬
evaluating-llms-harness
테스팅이 Claude Skill은 MMLU, GSM8K를 포함한 60개 이상의 표준화된 학술 과제에서 LLM 성능을 벤치마크하기 위해 lm-evaluation-harness를 실행합니다. 개발자들이 모델 품질을 비교하고, 학습 진행 상황을 추적하거나 학술 결과를 보고할 수 있도록 설계되었습니다. 이 도구는 HuggingFace와 vLLM 모델을 포함한 다양한 백엔드를 지원합니다.
cloudflare-cron-triggers
테스팅이 스킬은 cron 표현식을 사용하여 Worker를 스케줄링하기 위한 Cloudflare Cron Triggers 구현에 관한 포괄적인 지식을 제공합니다. 주기적 작업, 유지보수 작업, 자동화된 워크플로우 설정 방법을 다루며, 잘못된 cron 표현식이나 시간대 문제 같은 일반적인 이슈들을 해결하는 방법을 포함합니다. 개발자들은 이를 통해 스케줄된 핸들러 구성, cron 트리거 테스트, Workflows 및 Green Compute와의 연동 작업을 수행할 수 있습니다.
webapp-testing
테스팅이 Claude Skill은 Python 스크립트를 통해 로컬 웹 애플리케이션을 테스트하기 위한 Playwright 기반 툴킷을 제공합니다. 프론트엔드 검증, UI 디버깅, 스크린샷 캡처, 로그 확인 기능을 지원하며 서버 라이프사이클을 관리합니다. 브라우저 자동화 작업에 사용하되 컨텍스트 오염을 방지하기 위해 소스 코드를 읽지 않고 스크립트를 직접 실행하세요.
finishing-a-development-branch
테스팅이 스킬은 테스트 통과를 확인한 후 체계적인 통합 옵션을 제시하여 개발자가 완성된 작업을 마무리하도록 돕습니다. 구현이 완료된 후 머지, PR 생성, 브랜치 정리와 같은 워크플로우를 안내합니다. 코드가 준비되고 테스트가 완료되었을 때 개발 프로세스를 체계적으로 마무리하기 위해 사용하세요.
