Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

landing-page登陆页面

Agent Skill

landing-page 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

824

周安装

34

GitHub Stars

115

下载量

269
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/shawnpang/startup-founder-skills --skill landing-page

简介

landing-page 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 适用于研究检索类任务,可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 通过 npx skills add 命令从 GitHub 仓库安装,支持主流 AI 宿主环境。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 当前顶部介绍为空,需结合原始 SKILL.md 内容进一步核验功能细节和使用限制。

SKILL.md

Landing Page

When to Use

  • Creating a new landing page from scratch (product launch, feature page, waitlist).
  • Auditing an existing page for conversion rate optimization (CRO).
  • Rewriting headlines, CTAs, or hero sections.
  • Structuring page sections for a specific audience and traffic source.
  • Generating A/B test variants for copy or layout changes.

Context Required

  • From startup-context: product description, ICP (ideal customer profile), value proposition, competitive positioning, stage, tone of voice.
  • From the user: page URL or current copy (if auditing), page type (homepage, landing page, pricing, feature, blog), primary conversion goal (signup, demo, purchase, subscribe, download), traffic source (organic, paid, email, social), any existing conversion data or user research.

Workflow

  1. Identify page type and conversion goal -- Every page gets one primary conversion action. Determine whether this is a homepage, landing page, pricing page, feature page, or blog post -- each has a different CRO framework.
  2. Assess value proposition clarity -- Can a visitor understand what this is and why they should care within 5 seconds? Check whether copy is benefit-focused (good) or feature-focused (common problem). Ensure it is written in the customer's language, not company jargon.
  3. Evaluate headline effectiveness -- Does the headline communicate the core value proposition? Is it specific enough to be meaningful? Does it match the traffic source's messaging? Apply headline patterns:

- Outcome-focused: "Get [desired outcome] without [pain point]" - Specificity: Include numbers, timeframes, or concrete results - Social proof: "Join [N] teams who [achieve outcome]" - Direct address: "You [do painful thing]. There's a better way."

  1. Audit CTA placement, copy, and hierarchy -- Is there one clear primary action visible without scrolling? Does button copy communicate value, not just action? ("Start my free trial" beats "Submit"). Check CTA hierarchy: primary vs. secondary, repeated at key decision points.
  2. Check visual hierarchy and scannability -- Can someone scanning the page get the main message? Are the most important elements visually prominent? Is there sufficient whitespace? Do images support or distract from the message?
  3. Evaluate trust signals and social proof -- Look for: customer logos (especially recognizable ones), testimonials with specifics and attribution, case study snippets with real numbers, review scores, security badges. Place trust signals near CTAs and after benefit claims.
  4. Identify objection handling -- Are common objections addressed? Price/value concerns, "will this work for me?", implementation difficulty, "what if it doesn't work?" Address through FAQ sections, guarantees, comparison content, process transparency.
  5. Find friction points -- Too many form fields, unclear next steps, confusing navigation, required fields that should not be required, poor mobile experience, slow load times.

Output Format

  • If auditing: Recommendations structured as: (1) Quick Wins -- easy changes with immediate impact, (2) High-Impact Changes -- bigger efforts with significant conversion improvement, (3) Test Ideas -- hypotheses worth A/B testing. For key elements, provide 2-3 copy alternatives with rationale.
  • If drafting: Full page copy organized by section with 2-3 headline variants and CTA text options. Include layout and visual recommendations.

Frameworks & Best Practices

Page-Specific CRO

  • Homepage: Clear positioning for cold visitors, quick path to primary conversion, handle both "ready to buy" and "still researching" visitors.
  • Landing page: Message-match with traffic source, single CTA (remove navigation if possible), complete argument on one page.
  • Pricing page: Clear plan comparison, recommended plan indication, address "which plan is right for me?" anxiety.
  • Feature page: Connect feature to benefit, include use cases and examples, clear path to try/buy.
  • Blog post: Contextual CTAs matching content topic, inline CTAs at natural stopping points.

Copy Principles

  • The headline is the most important element on the page. If the headline does not stop the scroll, nothing else matters. Test headlines before anything else.
  • Specificity beats cleverness. "Save 12 hours per week on reporting" outperforms "Work smarter, not harder" every time.
  • The subheadline does the heavy lifting. The headline earns attention; the subheadline explains the value. Use it to clarify who the product is for, what it does, and why it matters.
  • Awareness-level matching. Match copy depth to visitor awareness. Paid search visitors are typically solution-aware (want pricing and CTAs). Social ad visitors are typically problem-aware or unaware (need problem education first). Traffic source reveals awareness level.

Conversion Principles

  • One page, one goal. Never give the visitor two equal choices. Every element should push toward the primary CTA.
  • Above-the-fold rule. Visitor should understand what you do, who it is for, and what to do next within 5 seconds.
  • Risk reversal near final CTA. Address "what if it doesn't work?" -- free trial, money-back guarantee, or no-commitment language.
  • Social proof placement. Small proof element in hero section ("Trusted by 500+ teams"), dedicated proof section below the fold.
  • Testimonial specificity. "This product is great" is worthless. "We reduced onboarding time from 3 weeks to 2 days" is persuasive. Seek specific, outcome-driven testimonials with numbers.
  • Reduce cognitive load. Every additional choice, link, or piece of information adds friction. Cut anything that does not directly support the primary conversion.
  • Mobile-first. Over 60% of traffic is mobile. Design for thumb zones. Ensure CTAs are tappable without zooming.

Related Skills

  • content-strategy -- when the landing page needs supporting content to drive traffic
  • seo-technical -- when the landing page needs to rank organically
  • cold-outreach -- when the landing page is the destination for outbound campaigns and copy must align with email messaging

Examples

Example 1: Page audit

"Here's our landing page copy. We're getting 15k visitors/month but only 1.2% conversion. What's wrong?"

Good output: Quick wins (e.g., rewrite feature-focused headline to outcome-focused), high-impact changes (restructure page sections, add social proof to hero), and test ideas (3 headline variants, 2 CTA copy options). Each recommendation includes the specific issue, the fix, and expected impact.

Example 2: New page draft

"We're launching a waitlist page for our developer tool. Target audience is backend engineers frustrated with deployment complexity."

Good output: Full section-by-section copy. Hero headline: "Deploy to production in 3 commands, not 30 steps." Problem agitation naming the specific pain. 3-step "how it works" section. Social proof placeholder guidance. CTA: "Join 2,400 engineers on the waitlist." Two alternative headline options and layout notes.

Example 3: A/B test recommendations

"Our signup page converts at 3.5%. What should we test first?"

Good output: Priority-ordered test plan. (1) Headline -- 3 variants reframing value prop from feature-first to outcome-first. (2) CTA copy -- "Start free trial" vs. "See it in action" vs. "Get started in 2 minutes." (3) Hero trust element -- customer count or logo bar. Each test includes control, variant, hypothesis, and minimum sample size guidance.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

40.89%
按下载量换算110

Claude

28.1%
按下载量换算76

Cursor

17.39%
按下载量换算47

Gemini CLI

9.43%
按下载量换算25

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills