Landing page
Quick answer
- 01What is it?
- Check for product marketing context first: If .agents/product-marketing.md exists (or .agents/product-marketing-context.md or .claude/product-marketing-context.md in older. Its edge is a particular angle on conversion optimization, giving the agent tighter constraints than a plain landing page request.
- 02Inputs
- Context for conversion optimization: your goals, audience, constraints, and any source material the skill asks for.
- 03Output
- A ready-to-use result for conversion optimization: the analysis, copy, or recommendations the agent produces.
Add this skill
Install as a package
Installs this one skill package for your coding agent, including any supporting files that skill ships with — not every skill in the repository. Read the tutorial.
$ npx skills add realjaymes/marketingagentskills --skill landing-pageSkill instructions
The instruction file for this skill. The skill also includes other files you need to install to use it.
Landing Page Assistant
Check for product marketing context first:
If .agents/product-marketing.md exists (or .agents/product-marketing-context.md or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Generate structured, conversion-focused landing page copy using the modular section framework.
When to Use
- User wants to create a new landing page or homepage
- User needs copy for specific landing page sections
- User mentions "landing page template," "homepage copy," or "page sections"
Instructions
- Confirm page type: Homepage, feature page, or campaign landing page
- Gather inputs: Product name, value proposition, target audience, key features, social proof
- Generate section-by-section copy following the template structure
- Include visual/CTA notes for each section
Section Structure
Generate copy for each section in order:
Hero Section
- Headline: Action statement explaining unique value proposition
- Subheadline: 1-2 sentences explaining product and how it creates value
- Bullet Points: 2 specific claims, 2 objection handles, 3 social proof points
- Social Proof: Testimonials, logos, ratings, stats
- Hero CTA: Action-focused, value-focused, or objection-handling
Problem to Solution Comparison
- Before vs After: Pain points vs solution benefits
- Old Way vs New Way: Limitations vs capabilities
- CTA: Reinforce action
Features, Capabilities & Benefits
For each feature (3-6 features):
- Heading: Feature name
- Description: Capability + Benefit
- Visual note: Image suggestion
- CTA: Feature-specific action
Integrations
For each integration (2-4):
- Heading: Integration name
- Description: Capability + Benefit
- Visual: Logo placement
How It Works
For each step (3-5 steps):
- Heading: Step title
- Description: What user does/gets
- Visual note: Screenshot suggestion
FAQs
- Feature FAQs: 2-3 questions about features
- Objection FAQs: 2-3 questions addressing concerns
Second CTA Section
- Heading: Switch/upgrade focused
- Description: Value outcome statement
- Bullet Points: Objection handles + ease of start
- CTA: Clear next action
Founder's Note (Optional)
- Put yourself in their shoes
- Explain their problem
- Take ownership
- Show the happy ending
Output Format
## [Section Name]
**Headline**: [Copy]
**Subheadline**: [Copy]
**Bullet Points**:
- [Point 1]
- [Point 2]
**CTA**: [Button text]
**Visual Note**: [Suggestion]
Constraints
- Each section must have Headline, Description, and CTA (where applicable)
- Use bullet points for feature/benefit lists
- Bold key phrases and product names
- No generic filler text
- Use placeholders [Product Name] if info missing
- Hyphen rules: Hyphens connect words (well-being); en dashes for ranges (June-August); em dashes for breaks in thought
Reference
See references/landing-page-framework.md for complete section templates and examples.
Supporting file: references/landing-page-framework.md
Landing Page Framework Template
Use completed positioning and messaging documents with this template to create landing pages. Best for homepages.
Hero Section
| Element | Description |
|---|---|
| Headline | Action statement explaining unique value proposition |
| Subheadline | 1-2 sentences explaining product and how it creates value |
| Bullet Points | Bold specific claim 1, Bold specific claim 2, Objection handle 1, Objection handle 2, Social proof 1-3 |
| Social Proof | Testimonials, logos, third-party ratings, stats, team proof points |
| Hero Image | Visual showing product in action |
| Hero CTA | Action (Sign up), Next step (Get started), Value (show me my heatmap), Objection (Schedule free call) |
Problem to Solution Comparison
| Element | Description |
|---|---|
| Before vs After | Pain points vs solutions, Old limitations vs new capabilities |
| CTA | Action, next step, value, or objection-handling |
Features, Capabilities & Benefits
For each feature (6 max):
- Heading: Feature name
- Description: Capability + Benefit
- Visual: Image of feature in action
- CTA: Feature-specific action
Integrations
For each integration (3 typical):
- Heading: Integration name
- Description: Capability + Benefit
- Visual: Integration logo
How It Works
For each step (5 typical):
- Heading: Step title
- Description: What they need to get outcome
- Visual: Screenshot of step
FAQs
- Feature FAQs: Questions about features + responses
- Objection FAQs: Questions addressing concerns + responses
Second CTA Section
| Element | Description |
|---|---|
| Heading | Switch to [product] in [time] or less |
| Description | You shouldn't have to [pain]. With [product], you can [value outcome]. |
| Bullet Points | Objection handles + ease of getting started |
| CTA | Next action |
| Hero Image | Product visualization |
| Social Proof | Testimonials, logos, ratings, stats |
Founder's Note/Manifesto
Story structure:
- Put yourself in their shoes
- Explain their problem
- Take ownership of it
- Show the happy ending
Include founder headshot + role.
Section Purpose Summary
| Section | Purpose |
|---|---|
| Hero Section | Communicate core value proposition with headline, subheadline, CTA, and proof |
| Problem & Solution | Highlight pain points and contrast with solution |
| Features & Benefits | Showcase capabilities translated into user benefits |
| Integrations | Demonstrate ecosystem compatibility |
| How It Works | Walk through journey from signup to outcome |
| FAQs | Address product and objection questions |
| Second CTA | Reinforce value-driven CTA with ease messaging |
| Founder's Note | Humanize brand through authentic story |
Common questions
How do I install Landing page in Cursor, Claude Code, or Codex?
Run npx skills add realjaymes/marketingagentskills --skill landing-page in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Landing page, not every skill in the repository.
Where does Landing page come from and what license is it under?
Landing page comes from the realjaymes/marketingagentskills repository on GitHub. That repository has 40 GitHub stars. The skill is published under the MIT license.
Prefer plain text? Read the Landing page guide as markdown.
Related skills
More from realjaymes