Agent skill · Content & Marketing

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.

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill landing-page-copy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/landing-page-copy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Landing Page Copy Write copy for pages with a single conversion goal: signup, purchase, demo request, download, lead capture. Stack-agnostic. This skill is narrower than `content-and-copy`. Landing pages exist to drive a specific action, not to inform broadly. --- ## When to use - Writing a hero section for a homepage or product page - Writing a sales page or long-form sales letter - Drafting opt-in or lead-capture page copy - Campaign-specific landing pages - Pricing page copy - Demo or signup CTAs ## When NOT to use - Long-form blog content (use `content-and-copy`) - Email sequences (use `email-sequences`) - Brand voice definition (use `brand-voice`) - Page design and layout decisions (use `design-standards`) --- ## Required inputs - The product, service, or offer - The target audience and the specific objection they bring - The conversion goal (one specific action) - Brand voice - Existing customer language (testimonials, support tickets, sales calls) - Any constraints (length, format, regulatory) If audience is unclear or objections are unknown, run `brand-discovery` or pull from sales call recordings before writing. --- ## The framework: 7 sections A landing page does seven

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 7 sections
  5. 1. Hero
  6. 2. Social proof (early)
  7. 3. Problem / promise
  8. 4. Solution / mechanism
  9. 5. Proof and detail
  10. 6. Objection handling
  11. 7. Final CTA
  12. The CTA itself
  13. Workflow
  14. Failure patterns
Ships with 2 files
  • references/hero-formulas.md
  • references/objection-library.md
More from claude-skills
All skills →
About this skill
What does the landing-page-copy skill do?

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.

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill landing-page-copy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going