ads-landing
Landing page quality assessment for paid advertising campaigns. Evaluates message match, page speed, mobile experience, trust signals, form optimization, and conversion rate potential. Use when user says "landing page", "post-click experience", "landing page audit", "conversion rate", or "landing page optimization".
Install with Tessl CLI
npx tessl i github:AgriciDaniel/claude-ads --skill ads-landing82
Quality
75%
Does it follow best practices?
Impact
91%
1.54xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ads-landing/SKILL.mdDiscovery
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 well-crafted skill description that excels across all dimensions. It provides specific evaluation criteria, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and carves out a distinct niche around paid advertising landing pages.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Evaluates message match, page speed, mobile experience, trust signals, form optimization, and conversion rate potential.' These are distinct, measurable assessment criteria. | 3 / 3 |
Completeness | Clearly answers both what ('Landing page quality assessment for paid advertising campaigns' with specific evaluation criteria) AND when (explicit 'Use when user says...' clause with multiple trigger terms). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'landing page', 'post-click experience', 'landing page audit', 'conversion rate', 'landing page optimization'. Good coverage of common variations and related terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on landing pages specifically for paid advertising campaigns. The combination of 'paid advertising', 'post-click experience', and specific evaluation criteria like 'message match' creates a distinct scope unlikely to conflict with general web or marketing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of landing page quality factors with useful scoring tables and checklists. However, it lacks executable code for automation, includes some explanatory context Claude doesn't need, and could benefit from validation checkpoints in the workflow. The content is well-organized but somewhat verbose for a skill file.
Suggestions
Add executable code snippets for page speed checking (e.g., using Lighthouse CLI or PageSpeed API) and UTM parameter validation
Remove explanatory statements like 'Slow pages kill conversion rates' and 'Mobile experience is critical' - Claude knows this context
Add validation checkpoints to the workflow (e.g., 'Verify benchmarks.md exists before proceeding', 'Confirm all URLs are accessible')
Consider moving the detailed tables (Form Length Impact, Platform Requirements) to a separate reference file to keep SKILL.md leaner
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some explanatory text that Claude would already know (e.g., 'Slow pages kill conversion rates', '75%+ of ad clicks come from mobile'). Tables are well-structured but some sections could be tightened. | 2 / 3 |
Actionability | Provides good checklists and scoring criteria, but lacks executable code examples for checking page speed, validating UTM parameters, or generating the output report. The guidance is descriptive rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The 6-step process at the top provides a clear sequence, but lacks validation checkpoints. No feedback loops for error recovery (e.g., what if benchmarks.md doesn't exist, or if page speed tools fail). The workflow assumes everything works. | 2 / 3 |
Progressive Disclosure | References external files (benchmarks.md, conversion-tracking.md) appropriately, but the main content is quite long (~150 lines) with detailed tables that could be split into reference files. The structure is good but content organization could be improved. | 2 / 3 |
Total | 8 / 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.
- 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.