Skip to content

LeoYeAI/agent-master-skills / skills/apple-search-ads

Apple Search Ads

Verified

Create, optimize, and scale Apple Search Ads campaigns with API automation, attribution integration, and bid strategy recommendations.

FileKindSize
SKILL.mdskill md18.7 KB
_meta.jsonconfig289 B
api-reference.mdmarkdown7.8 KB
ios-integration.mdmarkdown11.0 KB
memory-template.mdmarkdown3.1 KB
scripts.mdmarkdown16.0 KB
setup.mdmarkdown1.5 KB
strategy.mdmarkdown8.7 KB
# Setup — Apple Search Ads

Read this when `~/apple-search-ads/` doesn't exist. Guide the user through setup.

## Your Attitude

You're helping someone grow their iOS app with paid acquisition. Be strategic, data-driven, and focused on ROI.

## Priority Order

### 1. Understand Their Situation

Ask open questions about their app and goals:

**For new advertisers:**
- "What's your app? What category?"
- "What's your budget to start? Daily or monthly?"
- "Do you have any idea what a user is worth to you (LTV)?"
- "Is your App Store listing optimized?"

**For existing advertisers:**
- "How are your current campaigns performing?"
- "What's your CPA target vs actual?"
- "Any keywords that are working well?"
- "Are you tracking attribution in your app?"

### 2. Technical Setup (if they want API access)

If they want to use the API or scripts:
- Walk them through OAuth credentials setup at https://app.searchads.apple.com/cm/app/settings/apicertificates
- Help them set environment variables (ASA_CLIENT_ID, ASA_TEAM_ID, etc.)
- Set up reporting automation

If they just want strategy:
- Skip API setup entirely
- Focus on structure, keywords, and optimization

## What Gets Saved

In `~/apple-search-ads/memory.md`:
- Their apps (adam IDs)
- Target CPA/ROAS
- Current campaign structure
- What's working, what's not
- Preferred reporting cadence

## When "Done"

Once you know their app(s), goals, and whether they want API access or just strategy, you're ready to help. Everything else builds over time through optimization cycles.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall