Google Ads deep analysis covering Search, Performance Max, AI Max, Display, YouTube, and Demand Gen campaigns. Evaluates 80 checks across conversion tracking, wasted spend, account structure, keywords, ads, and settings. Includes AI Max (search-term-matching, AI Brief, text customization, FUE, brand exclusions) and Smart Bidding signals. Use when user says Google Ads, Google PPC, search ads, PMax, Performance Max, AI Max, AI Brief, broad match audit, Quality Score check, search terms audit, Smart Bidding, or Google campaign.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a specific domain (Google Ads analysis), lists concrete capabilities (80 checks across named categories), and provides an explicit 'Use when' clause with comprehensive trigger terms. The description is well-structured, uses third person voice, and covers both common and specialized terminology that users would naturally employ.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and domains: evaluates 80 checks across conversion tracking, wasted spend, account structure, keywords, ads, and settings. Also specifies AI Max sub-features like search-term-matching, AI Brief, text customization, FUE, and brand exclusions. | 3 / 3 |
Completeness | Clearly answers both 'what' (deep analysis covering multiple campaign types, evaluates 80 checks across specific areas) and 'when' (explicit 'Use when user says...' clause with a comprehensive list of trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Google Ads', 'Google PPC', 'search ads', 'PMax', 'Performance Max', 'AI Max', 'AI Brief', 'broad match audit', 'Quality Score check', 'search terms audit', 'Smart Bidding', 'Google campaign'. These are terms real users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Google Ads analysis with very specific campaign types (PMax, AI Max, Demand Gen) and audit areas. Unlikely to conflict with other skills given the specificity of the domain and trigger terms. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable Google Ads audit skill with excellent domain-specific guidance, concrete thresholds, and clear workflows with validation checkpoints. Its main weakness is length — at 250+ lines with the AI Max and DSA migration sections inline, it pushes the boundaries of what should live in a single SKILL.md versus being split into referenced files. The content quality is high throughout, with particularly strong negative keyword rules and the DSA migration pre-flight checklist.
Suggestions
Move the AI Max for Search section (including the DSA Migration Pre-Flight Checklist) into a separate reference file like ads/references/ai-max-search.md and reference it from the main skill to improve progressive disclosure and reduce token load.
Move the Demand Gen and PMax Deep Dive sections into their own reference files (ads/references/pmax-audit.md, ads/references/demand-gen.md) since they are conditional sections that only apply when those campaign types exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~250+ lines) and includes some information Claude could infer (e.g., explaining what PMax asset groups are, what RSAs are). However, most content is domain-specific thresholds, rules, and checklists that genuinely add value. The AI Max section and DSA Migration Pre-Flight Checklist are thorough but border on verbose — some items could be condensed. The negative keyword rules section earns its place as critical operational guidance. | 2 / 3 |
Actionability | Highly actionable throughout: specific GAQL field names (campaign.ai_max_setting.enable_ai_max), concrete thresholds in the benchmarks table, exact match type syntax ([keyword] vs "keyword"), deduplication rules with tuple format (ad_group_id + keyword_text + match_type), specific dollar thresholds (>$10 spend AND 0 conversions), and a complete DSA migration checklist with checkboxes. The output format is copy-paste ready with the visual health score template. | 3 / 3 |
Workflow Clarity | The top-level process has clear sequencing with two explicit validation checkpoints (confirm ≥30 days data before proceeding, confirm all 80 checks evaluated before scoring). The DSA Migration Pre-Flight Checklist has a clear risk-staging workflow (LOW → HIGH) with a specific rollback trigger (>25% conversion drop in 7 days). The negative keyword rules include a feedback loop (review existing negatives for over-blocking). The MCP integration has a clear fallback path. | 3 / 3 |
Progressive Disclosure | References to external files are well-signaled (ads/references/google-audit.md, benchmarks.md, scoring-system.md, gaql-notes.md), but no bundle files were provided to verify they exist. The SKILL.md itself is quite long and monolithic — the AI Max section, DSA Migration Checklist, and Demand Gen section could arguably be split into separate reference files. The inline content is well-structured with headers but the sheer volume in a single file works against progressive disclosure principles. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
283d9d4
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.