When the user needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts.
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/landing-page/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 is a strong description that clearly identifies a specific niche (landing page conversion optimization) with concrete actions and natural trigger terms. Its main weakness is structural: it's written entirely as a 'when' clause without a separate declarative statement of what the skill does, which slightly reduces completeness. The specificity and distinctiveness are excellent.
Suggestions
Restructure to lead with a declarative 'what' statement followed by a 'Use when...' clause, e.g., 'Creates, critiques, and optimizes landing pages for conversion, including headline rewrites, CTA placement, layout restructuring, and full page copy drafts. Use when the user asks about landing pages, conversion optimization, CTAs, or page copy.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'headline rewrites, CTA placement, layout restructuring, or full page copy drafts' along with higher-level actions 'create, critique, or optimize a landing page for conversion'. | 3 / 3 |
Completeness | The description effectively answers 'what' (create, critique, optimize landing pages with specific sub-tasks) and has a 'when' framing ('When the user needs to...'), but it reads more as a single 'when' clause without a separate explicit 'what it does' statement. It lacks a clear two-part structure with distinct 'what' and 'when' sections, though the trigger guidance is present. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'landing page', 'conversion', 'headline', 'CTA', 'layout', 'copy drafts'. These are terms a user would naturally use when requesting this type of help. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to landing page conversion optimization, which is a distinct niche. The combination of 'landing page', 'conversion', 'CTA placement', and 'headline rewrites' makes it unlikely to conflict with general copywriting or web development skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%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-organized landing page skill with a clear workflow and good examples, but it's overly verbose for Claude's capabilities—many of the CRO and copy principles are marketing fundamentals that don't need this level of explanation. The actionability is decent with concrete headline patterns and examples, but would benefit from structured templates or output schemas. The content would be stronger if the extensive frameworks section were split into a reference file, keeping the main skill leaner.
Suggestions
Trim the Copy Principles and Conversion Principles sections to bullet-point reminders rather than explanations—Claude already understands concepts like 'specificity beats cleverness' and 'mobile-first design'.
Add a structured output template or schema for both audit and draft modes, so Claude produces consistent, actionable deliverables rather than freeform advice.
Move the Frameworks & Best Practices section (page-specific CRO, copy principles, conversion principles) into a separate reference file like FRAMEWORKS.md and link to it from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some verbose explanations that Claude would already know (e.g., explaining what specificity means in copy, general mobile-first principles, basic CRO concepts). Several sections could be tightened—for instance, the Copy Principles and Conversion Principles sections contain marketing fundamentals that don't need this level of elaboration for Claude. | 2 / 3 |
Actionability | The skill provides structured frameworks and headline patterns with concrete examples (e.g., 'Deploy to production in 3 commands, not 30 steps'), but lacks truly executable artifacts—no templates, no structured output schemas, no copy frameworks that could be directly filled in. The guidance is specific enough to be useful but sits between abstract advice and fully actionable templates. | 2 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced and logically ordered from identification through friction analysis. The output format section provides clear branching based on task type (auditing vs. drafting). While there are no explicit validation checkpoints, this is an advisory/creative skill rather than a destructive operation, so the sequential clarity is appropriate. | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom (content-strategy, seo-technical, cold-outreach), which is good. However, the content is quite long and monolithic—the Frameworks & Best Practices section with its sub-sections on page-specific CRO, copy principles, and conversion principles could be split into separate reference files. The inline examples at the end are helpful but the overall document would benefit from better content splitting. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
4ad31b4
Table of Contents
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.