Full multi-platform paid advertising audit with parallel subagent delegation. Analyzes Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads, Microsoft Ads, and Apple Ads accounts via 6 parallel audit agents. Amazon Ads, cross-platform attribution, and server-side tracking are covered by their standalone sub-skills (ads-amazon, ads-attribution, ads-server-side-tracking) — Wave 3 will add their paired agents so they can dispatch in parallel here. Generates health score per platform and aggregate score (0-100). Use when user says audit, full ad check, analyze my ads, account health check, paid media audit, paid advertising audit, ad spend audit, advertising audit, or PPC audit.
67
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 a strong skill description that excels across all dimensions. It clearly specifies what the skill does (multi-platform ad audits with parallel agents, health scoring), names the exact platforms covered, explicitly delineates boundaries with related sub-skills, and provides a comprehensive list of natural trigger terms. The only minor weakness is the inclusion of implementation details about Wave 3 future plans, which adds noise without aiding skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: analyzes 6 named ad platforms via parallel audit agents, generates health scores per platform and aggregate scores (0-100), and references specific sub-skills for additional capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (multi-platform paid advertising audit with parallel subagent delegation, health scores) and 'when' (explicit 'Use when user says...' clause with extensive trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'audit', 'full ad check', 'analyze my ads', 'account health check', 'paid media audit', 'paid advertising audit', 'ad spend audit', 'advertising audit', 'PPC audit'. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — focuses on full multi-platform paid advertising audits with parallel execution, clearly differentiates itself from standalone sub-skills (ads-amazon, ads-attribution, ads-server-side-tracking), and the trigger terms are specific to advertising audits rather than generic analysis. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured orchestration skill with clear workflow sequencing and validation checkpoints, making it effective as a coordination document for multi-platform ad audits. Its main weaknesses are moderate verbosity in the report structure section (which reads more like a template than actionable instructions) and a lack of concrete executable examples for subagent delegation or scoring calculations. The skill would benefit from trimming the report template sections and adding concrete invocation patterns.
Suggestions
Add concrete subagent delegation syntax or invocation examples showing exactly how to dispatch and collect results from audit-google, audit-meta, etc.
Move the detailed Report Structure section (Executive Summary, Per-Platform Sections, Cross-Platform Analysis, Strategic Recommendations) to a separate reference file like ads/references/report-template.md to reduce inline verbosity
Replace the Quick Wins pseudocode with an actual executable scoring snippet or at minimum specify the exact severity_multiplier values and estimated_impact calculation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary detail that Claude could infer, such as the full report structure section which is essentially a template outline, and the thinking framework preamble. The scoring weights table and priority definitions are useful reference material but the report structure section is verbose. | 2 / 3 |
Actionability | The skill provides a clear process with named subagents and specific check counts, scoring formulas, and output file names. However, it lacks executable code or commands — there are no actual API calls, script invocations, or concrete delegation syntax. The subagent references (audit-google, audit-meta, etc.) are named but not shown how to invoke. The Quick Wins criteria pseudocode is illustrative but not executable. | 2 / 3 |
Workflow Clarity | The process is clearly sequenced with numbered steps, includes two explicit validation checkpoints (step 2: confirm data availability before proceeding; step 6: verify subagent scores before aggregating), and has a logical flow from collection through delegation, scoring, and reporting. The data collection section provides fallback paths (screenshots/manual entry if no exports). | 3 / 3 |
Progressive Disclosure | The skill references external files (ads/references/thinking-framework.md, ads/references/scoring-system.md) and subagent skills, which is good progressive disclosure. However, no bundle files were provided to verify these references exist, and the report structure and cross-platform analysis sections are quite detailed inline content that could potentially be split into reference files. The balance between overview and inline detail leans toward too much inline. | 2 / 3 |
Total | 9 / 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.