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

47%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/landing-page-guide-v2/SKILL.md

Quality

Content

62%

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

This skill provides comprehensive, actionable guidance for creating landing pages with excellent workflow structure and executable code examples. However, it severely violates token efficiency by including extensive explanations of concepts Claude already understands (typography basics, CSS fundamentals, why accessibility matters) and repeating key points multiple times. The content would be significantly more effective at 30-40% of its current length.

Suggestions

Remove explanatory content Claude already knows: delete 'Why ShadCN UI?' section, basic CSS/Tailwind explanations, and general web development concepts like 'what is responsive design'

Consolidate repeated content: the 'avoid generic AI aesthetics' guidance appears in multiple sections - state it once definitively

Move the detailed '11 Essential Elements' section, 'Design Aesthetics Guidelines', and 'Common Patterns' to separate reference files, keeping only a brief summary in the main skill

Reduce the validation checklist to essential items only - many items duplicate guidance already provided in the workflow steps

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 500+ lines with extensive explanations Claude already knows (what typography is, how CSS variables work, basic Tailwind concepts). Contains redundant sections like 'Why ShadCN UI?' explaining obvious benefits, and repeats the same concepts multiple times (e.g., 'avoid generic AI aesthetics' appears in at least 4 places).	1 / 3
Actionability	Provides fully executable code examples including CSS setup, TypeScript metadata configuration, component implementations, and bash commands for ShadCN installation. The code is copy-paste ready with specific font names, color variable patterns, and animation keyframes.	3 / 3
Workflow Clarity	Clear 9-step implementation workflow with explicit sequencing (Design First → Setup Design System → Setup Metadata → Create Components → etc.). Includes comprehensive validation checklist with checkboxes covering design quality, 11 essential elements, technical requirements, and final polish.	3 / 3
Progressive Disclosure	References external files appropriately (references/11-essential-elements.md, references/component-examples.md) with clear signaling, but the main SKILL.md contains far too much inline content that should be split out. The 11 elements framework, design aesthetics guidelines, and common patterns sections could each be separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

32%

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 identifies a clear domain (landing pages) and specifies the tech stack, but lacks explicit trigger guidance ('Use when...') which is critical for skill selection. It uses appropriate third-person voice but relies on marketing language ('high-converting', 'exceptional design quality') rather than concrete actions, and the '11 essential elements framework' reference is vague without enumeration.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'landing page', 'marketing page', 'conversion page', 'lead generation page', or 'sales page'

Replace vague phrases like 'proven conversion elements' and '11 essential elements framework' with specific actions like 'create hero sections, CTAs, testimonial blocks, pricing tables'

Include common user phrasings and file/project indicators that would trigger this skill, such as 'marketing site', 'product launch page', or 'signup page'

Dimension	Reasoning	Score
Specificity	Names the domain (landing pages) and mentions some technologies (Next.js 14+, ShadCN UI) and references an '11 essential elements framework', but doesn't list specific concrete actions like 'create hero sections', 'implement CTAs', or 'build testimonial blocks'.	2 / 3
Completeness	Describes what it does (create landing pages with specific tech stack) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant terms like 'landing pages', 'Next.js', 'ShadCN UI', and 'high-converting', but misses common variations users might say like 'marketing page', 'sales page', 'conversion page', 'homepage', or 'lead capture'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'landing pages' + 'Next.js 14+' + 'ShadCN UI' provides some distinctiveness, but could overlap with general web development or React component skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 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	10 / 11 Passed

Repository: bear2u/my-skills
Commit: 1be5394

Reviewed: 3 months 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.