landing-page-guide

Comprehensive guide for creating effective landing pages using Next.js or React. This skill should be used when users request to create landing pages, marketing pages, or product pages that require the 11 essential elements for high-converting landing pages. Specifically designed for Next.js 14+ App Router with ShadCN UI components.

Quality

66%

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/SKILL.md

Quality

Content

63%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 executable guidance and a clear workflow backed by a verification checklist and properly signaled one-level references. Its chief weakness is conciseness: redundant list repetition and generic best-practice padding inflate the token budget without adding skill-specific value.

Suggestions

Remove the duplicate full 11-element listing in the body and keep only a brief pointer to references/11-essential-elements.md, retaining the concise checklist for verification.

Cut the 'Why ShadCN UI?' and 'Best Practices' sections, which restate accessibility/typography/conversion concepts Claude already knows.

Add an explicit feedback loop after the Validation Checklist: 'If any item fails, fix and re-verify before declaring the page complete.'

Dimension	Reasoning	Score
Conciseness	The body restates the 11-element list three times (framework, workflow, checklist) and includes a 'Why ShadCN UI?' plus 'Best Practices' sections that restate concepts Claude already knows, producing noticeable verbosity and redundancy. It is above a 2 because there is no basic-concept tutorial padding, but below a 3 because the duplicated lists and generic content-design tips are unnecessary tokens.	2.5 / 5
Actionability	Provides executable commands ('npx shadcn-ui@latest add button'), a complete TypeScript metadata block, a project structure tree, and a section-to-ShadCN component mapping. It is not a 5 because the actual component implementations live in the reference file rather than inline, leaving a minor gap in the body itself.	4 / 5
Workflow Clarity	A clear 6-step Implementation Workflow with a component build order and a terminal Validation Checklist provides a well-sequenced process with a checkpoint. It is not a 5 because there is no explicit failure feedback loop (e.g., 'if the checklist fails, fix and re-verify') before sign-off.	4 / 5
Progressive Disclosure	The body is a well-organized overview pointing to two real, one-level-deep references ('references/11-essential-elements.md', 'references/component-examples.md'), each described so the model knows when to load them. It is not a 5 because the 11-element list is duplicated inline alongside its dedicated reference, a minor organization gap.	4 / 5
	Total	14.5 / 20 Passed

Description

70%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 clearly communicates both purpose and trigger conditions in third person, with solid keyword coverage and a distinct tech niche. Its main weakness is specificity: it describes the skill as a generic 'comprehensive guide' rather than enumerating concrete capabilities.

Suggestions

Replace the generic 'Comprehensive guide for creating effective landing pages' opener with concrete actions, e.g. 'Generates Next.js 14 App Router landing pages with the 11 high-conversion elements using ShadCN UI components.'

Add a few natural synonyms users might say (e.g., 'promotion page', 'product launch page') to broaden trigger coverage.

Tighten the framework reference so the niche reads as a single capability rather than 'Next.js or React', which slightly widens overlap risk.

Dimension	Reasoning	Score
Specificity	Names the domain (landing pages via Next.js/React) and a few near-synonymous actions ('create landing pages, marketing pages, or product pages'), but does not enumerate several distinct concrete capabilities, matching the anchor 3 '1-2 concrete actions, not comprehensive'. It is not a 4 because the listed actions are variations of one capability rather than a list of specific operations.	3 / 5
Completeness	Explicitly answers both 'what' ('Comprehensive guide for creating effective landing pages...') and 'when' ('This skill should be used when users request to create landing pages, marketing pages, or product pages...'). It falls short of a 5 because the 'what' is generic ('comprehensive guide') rather than a list of concrete actions paired with the trigger phrases.	4 / 5
Trigger Term Quality	Includes natural user phrases ('landing pages, marketing pages, or product pages') plus concrete tech triggers ('Next.js 14+ App Router', 'ShadCN UI'), giving good keyword coverage. It is not a 5 because some natural synonyms (e.g., 'promotion page', 'squeeze page') and file/extension cues are absent, and not a 3 because coverage is clearly broader than a single keyword.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (Next.js 14+ App Router + ShadCN UI + the '11 essential elements' framework) with distinct triggers, giving mostly distinct scope with minor overlap risk. It is not a 5 because the 'Next.js or React' framing keeps it slightly broad relative to a single tightly-scoped niche.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: bear2u/my-skills
Path: skills/landing-page-guide/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.