landing-page-copy

Write landing page copy with attention to the hero, value proposition, social proof, objection handling, and conversion-focused CTAs. Use this skill whenever the user wants to write a landing page, sales page, hero section, or any conversion-focused web copy. Triggers on landing page, sales page, hero copy, value proposition, headline, subheadline, hero section, CTA copy, conversion copy, opt-in page, squeeze page. Also triggers when the user has a marketing campaign or product launch needing dedicated conversion copy.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-structured, actionable copywriting skill with a clear framework, concrete examples, a sequenced workflow with checkpoints, and properly externalized reference files. The only weakness is mild verbosity from some repeated and lengthy pattern lists that could be condensed.

Suggestions

Consolidate the duplicate CTA guidance — the 'Final CTA' section (step 7) and the standalone 'The CTA itself' section overlap; merge or cross-reference to cut length.

Trim the parallel strong/weak pattern lists (hero, CTA) to the highest-value examples; the contrasts are useful but the current volume competes with the token budget.

Consider moving the full strong/weak headline pattern catalog into references/hero-formulas.md and keeping only the top 2-3 patterns inline in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but the ~260-line body repeats some material (CTA guidance appears in both 'Final CTA' and 'The CTA itself', strong/weak pattern lists run long) and could be tightened without losing clarity.	2 / 3
Actionability	Highly concrete for an instruction-only skill: specific strong/weak hero and CTA patterns with example copy, named objection types, a 9-step workflow, and a copy-paste-ready output-format template.	3 / 3
Workflow Clarity	The 9-step Workflow is clearly sequenced with explicit checkpoints (draft 5-10 hero variations, read-aloud CTA test, pre-publish checklist for links/spell-check/mobile/SEO).	3 / 3
Progressive Disclosure	Body serves as the framework overview and points to two well-signaled, one-level-deep references (hero-formulas.md, objection-library.md) that are real files with descriptive links; detail is appropriately split out.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive description that clearly states capabilities, packs in natural trigger terms, and explicitly covers both what and when. Voice is imperative/third person throughout, consistent with the good examples and free of first/second-person penalty.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete components of the task — 'hero, value proposition, social proof, objection handling, and conversion-focused CTAs' — each a specific action rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Write landing page copy with attention to...') and when ('Use this skill whenever the user wants to write... Triggers on...'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Strong coverage of natural user phrasings: 'landing page, sales page, hero copy, value proposition, headline, subheadline, CTA copy, conversion copy, opt-in page, squeeze page' plus 'marketing campaign or product launch'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (conversion-focused web copy) with distinct triggers; 'conversion-focused' framing and narrow scope make conflict with adjacent content skills unlikely.	3 / 3
	Total	12 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Commit: f1bc195

Reviewed: 11 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.