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

landing-page登陆页面

Agent Skill

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

总安装

392

周安装

16

GitHub Stars

168

下载量

127
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/whawkinsiv/claude-code-skills --skill landing-page

简介

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

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态或协作事项进行整理。
  • 通过 npx skills add 命令从指定仓库安装并使用。
  • 安装前需确认权限范围和维护状态,避免触发联网或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Landing Page

A landing page is a sales conversation, not a brochure. You have 5 seconds to communicate what the product does and why it matters. This skill gives you the structure and copy for every section.

Core Principles

  • A landing page has ONE goal. Everything serves that goal or gets cut.
  • Structure follows the buyer's internal monologue: "What is this?" -> "Is it for me?" -> "How does it work?" -> "Can I trust it?" -> "What do I do next?"
  • Above the fold is the most valuable real estate on the internet.
  • Long pages can outperform short pages — IF every section earns its place.

Workflow

Landing Page Build:
- [ ] Define the ONE goal (signup, waitlist, demo request)
- [ ] Write the hero section (headline + subheadline + CTA)
- [ ] Plan sections in scroll order
- [ ] Write copy for each section
- [ ] Build the page
- [ ] Test on mobile
- [ ] Add analytics tracking (see analytics skill)

Section-by-Section Build

Hero (Above the Fold)

The hero has 5 elements. Get these right and the rest is easier.

  1. Headline — State the outcome, not the product.

- Be specific: "Cut your deploy time from 45 minutes to 45 seconds" - Not: "Deploy faster"

  1. Subheadline — Add the "how" or a second benefit.
  2. Primary CTA — High contrast, specific action text. "Start building free" not "Get started."
  3. Visual — Product screenshot, short demo, or animated illustration. Show the product in action.
  4. Social proof bar — Logo strip or metric: "Trusted by 15,000+ teams"

Tell AI:

Write the hero section for our landing page:
- Product: [what it does, one sentence]
- Audience: [who it's for]
- Main benefit: [the #1 outcome users get]
- Social proof: [number of users, notable customers, or key metric]

Give me:
- 3 headline options (under 10 words each, outcome-focused)
- Subheadline for each (adds "how" or second benefit)
- Primary CTA button text + anxiety reducer below it
- Social proof line
Pick the strongest option and explain why.

How It Works

Exactly 3 steps. Cognitive simplicity.

Format: [Number/Icon] + [Short title] + [One sentence]

Example:

  1. Connect your repo — Link your GitHub in one click.
  2. Configure your pipeline — Our AI suggests the optimal setup.
  3. Ship with confidence — Deploy automatically on every push.

Feature Sections

Alternate layout: text-left/image-right, then text-right/image-left.

Each feature: [Eyebrow label] + [Benefit headline] + [2-3 sentence description] + [Screenshot]

Lead with benefit, not feature name:

  • BAD: "Advanced Analytics Dashboard"
  • GOOD: "Know exactly what's working — and what's not"

Testimonials

  • Include: Name, title, company, headshot.
  • Quote should mention: a specific result, a before/after, or an emotional reaction.

- GOOD: "We cut onboarding from 2 weeks to 2 days. New hires actually thank us now." — Sarah Chen, VP Eng @ Acme - BAD: "Great product, really love it!" — J.S.

  • Place near objection points (security testimonial near pricing, etc.)

FAQ

Must answer for any SaaS:

  1. "Is there a free plan / trial?"
  2. "How long does setup take?"
  3. "Can I cancel anytime?"
  4. "Is my data secure?"
  5. "What integrations do you support?"
  6. One or two product-specific questions.

Final CTA

Repeat the primary CTA with a slightly different angle. Different headline, same action.


Full Page Build

Tell AI:

Build a landing page for our SaaS product:
- Product: [what it does]
- Audience: [who it's for]
- Main benefit: [#1 outcome]
- Features: [list 3-4 key features]
- Social proof: [logos, metrics, testimonials you have]
- CTA: [what you want visitors to do — signup, waitlist, demo]

Use this section order:
1. Hero (headline, subheadline, CTA, social proof bar)
2. Problem agitation (articulate the pain they're feeling)
3. How it works (3 steps)
4. Feature sections (3-4, alternating layout with screenshots)
5. Testimonials (use placeholders if I don't have real ones yet)
6. Pricing preview or "See plans" CTA
7. FAQ (6-8 questions)
8. Final CTA (different angle, same action)

Make it responsive. Use [Tailwind / our existing design system].
If I'm using Lovable: keep the prompt focused on what the user sees, not implementation details.

Improving an Existing Page

Tell AI:

Review our landing page at [URL or file path] and improve it:
- Check: Is the headline outcome-focused or feature-focused?
- Check: Is there a clear single CTA above the fold?
- Check: Does social proof appear early?
- Check: Does the page follow the buyer's monologue
  (What is this → Is it for me → How does it work → Can I trust it → What do I do)?
- Rewrite any weak sections
- Add missing sections (FAQ, testimonials, final CTA)

Performance Requirements

  • Load time: <2 seconds on 3G
  • LCP (Largest Contentful Paint): <2.5 seconds
  • No layout shift on load (CLS <0.1)
  • Lazy load everything below the fold
  • Hero image/video optimized aggressively

Common Mistakes

MistakeFix
No clear CTA above the foldOne high-contrast button with specific action text
Feature-focused headlineState the outcome the user gets, not what the product does
"Get started" or "Learn more" CTAsBe specific: "Create your first dashboard"
No social proofAdd logos, user count, or testimonial — even one helps
Missing FAQ sectionAnswer the 5-6 questions every buyer has
Desktop-only design50%+ of traffic is mobile. Test there first.
Trying to say everythingOne page, one goal, one audience. Cut the rest.

Related Skills

  • copywriting — Write stronger headlines, CTAs, and microcopy
  • conversion — CRO techniques for higher signup rates
  • seo — Make the landing page rank for target keywords
  • brand-identity-generator — Establish visual identity before building
  • beautify — Make the page look intentionally designed

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Claude

34.34%
按下载量换算44

Codex

33.83%
按下载量换算43

Cursor

20.61%
按下载量换算26

Gemini CLI

8.79%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

来源信息

继续浏览同类 Skills