landing-page-guide-v2

Create distinctive, high-converting landing pages that combine proven conversion elements with exceptional design quality. Build beautiful, memorable landing pages using Next.js 14+ and ShadCN UI that avoid generic AI aesthetics while following the 11 essential elements framework.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/landing-page-guide-v2/SKILL.md

Quality

Content

60%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 content is highly actionable with a clear sequenced workflow and well-signaled reference files, but its ~790-line length, redundancy with the reference files, and restating of generic design/SEO/performance knowledge drag down conciseness.

Suggestions

Move the full element-by-element guide into references/11-essential-elements.md and keep only a one-line summary per element in the body to remove the duplication.

Cut the "Best Practices" and "Common Patterns" sections that restate generic knowledge (color psychology, SEO, Core Web Vitals) Claude already has, retaining only skill-specific guidance.

Interleave validation checkpoints inside the Implementation Workflow (e.g. "verify fonts loaded" after Step 2) instead of only the final checklist.

Dimension	Reasoning	Score
Conciseness	At ~790 lines the body is noticeably verbose: the 11-elements framework is detailed inline AND duplicated in references/11-essential-elements.md, and large tracts restate knowledge Claude already has (color psychology, SEO basics, Core Web Vitals thresholds, semantic HTML, responsive prefixes) with the "Best Practices" and "Common Patterns" sections largely repeating earlier content.	2 / 5
Actionability	Provides mostly executable, copy-paste-ready guidance — ShadCN install commands, globals.css/tailwind.config/metadata code blocks, a Hero CTA Button example, animation keyframes, and reduced-motion CSS — with only minor gaps (some placeholders like 'Your Display Font' and "Custom content" comments).	4 / 5
Workflow Clarity	A clear 9-step Implementation Workflow is sequenced (design-first → design system → metadata → components → animations → responsive → performance → accessibility) with a terminal Validation Checklist, though validation checkpoints are end-of-process rather than interleaved feedback loops.	4 / 5
Progressive Disclosure	Two real, clearly signaled, one-level-deep references ("refer to `references/11-essential-elements.md`" and "refer to `references/component-examples.md`") exist and are well-organized, but the body still inlines substantial detail that overlaps those references, a minor organization gap.	4 / 5
	Total	14 / 20 Passed

Description

53%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 conveys a clear what and a distinctive niche, but lacks an explicit when/trigger clause and only offers one real action verb, leaving trigger guidance and action breadth as the main weaknesses.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating landing pages, marketing pages, or product pages."

Include natural synonyms users say ("marketing pages", "product pages", "promo pages") in the description, not just the body.

Vary the verbs beyond create/build to name concrete actions like "design, scaffold, and ship" to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("landing pages") and concrete tech specifics ("Next.js 14+", "ShadCN UI", "11 essential elements framework", "avoid generic AI aesthetics"), but the actual verbs are limited to "Create" and "Build" — essentially one action repeated with rich description rather than multiple distinct operations.	3 / 5
Completeness	Clearly states what the skill does, but contains no "Use when..." clause or equivalent explicit trigger guidance; per the rubric a missing when-clause caps completeness at 3.	3 / 5
Trigger Term Quality	Uses the natural term "landing pages" (repeated), but omits common synonyms users would say such as "marketing pages", "product pages", or "promo pages" that appear only in the body, not the description.	3 / 5
Distinctiveness Conflict Risk	The landing-page niche with a fixed stack (Next.js 14+, ShadCN UI, 11-element framework, anti-generic-AI design focus) is mostly distinct with only minor overlap risk against general web/page-building skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (795 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: bear2u/my-skills
Path: skills/landing-page-guide-v2/SKILL.md
Commit: 8ed5784

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