CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

landing-page-conversion-audit

Identify conversion blockers and ad-budget leaks with a severity-ranked landing page audit. Use when: Identify high-risk conversion leaks before launching ad campaigns; Audit landing page HTML for CTA dominance and competing actions; Detect distracting elements and outbound links in the hero section.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-web-audits/skills/landing-page-conversion-audit/SKILL.md

The canonical home for this skill is landing-page-conversion-audit in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

28%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 reads as a marketplace sales page rather than an operational skill: it promotes the audit's value and answers purchase/install questions, but never tells Claude how to actually perform the audit — the "codified checklist engine" is referenced yet not included (scripts and templates are explicitly noted as absent). It also claims "seven critical conversion families" while listing only six.

Suggestions

Replace the FAQ and 'Why use this skill' marketing sections with the actual audit procedure: per-family concrete checks (CTA dominance rules, form-field threshold of 5+, 800px value-prop viewport rule, tap-target and page-weight limits) and explicit CRITICAL/HIGH/MEDIUM/LOW severity definitions.

Add a sequenced workflow — obtain HTML (URL or file), evaluate each conversion family in order, assign severities, emit the ranked report — anchored on the existing example output as the report template.

Delete the purchase-oriented questions, creator/catalog links, and the 'When to use' section that duplicates the frontmatter description; also fix the 'seven critical conversion families' claim to match the six families actually listed.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections that add no executable value: the six-question marketing FAQ ("What is included with my purchase of this skill?", "Do I need technical expertise to install or run the audit?"), the promotional "Why use this skill" section, and a "When to use" section that duplicates the frontmatter description. Not 1 because the module list and example output do carry real information.

2 / 5

Actionability

Minimal concrete guidance: the body describes what is checked ("Checks for primary CTA dominance and competing call-to-actions", "Analyzes form field counts") and shows one sample output, but provides no actual checklist, selector patterns, thresholds, or severity definitions — and states "Scripts, extension source, and templates from the original package are not in this folder". Anchor 2 fits: high-level hints with the specific steps to execute missing.

2 / 5

Workflow Clarity

No sequenced steps exist: the audit procedure (how to obtain/parse the HTML, in what order to evaluate the families, how to assign CRITICAL-to-LOW severity, how to format the report) is entirely unspecified, leaving only a rough implied input-to-report flow from the Request/Result example. Not 1 because the example does imply a coherent input → audit → ranked-report flow; not 3 because no real step list or checkpoints are present.

2 / 5

Progressive Disclosure

The body has clear section headers ("What it does", "When to use", "Known limitations", "Example") and no broken or nested references since no bundle files exist. However, content that should live in separate reference files — the per-family audit checklists and severity rubric — is simply absent rather than linked, and the marketing FAQ is inlined where a lean overview belongs.

3 / 5

Total

9

/

20

Passed

Description

83%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 description: third-person, concise, with an explicit "Use when:" clause carrying three concrete trigger scenarios and domain-specific natural keywords. The only weakness is incomplete capability coverage and a few missing synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Identify conversion blockers and ad-budget leaks", "Audit landing page HTML for CTA dominance and competing actions", "Detect distracting elements and outbound links in the hero section" — with only minor coverage gaps (trust signals, friction, and mobile checks are unmentioned). Not 5 because the capability list is not comprehensive; not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: the "what" ("severity-ranked landing page audit" that identifies "conversion blockers and ad-budget leaks") and the "when" via a literal "Use when:" clause with three concrete trigger scenarios. This closely matches the anchor-5 example structure; anchor 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "conversion leaks", "landing page", "CTA", "ad campaigns", "hero section", "outbound links" — terms the target user would plausibly say. Not 5 because common synonyms ("CRO", "conversion rate optimization", "landing page optimization") and file extensions (.html) are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (landing-page CRO auditing) with distinct triggers (CTA dominance, hero-section outbound links) that an SEO or accessibility skill would not claim. Not 5 because generic phrasing like "conversion leaks before launching ad campaigns" leaves minor overlap risk with general site-review/marketing skills.

4 / 5

Total

17

/

20

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

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-web-audits/skills/landing-page-conversion-audit/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.