paid-ads
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,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.
78
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/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 clear 'when to use' guidance. The main weakness is that the capability descriptions ('campaign strategy, ad creation, audience targeting, and optimization') are somewhat high-level and could be more specific about concrete actions. The description effectively distinguishes itself from adjacent marketing skills through platform-specific and metric-specific terminology.
Suggestions
Replace the high-level capability list with more specific concrete actions, e.g., 'write ad copy and headlines, define audience segments, set bidding strategies, analyze campaign metrics, create A/B test variants, and recommend budget allocation.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (paid advertising) and some actions ('campaign strategy, ad creation, audience targeting, and optimization'), but these are fairly high-level categories rather than multiple specific concrete actions like 'write ad copy, set up A/B tests, calculate bid strategies, analyze campaign performance.' | 2 / 3 |
Completeness | Clearly answers both 'what' (campaign strategy, ad creation, audience targeting, optimization across multiple platforms) and 'when' with explicit trigger guidance ('When the user wants help with paid advertising campaigns...' and 'Also use when the user mentions...' with a comprehensive list of trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'Google Ads,' 'Meta,' 'Facebook/Instagram,' 'LinkedIn,' 'Twitter/X,' 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting.' These are all terms users would naturally use when seeking help with paid advertising. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around paid advertising specifically, with platform-specific mentions (Google Ads, Meta, LinkedIn, Twitter/X) and domain-specific acronyms (PPC, ROAS, CPA) that are unlikely to conflict with organic marketing, SEO, or general content creation skills. | 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 comprehensive paid advertising reference that excels at progressive disclosure and organization, with clear references to detailed sub-documents. However, it's overly verbose for a skill file—much of the content reads as a marketing textbook rather than actionable instructions for Claude. The lack of concrete, executable examples (API calls, specific platform configurations, script snippets) and explicit workflow feedback loops limits its actionability and workflow clarity.
Suggestions
Trim strategic advice Claude already knows (e.g., PAS/BAB framework definitions, basic platform descriptions) and focus on project-specific decision trees and concrete implementation steps.
Add explicit workflow sequences with validation checkpoints, e.g., 'After launching: wait 72 hours → check if 50+ conversions reached → if yes, switch to automated bidding → if no, diagnose using the optimization levers below.'
Include more concrete, executable examples such as UTM parameter templates, specific API/platform UI navigation steps, or sample campaign configuration JSON/CSV that could be directly used.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) and includes some information Claude already knows (e.g., what PAS and BAB frameworks are, basic ad platform descriptions). Tables like the platform selection guide and retargeting windows add value but the overall content could be tightened significantly. The 'Before Starting' context-gathering section is useful but verbose. | 2 / 3 |
Actionability | The skill provides structured frameworks, naming conventions, and checklists which are somewhat actionable, but lacks executable code/commands. Most guidance is strategic advice and conceptual frameworks rather than concrete, copy-paste-ready implementations. The optimization levers are helpful but still fairly general (e.g., 'tighten audience targeting'). | 2 / 3 |
Workflow Clarity | There's a reasonable progression from context gathering → platform selection → campaign structure → optimization → reporting, and the pre-launch checklist provides validation. However, the overall workflow is implicit rather than explicitly sequenced, and there are no feedback loops for campaign iteration (e.g., launch → monitor → diagnose → fix → re-evaluate cycle with specific checkpoints). | 2 / 3 |
Progressive Disclosure | The skill effectively uses one-level-deep references to separate files for detailed content (ad-copy-templates.md, audience-targeting.md, platform-setup-checklists.md, tool integration guides). The main file serves as a clear overview with well-signaled pointers to deeper material, and the related skills section provides good cross-navigation. | 3 / 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 | |
- Repository
- freekmurze/dotfiles
- Commit
05d40bb
- Reviewed
Table of Contents
Is this your skill?
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.