메뉴
Microsoft/Bing Ads deep analysis: search, Performance Max, Audience Network, Copilot integration, Google Ads import validation, LinkedIn audience targeting, cost advantage. Use when user says Microsoft Ads, Bing Ads, Bing PPC, Copilot ads, or Google import audit.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | ads-microsoft |
| description | Microsoft/Bing Ads deep analysis: search, Performance Max, Audience Network, Copilot integration, Google Ads import validation, LinkedIn audience targeting, cost advantage. Use when user says Microsoft Ads, Bing Ads, Bing PPC, Copilot ads, or Google import audit. |
| user-invokable | false |
| tested_date | "2026-05-17T00:00:00.000Z" |
| tested_with | claude-code v2.x |
ads/references/microsoft-audit.md for full 24-check auditads/references/benchmarks.md for Microsoft-specific benchmarksads/references/scoring-system.md for weighted scoringMost Microsoft Ads accounts start as Google Ads imports. Critical validation:
Microsoft's AI assistant creates unique ad opportunities:
These features are exclusive to Microsoft Ads; evaluate adoption:
| Feature | Description | Priority |
|---|---|---|
| CTV Ads | Netflix, Max, Hulu, Roku, discovery+. 30-second non-skippable. | Medium |
| Multimedia Ads | Image-rich search ads with visual elements | Medium |
| Action Extension | CTA button directly in search ad | Medium |
| Filter Link Extension | Filterable category links in ad | Low |
| LinkedIn Profile Targeting | Target by company, industry, job function | High (B2B) |
| Copilot Chat Placement | Ads within Copilot conversations | High |
| Auto-generated RSA | Enabled by default Jan 2026, 5% CTR increase | Medium |
| 9:16 Vertical Video | Vertical video ads (Apr 2025), 90-second max duration | Medium |
Microsoft Ads reach a distinct audience:
Ad copy optimization for this audience:
| Metric | Pass | Warning | Fail |
|---|---|---|---|
| CTR (Search) | ≥2.83% | 1.5-2.83% | <1.5% |
| CPC (Search) | ≤$1.55 | $1.55-2.50 | >$2.50 |
| CPC vs Google | 20-40% lower | 10-20% lower | Same or higher |
| CVR vs Google | Within 20% | 20-50% lower | >50% lower |
| Impression share (brand) | ≥80% | 60-80% | <60% |
Microsoft Ads Health Score: XX/100 (Grade: X)
Technical Setup: XX/100 ████████░░ (25%)
Syndication: XX/100 ██████████ (20%)
Structure: XX/100 ███████░░░ (20%)
Creative: XX/100 █████░░░░░ (20%)
Settings: XX/100 ████████░░ (15%)
MICROSOFT-ADS-REPORT.md: Full 24-check findings with pass/warning/failBuild, 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).