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.
80
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/landing-page-guide/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has strong completeness with explicit 'when to use' guidance and good trigger term coverage. However, it lacks specificity about what concrete actions or elements it actually provides (the '11 essential elements' are mentioned but not enumerated). The distinctiveness could be improved by being more precise about what differentiates this from general React/Next.js development skills.
Suggestions
List 2-3 of the '11 essential elements' explicitly (e.g., 'hero sections, CTAs, testimonials, pricing tables') to improve specificity
Add file extension triggers like '.tsx' or mention specific ShadCN components to strengthen distinctiveness from generic web development skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (landing pages) and framework (Next.js/React), mentions '11 essential elements' but doesn't list what those concrete actions or elements actually are. The description tells us it's a 'comprehensive guide' but doesn't specify what concrete actions it enables. | 2 / 3 |
Completeness | Explicitly answers both what ('creating effective landing pages using Next.js or React') and when ('when users request to create landing pages, marketing pages, or product pages'). Has clear 'should be used when' clause with explicit triggers. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms: 'landing pages', 'marketing pages', 'product pages', 'Next.js', 'React', 'ShadCN UI'. These are terms users would naturally use when requesting this type of work. | 3 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to landing pages with Next.js/ShadCN, but could overlap with general React component skills or other UI/web development skills. The 'marketing pages' and 'product pages' terms broaden scope and increase potential conflict. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent workflow clarity and progressive disclosure. The validation checklist is a strong feature for ensuring completeness. However, it could be more concise by removing explanatory content Claude already knows (like why ShadCN is good) and more actionable by including at least one complete component example inline rather than deferring all implementations to reference files.
Suggestions
Remove the 'Why ShadCN UI?' section - Claude already knows these benefits and this wastes tokens
Include at least one complete, executable component example (e.g., the Hero section) inline rather than deferring all to reference files
Trim the 'When to Use This Skill' section - the bullet points are redundant with the overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation (e.g., 'Why ShadCN UI?' section explaining benefits Claude already knows) and could be tightened. However, it's mostly efficient with good use of lists and code blocks. | 2 / 3 |
Actionability | Provides concrete bash commands and TypeScript code snippets, but the main component implementations are deferred to reference files rather than being directly executable. The metadata example is copy-paste ready, but component examples are only described, not shown. | 2 / 3 |
Workflow Clarity | Clear 6-step implementation workflow with explicit ordering. The validation checklist at the end serves as an excellent checkpoint system, ensuring all 11 elements and technical requirements are verified before completion. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, then detailed sections. References to external files (11-essential-elements.md, component-examples.md) are one level deep and clearly signaled. Content is appropriately split between overview and detailed references. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- bear2u/my-skills
- Commit
1be5394
- 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.