What problem does it solve?
Running Apple Ads operations through the asc CLI requires choosing between Platform API v1 and the deprecated Campaign Management API v5, handling separate OAuth credentials and ad-account contexts, and avoiding accidental spend from unguarded mutations. This Skill provides the exact command patterns, payload shapes, and safety rules to do that work correctly.
Core Features & Use Cases
- Authentication and account discovery: Configure Apple Ads OAuth profiles, CI environment variables, and ad-account selection via ACL discovery before any operation.
- Read-first campaign management: Query campaigns, ad groups, keywords, reports, recommendations, and assets with JSON-first output and correct pagination.
- Guarded mutations: Create paused test campaigns, apply recommendations, and manage budget orders with explicit confirmation gates and cleanup procedures.
- v5 to v1 migration: Map deprecated Campaign Management API v5 commands to their Platform API v1 equivalents before Apple's January 2027 retirement.
- Use Case: An agent discovers your ad account, queries all campaigns as JSON, drafts a paused test campaign with a timestamped name, and only creates it after you approve the payload.
Quick Start
Ask the agent to discover your Apple Ads ad account and list all campaigns as JSON using the asc ads commands.