CtrlK
BlogDocsLog inGet started
Tessl Logo

landing-page

Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls.

60

Quality

69%

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 ./agent-skills/web-design/landing-page/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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-structured, token-efficient playbook with clear sequencing and a defined output format. Its weakest dimension is actionability: guidance is largely directional and template-based rather than fully executable with worked examples.

Suggestions

Add one fully worked end-to-end example (hero copy + 3 benefits + how-it-works + FAQ) so Claude can pattern-match a complete landing page rather than assemble from fragments.

Tighten repeated 'Best when:' labels in the Layout types section into a compact table to recover a few tokens.

Include a short self-check after the output format (e.g. 'Verify: one primary CTA above the fold, proof next to the claim it supports') to add an explicit validation checkpoint.

DimensionReasoningScore

Conciseness

The body is dense and efficiently organized into scannable checklists and templates with minimal padding, though a few short labels (e.g. 'Best when:') repeat and could be tightened.

4 / 5

Actionability

Provides concrete templates (headline formulas, CTA rules, output format) and specific examples, but much guidance is directional rather than executable — there is no code, no copy-the-pattern runnable artifact, and several sections list principles without a worked end-to-end example.

3 / 5

Workflow Clarity

Clear sequenced workflow ('Before you design/write' → 'Core structure' → 'Section-by-section workflow' → 'Output format') with a numbered build order; it lacks explicit validation checkpoints, but the task is generative rather than destructive so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

Well-organized overview with clearly signaled sections and a defined output format; for a self-contained single-file skill under 50 lines-equivalent of substantive guidance, the structure is appropriately navigable with no nested references.

5 / 5

Total

16

/

20

Passed

Description

67%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 specific, complete, and clearly distinct, explicitly pairing 'what' and 'when' clauses. Its main weakness is trigger-term breadth: it misses several natural synonyms a user might actually say.

Suggestions

Add natural trigger synonyms users say, e.g. 'sales page', 'squeeze page', 'lead capture page', or 'offer page', to broaden keyword coverage.

Specify the conversion-oriented trigger more concretely, e.g. 'Use when the user wants to improve conversion rates on a single-offer page'.

Consider including a quick example phrase ('make me a landing page', 'rewrite my SaaS homepage into a landing page') to anchor natural phrasing.

DimensionReasoningScore

Specificity

Lists several concrete actions (structure, layout patterns, conversion strategies, copywriting, SEO/AEO, common pitfalls), giving good coverage of the skill's scope with only minor gaps.

4 / 5

Completeness

Has both a clear 'what' (designing/rewriting a high-converting landing page covering structure, copywriting, SEO/AEO) and an explicit 'when' ('Use when designing or rewriting...'), though the trigger phrasing could be more specific.

4 / 5

Trigger Term Quality

Includes some natural terms ('landing page', 'SaaS/apps/services', 'high-converting'), but lacks common user phrases like 'sales page', 'squeeze page', or 'lead capture' that a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

The 'landing page (single-offer page)' niche is mostly distinct from homepage or general web-design skills, with only minor overlap risk against broader web-design skills.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
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.