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
Quality
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 completeness. It clearly defines when to use the skill with explicit trigger guidance and platform-specific terms. The main weakness is that the capability descriptions are somewhat high-level categories rather than granular concrete actions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (paid advertising) and lists some actions ('campaign strategy, ad creation, audience targeting, and optimization'), but these are somewhat high-level categories rather than multiple specific concrete actions like 'write ad headlines, set up conversion tracking, analyze campaign metrics.' | 2 / 3 |
Completeness | Clearly answers both what ('campaign strategy, ad creation, audience targeting, and optimization' across multiple platforms) AND when ('When the user wants help with paid advertising campaigns' plus explicit 'Also use when the user mentions' clause with specific trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' plus specific platform names (Google Ads, Meta, LinkedIn, Twitter/X). These are terms users naturally use when discussing paid advertising. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on paid advertising with distinct platform names and industry-specific acronyms (ROAS, CPA, PPC). Unlikely to conflict with organic social media, SEO, or general marketing skills due to the explicit paid/advertising focus. | 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 skill with excellent organization and progressive disclosure. However, it leans toward conceptual guidance rather than executable actions, and could be more concise by removing explanations of concepts Claude already knows. The workflow sections would benefit from explicit validation steps and error recovery guidance.
Suggestions
Add executable code examples for common tasks like UTM parameter generation, API calls for campaign creation, or scripts for pulling performance data
Add explicit validation steps to workflows, e.g., 'After setting up conversion tracking, verify by: 1) triggering a test conversion, 2) checking Events Manager shows the event within 20 minutes, 3) if not appearing, check [troubleshooting guide]'
Trim explanatory content that Claude already knows (e.g., remove definitions of lookalikes, retargeting concepts) and trust Claude to understand marketing terminology
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the detailed account organization ASCII diagram and explanations of basic concepts (e.g., what lookalikes are). Some tables could be more compact. | 2 / 3 |
Actionability | Provides good frameworks and checklists but lacks executable code examples for actual API calls or automation. The naming conventions and formulas are helpful but most guidance remains at the conceptual level rather than copy-paste ready commands. | 2 / 3 |
Workflow Clarity | Has clear checklists and sequential guidance (e.g., budget allocation phases, bid strategy progression) but lacks explicit validation checkpoints. The pre-launch checklist is good but doesn't specify how to verify each item or what to do if checks fail. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to detailed materials (ad-copy-templates.md, audience-targeting.md, platform-setup-checklists.md). Navigation is easy with clear section headers and related skills linked at the end. | 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
355d067
- 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.