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.

76

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The content is a well-organized, lean, and highly actionable reference for landing page design with clear workflows and a defined output format. The main gap is the absence of explicit validation or feedback checkpoints in its workflows.

Suggestions

Add explicit validation/review checkpoints in the section-by-section workflow (e.g., 'After drafting the hero, confirm the headline states an outcome for the ICP before moving on') to strengthen workflow clarity.

Make the 'Quick questions' gating explicit as a step that must run before generating output, so the workflow is unambiguous rather than implied.

Consider a short self-check before the final CTA step (e.g., verify objection handling and risk reversal are present) to close the implicit feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven with no padding or generic concept explanations; it assumes Claude's competence and every section earns its place, matching the lean-and-efficient anchor.

3 / 3

Actionability

Provides concrete, copy-paste-ready guidance including headline formulas, good/bad CTA examples, specificity examples, and a numbered output format; for an instruction-only skill this is fully actionable.

3 / 3

Workflow Clarity

Sequences are clearly ordered (section-by-section workflow, output format, quick questions) but validation checkpoints and error-recovery feedback loops are only implicit, so it sits at the 'steps listed but checkpoints missing/implicit' anchor rather than 3.

2 / 3

Progressive Disclosure

No bundle files exist and none are referenced; the body is well-organized into clearly headed sections, which per the rubric guidelines can score 3 for skills with no need for external references.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concise, uses third person, and clearly states both what the skill covers and when to use it with natural trigger terms. It is a strong, distinct, well-targeted description.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete capability areas (structure, layout patterns, conversion strategies, copywriting, SEO/AEO, pitfalls) rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicit 'Use when' clause answers when, and the 'Covers...' sentence answers what, matching the anchor for clearly answering both what AND when with explicit triggers.

3 / 3

Trigger Term Quality

Uses natural terms users would say ('landing page', 'high-converting', 'SaaS/apps/services') with good coverage; only minor variations like 'sales page' are absent, keeping it at the top anchor rather than below.

3 / 3

Distinctiveness Conflict Risk

The clear niche of 'high-converting landing page (single-offer page)' with explicit triggers is unlikely to fire for unrelated skills, matching the distinct-niche anchor.

3 / 3

Total

12

/

12

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.