Token导航 LogoToken导航

Agent Skill · 前端设计

landing-page-optimization(着陆页优化)

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

landing-page-optimization 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 6,853。

总安装 447周安装 19GitHub Stars 40下载 157核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

着陆页优化技能用于提升网站转化率与用户体验。适用于前端设计与页面性能调优场景,支持多宿主环境集成。通过 GitHub 安装后可在 Codex、Claude、Cursor 等工具中调用。使用前请确认仓库权限与维护状态,避免触发未授权操作或文件修改。建议结合原始 README 文档了解具体功能与使用限制。

来源仓库内路径:skills/landing-page-optimization

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/manojbajaj95/gtm-skills --skill landing-page-o…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

landing-page-optimization 怎么安装?

在终端执行 npx skills add https://github.com/manojbajaj95/gtm-skills --skill landing-page-optimizatio…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

landing-page-optimization 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

landing-page-optimization 需要什么权限?

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

landing-page-optimization 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

landing-page-optimization 用的人多吗?

公开数据是累计安装 447 次,近一周安装 19 次,下载 157 次,GitHub 40 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

landing-page-optimization 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
landing-page-optimization

着陆页优化 · 本页

44740只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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

平台分布

Codex

34.88%
按下载量换算55

Claude

31.07%
按下载量换算49

Cursor

16.56%
按下载量换算26

Gemini CLI

8.4%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills