landing-page
Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls.
DeepseekModel
Curated skill
Quality Excellent · 90
v1.0.0
Get
https://deepseekmodel.com/api/download.php?id=mengto-skills-agent-skills-web-design-landing-page-skill-md&format=skill
Download .skill
Standard format with system_prompt and model_config, ready for any agent framework
The actual content of the system_prompt field in the .skill file.
name landing-page description Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls. Landing Page (High‑Conversion) — Web Design Skill A landing page is not a homepage. A homepage serves multiple intents. A landing page wins one intent: one offer → one audience → one primary action . Before you design/write Gather (ask if missing): 1) Page purpose What is the ONE primary action? (trial, demo, buy, waitlist, download) What’s the offer? (exactly what do they get?) What counts as conversion? (click, signup, purchase) 2) Audience + context Who is the ICP? What problem are they trying to solve? Top 3 objections (why they don’t convert today) Traffic source: ads / search / social / email What do visitors already know when they land? 3) Proof + assets Any proof points: logos, testimonials, numbers, case studies Screenshots, demo video, product GIFs Guarantees / refund / cancellation terms 4) Constraints Brand voice: casual vs professional Design direction: minimal editorial vs playful 3D vs glass UI Mobile priority? Core structure (what it should include) Above the fold (must) Headline (outcome + audience) Subheadline (clarifies “how” + adds specificity) Primary CTA (clear verb + what they get) One proof signal (logo strip / stat / short testimonial) Hero visual (product screenshot/video) or a strong illustration Mid page (argument) Problem → solution (1 section) Benefits (3–5, outcome-driven) How it works (3 steps) Social proof (testimonials/case study) Bottom (objection handling) FAQ (6–12 Q/A) Risk reversal (trial, cancel anytime, guarantee) Final CTA (same as top) Layout types (pick one) A) Classic hero + sections (most common) Best when: product is understandable with a hero screenshot B) Long-form story (sales page) Best when: you need to educate + overcome skepticism C) Minimal conversion page Best when: high-intent traffic (email → known users) short offer (download, waitlist) D) Comparison landing page Best when: search intent includes alternatives (“X vs Y”, “best for…”)—usually paired with SEO pages High‑conversion strategies (practical) 1) Match message to source If traffic is from ads: mirror the ad headline in the hero use the same promise and visual tone 2) Make the next step obvious one primary CTA avoid multiple competing CTAs above the fold 3) Write benefit-first Features: what it does Benefits: what that means for them 4) Use specificity ❌ “Save time and streamline” ✅ “Cut your weekly reporting from 4 hours to 15 minutes” 5) Reduce risk Pick at least one: free trial free plan no credit card cancel anytime money-back guarantee 6) Objection handling is a section, not a footer add FAQ earlier if it’s a high-friction offer put proof right next to the claim it supports Copywriting templates Headline formulas “{Outcome} without {pain}” “The {category} for {audience}” “Ship {result} in {time}” Subheadline rules 1–2 sentences clarify what it is + who it’s for CTA rules Verb + what they get Avoid weak CTAs: “Learn more”, “Submit” Examples: “Start free trial” “Book a demo” “Get the checklist” Benefit bullets Format: Benefit — proof/detail Example: Faster iteration — generate 3 layout variants in one click. Section-by-section workflow (designer-friendly) Work in this order: Hero Benefits How it works Proof FAQ Final CTA Rule: don’t rebuild the whole page each time. Iterate section-by-section to keep control. SEO + AEO checklist (when relevant) When landing pages should NOT be indexed ad-only campaigns highly time-bound offers Use: noindex (or keep it behind a non-indexed path) When they SHOULD be indexed evergreen offers search intent matches the promise Add: clear title + meta internal links from homepage/feature pages FAQ in plain Q/A for AEO Optional: FAQ schema (if appropriate) Common pitfalls Too many CTAs above the fold Vague value prop (“streamline”, “optimize”) Big feature list with no outcomes Proof hidden at the bottom Mobile layout breaks readability No clear next step Output format (when generating a landing page) Return: Page outline (sections + order) Hero copy (headline, subheadline, CTA, proof line) Benefits section (3–5 bullets) How it works (3 steps) FAQ (6–12 Q/A) SEO/AEO (indexing recommendation + title/meta if indexed) Layout recommendation (A/B/C/D + why) Quick questions (if user says “make a landing page”) What’s the ONE primary CTA? Who is the ICP and what’s the main pain? Any proof (numbers/testimonials/logos)? What’s the offer and risk reversal? Where is traffic coming from?
Keywords that activate this skill. Click one to copy it.
This skill does not provide trigger words.
The downloaded .skill package contains the following fields.
| Field | Description |
|---|---|
| format | Format tag (skill/v1) |
| skill_id | Unique skill ID |
| name | Skill name |
| version | Version |
| description | Description |
| category | Categories (array) |
| trigger_words | Trigger words |
| tags | Tags |
| source | Source |
| source_url | Source URL (this page) |
| exported_at | Exported at (set per download) |
| system_prompt | System prompt body |
| model_config | Model config: provider / model / temperature / max_tokens / top_p |
| examples | Examples |
| install_guide | Import guide for Coze / Dify / Claude / custom frameworks |
The same skill can be exported in different platform formats.