landing-page-design
Design Higher-Converting Landing Pages
Landing pages often fail because message, proof, and CTA placement are unclear. This skill gives Claude, Codex, and Claude Code practical rules for hero sections, social proof, forms, mobile layout, and AI-generated visuals.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "landing-page-design" from https://skillstore.io/skills/halt-catch-fire-landing-page-design.md and its manifest at https://skillstore.io/api/skills/halt-catch-fire-landing-page-design/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "landing-page-design". A founder needs a landing page for an AI meeting notes product.
Expected outcome:
- Headline: Turn every meeting into a clear action plan.
- Subheadline: Capture decisions, owners, and follow-ups automatically so teams leave every meeting aligned.
- Primary CTA: Start Free Trial. Social proof should appear directly below the CTA.
Using "landing-page-design". A SaaS marketer asks why a signup page has weak conversion.
Expected outcome:
- The hero headline is vague and does not state the user outcome.
- The form asks for too much information before trust is established.
- Move customer logos above the first scroll point and repeat the CTA after pricing.
Using "landing-page-design". A designer needs hero image direction for a dashboard product.
Expected outcome:
Show the outcome of using the dashboard: a team reviewing clear growth results on one screen. Avoid abstract backgrounds and hard-to-read screenshots.
Security Audit
Medium RiskThe skill is a landing page design guide, but it tells agents to run belt and npx commands. Those commands invoke external services or install related skills, which creates medium external command risk. Most other static backtick findings are Markdown formatting false positives, and no prompt injection text was found.
Confirmed security concerns (1)
Capability review items (9)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (18)
🌐 Network access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/halt-catch-fire-landing-page-design/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/halt-catch-fire-landing-page-design?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/halt-catch-fire-landing-page-design?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/halt-catch-fire-landing-page-design/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/halt-catch-fire-landing-page-design.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
halt-catch-fire. (2026). landing-page-design security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/halt-catch-fire-landing-page-design/audits/4BibTeX citation
@techreport{halt-catch-fire-halt-catch-fire-landing-page-design-2026,
author = {halt-catch-fire},
title = {landing-page-design security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/halt-catch-fire-landing-page-design/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "landing-page-design security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "halt-catch-fire"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/halt-catch-fire-landing-page-design/audits/4"
identifiers:
- type: other
value: "skillstore:halt-catch-fire-landing-page-design:audit:4"
description: "Skillstore immutable audit report identifier"
Compare variants
3 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
2389-research-landing-page-design
2026-08-21
halt-catch-fire-landing-page-design
2026-08-21
101-skills-landing-page-design
2026-08-21
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Plan a Startup Launch Page
Create a clear first-page structure with an outcome headline, primary CTA, proof section, and signup form guidance.
Improve SaaS Conversion Copy
Review hero messaging, CTA text, social proof placement, and pricing flow for a product marketing page.
Guide Visual Direction
Translate product outcomes into hero image concepts, OG image prompts, and mobile-first layout requirements.
Try These Prompts
Use the landing-page-design skill to outline a landing page for [product]. Include headline, subheadline, primary CTA, social proof, and section order.
Review this hero section for conversion clarity: [paste copy]. Suggest a stronger headline, subheadline, CTA text, and proof placement.
Use the skill to adapt this landing page for mobile users: [describe page]. Prioritize CTA access, form length, typography, and image behavior.
Compare my landing page goals with three competitor examples. Identify message gaps, proof gaps, risky claims, and A/B test ideas.
Best Practices
- Start with one clear user outcome before choosing layout, copy, or visuals.
- Place the primary CTA and strongest proof where users can see them without scrolling.
- Validate claims, social proof, and conversion recommendations with current evidence.
Avoid
- Using a vague headline that describes the company instead of the customer outcome.
- Adding multiple competing CTAs before the visitor understands the offer.
- Using decorative hero images that do not explain the product result.
Frequently Asked Questions
What does this skill help create?
Can it generate images?
Does it write production code?
Is it useful for SaaS pages?
Should teams trust every conversion claim?
Which AI tools can use it?
Developer Details
Author
halt-catch-fireLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
30c73eac2afe762f6aa9c4553158769369d47351
Maintenance freshness
7/18/2026
Usage
6 downloads · 0 views
File structure
📄 SKILL.md