apple-ads-certification-core
Skill0 starsChanged 5 days agoMITView on GitHub
Core Apple Ads certification guidance for keyword strategy, campaign structure (brand/category/competitor/discovery), Search Match usage, and performance interpretation. Use when planning or reviewing search-results campaign strategy against certification-aligned best practices.
In this repository7 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Keep Search Match focused on Discovery ad groups.
- Distinctive: line 26
Do not claim unsupported Apple Ads API endpoints.
- Distinctive: line 27
Prefer observed certification guidance.
- Distinctive: line 28
Keep recommendations region-sensitive for Search Match and localization constraints.
- Distinctive: line 29
Before running CLI commands or interpreting Insights, read the Platform API agent guidance.
- Very specific: line 32
Read references/certification-findings.md for extracted observed findings, review thresholds, and inferred policy notes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Apple Ads Certification Core
Use when
- A user asks for Apple Ads strategy aligned with certification guidance.
- A user wants campaign/account structure recommendations for search results campaigns.
- A user wants to understand how to use Search Match, exact/broad/negative keywords, and keyword suggestions in a certification-consistent way.
Workflow
- Confirm goal and campaign type (new setup, restructure, or optimization review).
- Use certification-aligned structure:
- Separate Brand, Category, Competitor, and Discovery campaigns.
- Keep Search Match focused on Discovery ad groups.
- Validate keyword/match-type setup against the checklist and default thresholds in
references/certification-findings.md. - Recommend concrete next actions with measurable thresholds:
- Observation only when data volume is below review minimums.
- Bid or budget adjustment only when efficiency is acceptable and volume is proven.
- Restructure when query intent, match-type hygiene, or campaign separation is breaking attribution clarity.
- Clearly label observed guidance vs working-policy inference.
Guardrails
- Do not claim unsupported Apple Ads API endpoints.
- Prefer observed certification guidance; mark inferred automation policy as inferred.
- Keep recommendations region-sensitive for Search Match and localization constraints.
- Before running CLI commands or interpreting Insights, read the Platform API agent guidance. It covers explicit account selection, SOV metric limits, unsupported operations, and write recovery.
References
- Read
references/certification-findings.mdfor extracted observed findings, review thresholds, and inferred policy notes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.