菜单
YouTube Ads analysis across skippable and non-skippable in-stream, bumper, Shorts, Demand Gen, and Connected TV formats: creative quality, targeting, measurement, frequency capping. Use when user says YouTube Ads, video ads, pre-roll, bumper ads, Shorts ads, Demand Gen, VAC, or CTV.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ads-youtube |
| description | YouTube Ads analysis across skippable and non-skippable in-stream, bumper, Shorts, Demand Gen, and Connected TV formats: creative quality, targeting, measurement, frequency capping. Use when user says YouTube Ads, video ads, pre-roll, bumper ads, Shorts ads, Demand Gen, VAC, or CTV. |
| user-invokable | false |
| tested_date | "2026-05-17T00:00:00.000Z" |
| tested_with | claude-code v2.x |
ads/references/google-audit.md for YouTube-relevant checks (incl. G-DG1 through G-DG3, G-CTV1)ads/references/platform-specs.md for video specificationsads/references/benchmarks.md for YouTube benchmarksads/references/scoring-system.md for health score algorithm| Metric | Benchmark | Notes |
|---|---|---|
| View Rate (skippable) | ≥15% | Higher = better hook |
| CPV (skippable) | $0.01-0.10 | Varies by targeting |
| VTR (bumper) | 90%+ | Non-skippable, should be near 100% |
| CPM (non-skip) | $6-15 | Varies by market |
| CTR (Demand Gen) | ≥0.5% | Image+video combined |
| Brand Lift | Measurable | Requires Google Brand Lift Study |
Weighted assessment from ads/references/scoring-system.md:
Category Weights:
Creative Quality: 30% ██████████
Campaign Setup: 25% ████████░░
Audience Targeting: 25% ████████░░
Measurement: 20% ██████░░░░
Grade: A (90-100), B (75-89), C (60-74), D (40-59), F (<40)
High-performing Shorts ad pattern:
| Check | Fix | Time |
|---|---|---|
| YT-05: Demand Gen migration | Upgrade remaining VACs to Demand Gen with video+image | 15 min |
| YT-04: Shorts vertical | Create 9:16 vertical cuts of existing ads | 10 min |
| YT-09: Add image assets | Upload image assets to Demand Gen (20% more conversions) | 10 min |
| YT-12: Frequency monitoring | Set Target Frequency to 4/week for awareness campaigns | 5 min |
YouTube Ads Assessment
Campaign Types: ████████░░ Active formats evaluated
Creative Quality: ██████████ Hook, production, volume
Audience Targeting: ███████░░░ Strategy and coverage
Measurement: █████░░░░░ Attribution and tracking
YOUTUBE-ADS-REPORT.md: Campaign-by-campaign analysisBuild, secure, and package Electron desktop apps — main/preload/renderer split, contextIsolation-safe typed IPC over a preload bridge, BrowserWindow + application menu + app naming, a strict CSP, and distribution (electron-builder/Forge, productName, code signing). Use when building an Electron app, wiring IPC, hardening security, fixing the app/menu name, or packaging. Do NOT use for web-only React UI (use cleanui) or Expo/React Native.
Write an engineering tech spec (design doc / RFC) that turns an approved PRD into an implementable design. Use when turning a PRD or epic into a design doc, writing an RFC, or answering 'how should we build this'. Do NOT use for product requirements (prd-development) or recording a single architectural decision (adr).
Run a right-sized threat-modeling pass (trust boundaries, STRIDE, abuse cases) on a forming design so security decisions land before Sign-Off 2. Use when a design adds attack surface — a new endpoint, data class, integration, or authz change. Do NOT use for code-diff security review (/security-review), pentests, or compliance audits.
Build and maintain a durable automated E2E suite — Playwright for web, Maestro for Expo/React Native: stable selectors, owned test data, CI gating, and a flake policy with teeth. Use when automating the E2E journeys a test plan defines or fixing a slow/flaky suite. Do NOT use for deciding what to test (test-strategy) or unit tests (tdd).
Run a go/no-go release review producing a scored readiness report — rollout plan, observability, rollback, comms verified before shipping. Use when preparing a release/launch, a go-live checklist, a rollout plan, or 'are we ready to ship'. Do NOT use for store-submission mechanics (expo-deployment) or writing the test plan itself (test-strategy).
Define production health before launch: user-centric SLIs, SLO targets with error budgets, burn-rate alerts that page on user pain (not CPU), and a runbook per pageable alert. Use when designing SLOs, alerts, error budgets, or runbooks. Do NOT use for the go/no-go review (release-readiness) or post-incident analysis (incident-postmortem).