Token导航 LogoToken导航TokenDH.com
前端设计只读github未标认证来源可访问许可证需确认审计通过

landing-page-optimization着陆页优化

Agent Skill

landing-page-optimization 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

4,488

周安装

187

GitHub Stars

42

下载量

1,496
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:landing-page-optimization(着陆页优化)
来源仓库:https://github.com/manojbajaj95/claude-gtm-plugin
仓库路径:skills/landing-page-optimization
安装命令:
npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill landing-page-optimization
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill landing-page-optimization

简介

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态进行整理。
  • 通过 npx 命令从指定仓库安装并使用。
  • 需确认权限范围和维护状态,避免触发联网或文件操作。
  • landing-page-optimization 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Landing Page Optimization

Build, write, and optimize high-converting landing pages combining proven copy frameworks, the 11-essential-elements structure, and a clear creation workflow.


1. Copy Framework

Gather Before Writing

Collect these inputs before drafting any copy:

  • Product/service name and core value proposition
  • Target audience and their primary pain point
  • Key differentiator vs alternatives
  • Desired visitor action (CTA goal)
  • Available social proof (testimonials, stats, logos)

Choose a Framework

FrameworkWhen to Use
PAS (Problem → Agitate → Solution)Strong pain point, emotional product
AIDA (Attention → Interest → Desire → Action)General purpose, awareness campaigns
StoryBrand (Hero → Guide → Plan → CTA → Success)Brand narrative, relationship-driven sales

Section Copy Guide

Hero — Value prop in ≤10 words; subheadline adds specificity; CTA + 1 trust signal above fold.

Headline formulas:

  • [Achieve outcome] without [pain point]
  • The [adjective] way to [desired result]
  • Stop [bad thing]. Start [good thing].

Problem — Name the pain in the audience's language; 2–3 specific scenarios; emotional, not clinical.

Solution — How the product solves it; 3–5 features written as benefits ("saves 2 hrs/day" not "automated scheduling").

How It Works — 3–4 steps, each with a clear action verb; close with CTA.

Social Proof — Testimonial template: "[Specific result]..." — Name, Title, Company. Aim for 4–6 testimonials; include stats and logos if available.

Pricing — Highlight recommended plan; include guarantee copy; one CTA per plan card.

FAQ — 5–10 objection-handling questions; cover pricing, refunds, technical requirements, comparison to alternatives.

Final CTA — Repeat the primary CTA; add urgency or risk-reversal ("Cancel anytime", "30-day guarantee"); larger and more dramatic than hero CTA.

CTA Copy Rules

  • Start with an action verb
  • Be specific: "Start My Free Trial" > "Submit"
  • First-person phrasing often converts better ("Get My Guide")
  • Avoid: "Click Here", "Learn More", "Submit"

Copy Best Practices

  • Active voice, present tense; benefits before features
  • Specific numbers over vague claims ("saves 2 hours" not "saves time")
  • Short sentences; scannable with headers and bullets
  • Address objections before the reader voices them
  • Multiple CTAs (same action) throughout — not multiple competing actions

2. Design Principles (11 Essential Elements)

Every landing page needs all 11 elements. See references/11-essential-elements.md for full detail on each.

#ElementConversion PurposeDesign Note
1URLSEO slug with keywords
2Header/LogoBrand trust, navigationSticky with blur-on-scroll
3Hero Title + SubtitleClear value prop, H1 with keywordsDistinctive display font, 4–6rem
4Primary CTAHero conversionContrasting color, micro-interaction on hover
5Social ProofCredibility, reduce hesitationAnimated counts, overlapping avatars
6Images/VideosProduct demonstrationDevice mockups or demo video; no stock photos
7Benefits/FeaturesJustify the purchase3–6 items with icons; benefits-first copy
8TestimonialsPeer validation4–6 with photo + name + role; specific results
9FAQObjection removalAccordion; 5–10 questions
10Final CTASecond conversion chanceFull-width section; urgency elements
11FooterTrust + legalContact info, privacy policy, social links

Aesthetic Direction

Pick ONE direction and execute it consistently:

DirectionFeelSuits
MinimalistClean whitespace, monochromaticPremium SaaS, professional services
Bold/MaximalistRich layers, vivid colorsCreative agencies, consumer brands
Retro-FuturisticGeometric, neon, monospaceDev tools, gaming, tech startups
OrganicSoft shapes, earth tonesWellness, food, sustainability
EditorialStrong type hierarchy, asymmetric gridsMedia, content platforms

Avoid: purple gradients on white (overused AI aesthetic), perfectly symmetric layouts on every section, stock photos of people pointing at laptops, default yellow stars.

Tech Stack (when building)

Next.js 14+ · TypeScript · Tailwind CSS · ShadCN UI

Build order: Design system → SEO metadata → Header → Hero (with animations) → Media → Benefits → Testimonials → FAQ → Final CTA → Footer.

See references/component-examples.md for production-ready ShadCN component implementations.


3. Creation Workflow

Follow this sequence for any landing page project:

Step 1 — Define the Goal

  • Single conversion action (one CTA target)
  • Audience segment this page serves
  • Traffic source (ad, email, organic) — shapes tone and assumed context

Step 2 — Structure First Use the full 11-element structure. Resist shortcutting: pages missing Social Proof or FAQ consistently underperform.

Step 3 — Write Copy Apply the Copy Framework (§1). Write hero copy first — if the value prop isn't clear in 10 words, clarify the offer before continuing.

Step 4 — Design Choose aesthetic direction, define design system (fonts, colors, motion), then build section by section.

Step 5 — Optimize

  • Above the fold: value prop + CTA + one trust signal visible without scrolling
  • Multiple CTAs with identical action (not competing goals)
  • Minimal form fields; reduce every friction point
  • Mobile-first; test on real devices
  • Performance: LCP <2.5s, CLS <0.1, no layout shifts

Step 6 — Launch Checklist

  • Headline is benefit-focused, specific, ≤10 words
  • Single primary CTA throughout
  • Social proof present and specific
  • Mobile responsive
  • Page loads <3s
  • Trust signals visible above fold
  • FAQ covers top 5 objections
  • Analytics tracking configured

References

  • references/11-essential-elements.md — Detailed breakdown of each element with implementation guidance and good/bad examples
  • references/component-examples.md — Production-ready ShadCN UI components for Hero, Benefits, Testimonials, FAQ, Final CTA, and Footer sections

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.91%
按下载量换算507

Claude

32.26%
按下载量换算483

Cursor

19.75%
按下载量换算295

Gemini CLI

10.06%
按下载量换算150

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills