Skills Plugins MCP Prompt Model 博客 我的中心
コンテンツ制作 #seo #design #writing

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 キュレーション済みスキル 品質 優秀 · 90 v1.0.0

取得

https://deepseekmodel.com/api/download.php?id=mengto-skills-agent-skills-web-design-landing-page-skill-md&format=skill
ダウンロード .skill 標準形式。system_prompt と model_config を収録し、任意の Agent で利用可能
.skill ファイルの system_prompt フィールドの実際の内容。
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?
このスキルを起動するキーワード。クリックでコピーできます。

このスキルにはトリガーワードがありません。

ダウンロードした .skill に含まれるフィールド。
フィールド 説明
formatフォーマット識別子(skill/v1)
skill_idスキル固有 ID
nameスキル名
versionバージョン
description説明
categoryカテゴリ(配列)
trigger_wordsトリガーワード
tagsタグ
sourceソース
source_urlソース URL(本ページ)
exported_atエクスポート日時(ダウンロード毎)
system_promptシステムプロンプト本文
model_configモデル設定:provider / model / temperature / max_tokens / top_p
examplesサンプル
install_guide各プラットフォームの導入説明(Coze / Dify / Claude / カスタム)
同じスキルを各プラットフォーム形式で出力できます。
.skill 標準形式。system_prompt と model_config を収録し、任意の Agent で利用可能 ダウンロード
.skillpro 拡張形式。scripts / tools / dependencies / hooks を含む ダウンロード
.json 純粋な JSON 出力。system_prompt とモデル設定のみ ダウンロード
Coze frontmatter 付き Markdown。Coze へのインポート用 ダウンロード
Dify Dify DSL。アプリ作成後にそのままインポート ダウンロード

每日精选 Skill 推荐,免费送到你邮箱

输入邮箱,每天接收一个精选 AI Agent 技能推荐。完全免费,持续更新。

提交后我们会发送一封确认邮件,点击邮件里的链接才会开始收信。

完全免费,取消任意时间。我们不会发送垃圾邮件。