ads-landing

Audit paid-ad landing pages for message match, mobile experience, performance, accessibility, trust, forms, consent, tracking, security, and conversion friction. Use for landing-page audit, post-click experience, LP audit, conversion-rate optimization, form optimization, ad-to-page message match, redirects, blocked navigation, or requests involving private, loopback, link-local, or metadata IP destinations.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, lean instruction body that sequences the audit and embeds a strong blocked-navigation validation contract. The main gap is that shared tooling (fetcher, common schema) is named but not shown how to invoke.

Suggestions

Add a one-line example of how to invoke the guarded HTTP fetcher and what the 'common schema' return shape looks like, so the workflow is fully executable rather than referencing external tools by name.

Move or duplicate the redirect-validation checkpoint inline within the six-step sequence so validation is visible at each step rather than only in the separate contract section.

Trim the slight restatement of DNS-check insufficiency between step 1 and the blocked-navigation contract to save tokens.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no explanation of what a landing page or message match is), but the DNS-insufficiency point is restated across step 1 and the blocked-navigation contract and could be tightened slightly.	4 / 5
Actionability	Concrete guidance on what to capture and which evidence fields to record (requested URL, redirect hop, resolved destination class, guard decision, reason, timestamp, request_sent: false), but invocation of the 'guarded HTTP fetcher' and 'common schema' is referenced rather than shown.	4 / 5
Workflow Clarity	A clear six-step sequence plus an explicit validation checkpoint ('Validate the initial URL and every redirect before sending the next request') and a needs_input feedback path, but the checkpoints live mainly in the contract section rather than inline with each step.	4 / 5
Progressive Disclosure	A short (under-50-line) single-purpose skill with a titled overview, numbered steps, a safety paragraph, and one well-signaled subsection — appropriately organized with no external references needed.	5 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does and when to use it, with comprehensive natural trigger terms and a well-defined niche. It avoids fluff and over-claims.

Dimension	Reasoning	Score
Specificity	Lists many concrete audit dimensions — 'message match, mobile experience, performance, accessibility, trust, forms, consent, tracking, security, and conversion friction' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' ('Audit paid-ad landing pages for...') and 'when' ('Use for landing-page audit, post-click experience...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases with synonyms — 'landing-page audit', 'LP audit', 'post-click experience', 'conversion-rate optimization', 'form optimization', 'ad-to-page message match', 'redirects', 'blocked navigation' — closely matching what a user would say.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche — paid-ad landing-page / post-click audits — with distinct triggers and minimal overlap risk with general skills; the IP-destination boundary language further sharpens it.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: AgriciDaniel/claude-ads
Path: skills/ads-landing/SKILL.md
Commit: ac21644

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.