When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see page-cro.
81
73%
Does it follow best practices?
Impact
89%
1.17xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/paid-ads/SKILL.mdQuality
Discovery
89%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 with excellent trigger term coverage and completeness. The explicit 'Use when' clause with extensive natural keywords and the cross-references to related skills make it highly functional for skill selection. The main weakness is that the capability actions could be more concrete and specific rather than listing broad categories like 'campaign strategy' and 'optimization.'
Suggestions
Replace high-level action categories with more specific concrete actions, e.g., 'Develops campaign structures, sets bidding strategies, defines audience segments, analyzes performance metrics, recommends budget allocation' instead of 'campaign strategy, audience targeting, bidding, and optimization.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (paid advertising) and some actions like 'campaign strategy, audience targeting, bidding, and optimization,' but these are somewhat high-level categories rather than multiple concrete, specific actions like 'create campaign structures, set bid strategies, define audience segments, analyze ROAS metrics.' | 2 / 3 |
Completeness | Clearly answers both 'what' (campaign strategy, audience targeting, bidding, optimization for paid advertising across multiple platforms) and 'when' (explicit 'Use when' clause with extensive trigger terms). Also includes helpful cross-references to related skills (ad-creative, page-cro). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including platform names (Google Ads, Facebook ads, LinkedIn ads), acronyms (PPC, ROAS, CPA), common phrases ('should I run ads,' 'ad budget,' 'cost per click,' 'paid media,' 'retargeting'), and variations users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly carves out a distinct niche for paid advertising campaigns with explicit boundary-setting via cross-references to ad-creative for bulk creative generation and page-cro for landing pages, reducing overlap risk significantly. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%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 paid advertising skill that covers the full campaign lifecycle with good use of tables and progressive disclosure to external references. Its main weaknesses are verbosity (covering general marketing knowledge Claude already possesses) and a lack of truly executable, concrete guidance—most advice is strategic rather than step-by-step actionable. The workflow could benefit from more explicit sequencing and validation checkpoints between campaign phases.
Suggestions
Trim sections covering general marketing knowledge Claude already knows (PAS/BAB frameworks, basic creative best practices, video ad structure) to brief references or remove entirely, focusing token budget on novel, project-specific guidance.
Add more concrete, executable examples—e.g., specific Google Ads API calls, exact Meta Ads Manager steps, or sample campaign configurations with real settings rather than conceptual descriptions.
Add explicit validation checkpoints to the workflow, such as 'Verify conversion tracking fires correctly before increasing budget' and 'Confirm CPA is within target for 7 days before scaling,' with clear feedback loops for when metrics don't meet thresholds.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some content Claude already knows (ad copy frameworks like PAS/BAB are well-known marketing concepts, basic definitions of retargeting). The tables and structure are efficient, but the overall length (~300 lines) could be tightened—several sections like 'Common Mistakes to Avoid' and 'Creative Best Practices' cover general marketing knowledge rather than novel, Claude-specific instructions. | 2 / 3 |
Actionability | The skill provides structured frameworks, naming conventions, and checklists which are useful, but lacks executable code/commands for actual platform implementation. Guidance is mostly strategic and conceptual (e.g., 'tighten audience targeting,' 'test new creative angles') rather than concrete step-by-step instructions with specific platform actions. The pre-launch checklist is actionable but most optimization advice is directional rather than executable. | 2 / 3 |
Workflow Clarity | There's a logical progression from context gathering → platform selection → campaign structure → optimization → reporting, and the pre-launch checklist provides validation. However, the overall workflow lacks explicit sequencing with numbered steps and validation checkpoints between phases. The budget scaling section mentions waiting 3-5 days but there's no feedback loop for verifying results before proceeding. | 2 / 3 |
Progressive Disclosure | The skill effectively uses progressive disclosure with clear references to separate files: ad-copy-templates.md, audience-targeting.md, platform-setup-checklists.md, and tool integration guides. References are one level deep, well-signaled with bold labels, and the main file serves as a comprehensive overview without burying essential content in external files. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
2c7c108
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.