CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

A well-structured, largely actionable instruction skill: the eight-step check workflow has explicit validation checkpoints, fallback paths, and a pre-handoff quality bar, and the one script invocation is concretely specified. Its main weaknesses are redundant repetition of the boundary/sibling-routing statements and total dependence on external bundle files that are not present alongside this SKILL.md.

Suggestions

State the check-only boundary and sibling routing (landing-optimizer, ad-account-auditor) once — in the intro or Next Best Skill — instead of repeating it in the intro, the post-Instructions paragraph, Reference Materials, and Next Best Skill.

Drop the duplicate five-check enumeration (intro vs. Skill Contract 'Expected output') and keep a single list, letting the numbered Instructions carry the detail.

Either inline a minimal punch-list/handoff output template or ship the referenced files (skill-contract.md, CONNECTORS.md, scripts/connectors/README.md) inside the skill bundle so the ../../../ links resolve on install.

DimensionReasoningScore

Conciseness

The body is domain-dense and assumes expertise, but the same information is repeated several times: the five checks are listed in the intro and again in "Expected output" before being enumerated in Instructions, and the boundary/routing disclaimer ("does not rewrite ... landing-optimizer", "RQS ... belong to ad-account-auditor") appears in the intro, the post-Instructions paragraph, Reference Materials, and Next Best Skill. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

Guidance is largely executable: a copy-paste-ready command ("python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/connectors/firecrawl.py\" scrape <landing-url> --mobile"), explicit decision criteria ("Mark Fix on any promise the page does not honor ... Partial on a softened or reworded match"), a concrete output path format, and Measured/Estimated labeling rules. It falls short of 5 only because the punch-list/handoff output shape is delegated entirely to an external skill-contract.md rather than shown or exemplified inline.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints: a NEEDS_INPUT stop path ("If neither the ad copy nor the page copy is available, you cannot check continuity"), a no-fabrication fallback ("Never invent a speed number ... mark it Estimated or ask for the ~~page speed export"), and an explicit pre-handoff quality-bar checklist with a fix-or-report loop ("If any item fails, fix it or report it in the handoff — do not ship silently"). This matches the anchor 'Clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes'; there are no destructive/batch operations that would require additional validation.

5 / 5

Progressive Disclosure

The body is well-sectioned (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with clearly signaled, descriptive references such as "[CONNECTORS.md](../../../CONNECTORS.md) — the keyless ~~page speed ... recipes". It does not reach 5 because every referenced file (skill-contract.md, roas-benchmark.md, scripts/connectors/README.md) lives outside this skill bundle via deep ../../../ paths, and no references/, scripts/, or assets/ files ship with the skill, so the navigation cannot be verified and the links would break in a standalone install.

4 / 5

Total

16

/

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.

This is an exemplary description: it states concrete capabilities, embeds verbatim user-facing trigger phrases, explicitly covers both what and when, and disambiguates against neighboring skills with named redirects. The trailing CJK summary line duplicates the frontmatter summary but does not meaningfully harm any dimension.

DimensionReasoningScore

Specificity

The description lists multiple concrete, distinct capabilities: "message-match gaps, above-the-fold check, page-speed read, form-friction count, mobile-render flags — as a pass/fix punch list" — comprehensive coverage of the skill's actions within its niche. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage', not 4, because no meaningful capability is left out.

5 / 5

Completeness

Both halves are explicit: what it does ("produces an ad↔page continuity report ... as a pass/fix punch list") and when to use it ("Use when the user asks to ..." with three concrete trigger phrases). This is a direct match for the anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases'; the level-4 anchor's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

It embeds verbatim natural trigger phrases users would actually say: "pre-launch check the landing page", "run a Quality-Score preflight", "verify ad-to-page message match before launch", plus synonyms (preflight, launch, landing page, message match). This is comprehensive natural-term coverage, exceeding the level-4 anchor where 'a few natural terms are missing'.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche and adds explicit negative boundaries: "Not for redesigning or rewriting the page — use landing-optimizer; not for scoring the account or the RQS — use ad-account-auditor." Distinct triggers plus disambiguating redirects give minimal conflict risk, matching the anchor 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

20

/

20

Passed

Validation

75%

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

CriteriaDescriptionResult

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

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.