landing-experience-checker

Use when the user asks to "pre-launch check the landing page", "run a Quality-Score preflight", or "verify ad-to-page message match before launch"; produces an ad↔page continuity report — message-match gaps, above-the-fold check, page-speed read, form-friction count, mobile-render flags — as a pass/fix punch list. Not for redesigning or rewriting the page — use landing-optimizer; not for scoring the account or the RQS — use ad-account-auditor. 落地页体验预检/广告落地页一致性检查

Quality

83%

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

73%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.

The body is a well-sequenced, checklist-driven preflight with strong validation gates and clear sibling routing. Its main weakness is conciseness — repeated boundary/routing statements and ROAS-framework filler inflate the token budget without adding actionable value.

Suggestions

State the 'checks only — does not rewrite or score' boundary once (e.g. in the Skill Contract) and reference it rather than restating it in the intro, Instructions close, and Next Best Skill.

Trim framework-narration filler such as 'This works the ROAS O (Offer) lever from the post-click side...' down to the one-phrase role it plays, since the sibling-skill links already convey the rest.

Consolidate the handoff/contract routing rules (hot-cache, open-loops, owner routing) into a single handoff subsection instead of scattering them across Skill Contract, Instructions step 8, and Next Best Skill.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but padded: the 'checks only / does not rewrite' boundary and the routing to landing-optimizer / ad-account-auditor are restated across the intro, Instructions close, and Next Best Skill, and framework filler like 'This works the ROAS O (Offer) lever from the post-click side...' could be trimmed.	3 / 5
Actionability	Provides one copy-paste command ('python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/firecrawl.py" scrape <landing-url> --mobile') and concrete per-check criteria (count required fields, mark Pass/Partial/Fix, label Measured/Estimated), with only minor gaps in executable coverage.	4 / 5
Workflow Clarity	An explicit 8-step numbered sequence is backed by a 'Quality bar before handoff' checklist, a 'Done when' gate, Measured/Estimated labeling discipline, and a re-preflight loop ('return here to re-preflight after the fix') — matching the checklist-with-feedback-loop anchor.	5 / 5
Progressive Disclosure	Clear section structure with one-level-deep, well-signaled references (skill-contract.md, CONNECTORS.md, SECURITY.md, roas-benchmark.md, firecrawl.py); no bundle files ship alongside the skill, and some contract/handoff detail is inlined rather than split out, keeping it just below the score-5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

92%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.

The description is strong across the board: concrete five-check action list, explicit trigger phrases, clear what/when, and explicit de-confliction against sibling skills. The only minor gap is a few everyday synonyms for the trigger phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'message-match gaps, above-the-fold check, page-speed read, form-friction count, mobile-render flags — as a pass/fix punch list' — with comprehensive coverage of the five checks, matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both what ('produces an ad↔page continuity report...pass/fix punch list') and when (concrete 'Use when the user asks to...' trigger phrases), matching the score-5 anchor.	5 / 5
Trigger Term Quality	Includes three natural quoted trigger phrases ('pre-launch check the landing page', 'run a Quality-Score preflight', 'verify ad-to-page message match before launch') a user would say, but common lay variations like 'check my landing page' are absent, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Explicit negative boundary clauses ('Not for redesigning...use landing-optimizer; not for scoring the account or the RQS — use ad-account-auditor') carve a clear niche with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

75%

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 — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 15 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: ad/orchestrate/landing-experience-checker/SKILL.md
Commit: 888dd38

Reviewed: 3 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.