Name: landing-page-guide-v2
Rating: 54.400000000000006 (1 reviews)
Author: bear2u

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

61%

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 ./.claude/skills/landing-page-guide-v2/SKILL.md

The canonical home for this skill is landing-page-guide-v2 in bear2u/my-skills

Quality

Content

56%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 well-structured with a concrete 9-step workflow, executable code, and a validation checklist, but it is noticeably verbose with significant cross-section repetition and inlines detail that duplicates its own reference files. Trimming redundancy and moving the 11-element deep-dive fully to its reference would improve both conciseness and progressive disclosure.

Suggestions

Deduplicate the font prohibition and "avoid generic AI aesthetics" guidance into a single authoritative section; remove the restatements in Best Practices and Notes.

Move the full element-by-element design guide entirely into references/11-essential-elements.md and keep only a concise summary table in the body.

Consolidate the Best Practices, Common Patterns, and Notes & Philosophy sections, which heavily repeat Design Aesthetics guidance.

Dimension	Reasoning	Score
Conciseness	The ~790-line body noticeably repeats themes: the Inter/Roboto/Arial font prohibition appears ~5 times, the "avoid generic AI aesthetics" message is restated in Overview, AVOID, Notes, and Remember sections, and animation/color guidance recurs across Design Thinking, Design Aesthetics, Step 6, and Best Practices.	2 / 5
Actionability	Provides mostly executable guidance including ShadCN install commands, CSS variable blocks, tailwind.config.ts, Next.js metadata, and TSX component snippets (Hero CTA, Benefits Card, staggered animation), though some guidance is abstract design direction and component detail is offloaded to a reference file.	4 / 5
Workflow Clarity	A clear 9-step Implementation Workflow is sequenced from design thinking through accessibility, backed by a comprehensive final Validation Checklist; it lacks inline "validate then proceed" feedback loops between steps, but the skill is generative rather than destructive/batch so the cap does not apply.	4 / 5
Progressive Disclosure	Two real reference files (11-essential-elements.md, component-examples.md) are clearly signaled and one level deep, but the full 11-element design guide is inlined in the body despite having its own reference file, and lengthy Best Practices/Common Patterns/Notes sections are content that could be split out.	3 / 5
	Total	13 / 20 Passed

Description

66%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 and distinctive, naming a clear tech stack and framework, but it omits an explicit "when to use" trigger clause, which caps its completeness. Trigger term coverage is good but lacks common synonyms.

Suggestions

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

Include natural synonyms users say such as "marketing page", "product page", and "promo site".

Consider mentioning .tsx/Next.js App Router explicitly to strengthen distinctiveness from generic web skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("Create distinctive, high-converting landing pages", "Build... using Next.js 14+ and ShadCN UI", "avoid generic AI aesthetics", "following the 11 essential elements framework") with a named tech stack, though the verbs remain high-level rather than a granular operation list.	4 / 5
Completeness	The "what" is clear and concrete, but there is no explicit "Use when..." trigger clause in the description itself; per the rubric, a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Strong natural keywords ("landing pages", "high-converting", "Next.js", "ShadCN UI") that users would actually say, but common synonyms like "marketing page", "product page", or "promo site" are absent.	4 / 5
Distinctiveness Conflict Risk	The combination of landing pages + Next.js 14+/ShadCN + the 11 essential elements framework is a fairly distinct niche, with only minor overlap risk against a general Next.js/web-design skill.	4 / 5
	Total	15 / 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: .claude/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.