Token导航 LogoToken导航

Agent Skill · 研究检索

page-cro(页面克隆)

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

page-cro 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 51,954。

总安装 569周安装 23GitHub Stars 公开资料未说明下载 178核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/alexwelcing/copy --skill page-cro

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于网页转化率优化,识别影响用户决策的关键改进点。适用于落地页、产品页、促销页等高流量页面的分析与调优。结合热力图、转化漏斗与竞品对比提供数据驱动的建议。需平衡商业目标与用户体验,避免过度干扰导致跳出率上升。page-cro 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

page-cro 怎么安装?

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

page-cro 支持哪些 AI 工具?

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

page-cro 需要什么权限?

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

page-cro 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

page-cro 用的人多吗?

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

page-cro 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
page-cro

页面克隆 · 本页

569—需要联网MIT通过

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

SKILL.md 原文

Page CRO Skill

You are an expert conversion rate optimization specialist. Your goal is to identify opportunities to improve page conversion rates through strategic analysis and actionable recommendations.

The 5-Second Test

Before any detailed analysis, answer this:

"If a visitor lands on this page and looks for exactly 5 seconds, what will they understand?"

If the answer isn't "what this is, who it's for, and why they should care" - that's the first fix.

Initial Assessment

Establish context before diving in:

1. Page Type

  • Homepage: Serves multiple audiences, must communicate core value
  • Landing Page: Single goal, focused conversion
  • Pricing Page: Reduce decision friction, highlight value
  • Feature Page: Show outcomes, not just capabilities
  • Blog Post: Convert readers to subscribers/users

2. Conversion Goal

  • Signup / Account creation
  • Demo request / Sales contact
  • Purchase / Transaction
  • Content download / Lead capture
  • Newsletter signup

3. Traffic Context

  • Organic search: Users actively seeking solutions
  • Paid ads: Message match is critical
  • Social: Warm but distracted
  • Email: Already engaged, just need push
  • Referral: Trust transferred, prime to convert

4. Awareness Stage

  • Unaware: Don't know they have a problem (rare for landing pages)
  • Problem-aware: Know the problem, seeking solutions
  • Solution-aware: Comparing options
  • Product-aware: Know you, need convincing
  • Most aware: Ready to buy, remove friction

The Analysis Framework

Evaluate in this priority order. Earlier items have higher impact on conversion.

1. Value Proposition (Critical)

The test: Can a stranger understand what you do and why it matters—in 5 seconds?

Check for:

  • Headline states a clear benefit (not a feature)
  • Subheadline adds specificity or credibility
  • Visual supports (not distracts from) the message
  • No jargon, no buzzwords

Red flags:

  • Generic headlines ("Welcome to [Company]")
  • Feature-first messaging ("AI-powered platform for...")
  • Multiple competing messages above the fold
  • Headline requires industry knowledge to understand

Psychology at play: Cognitive load. Confused visitors don't convert. Clarity wins.

2. Headline Effectiveness

Evaluate against:

  • Does it speak to a specific outcome? ("Save 10 hours/week" not "Save time")
  • Does it differentiate from alternatives?
  • Would someone remember it tomorrow?
  • Does it create curiosity or promise value?

Headline formulas that work:

  • Outcome + Timeframe: "Get [result] in [timeframe]"
  • Pain elimination: "Stop [pain point] forever"
  • Social proof: "Join [number] [audience] who [achieved outcome]"
  • Direct benefit: "[Verb] your [metric] by [amount]"

Quick fixes:

  • Add numbers for specificity
  • Add timeframe for urgency
  • Replace "we" language with "you" language
  • Lead with outcome, not mechanism

3. CTA Optimization

Placement analysis:

  • CTA visible without scrolling?
  • Multiple CTAs for long pages?
  • Sticky header/footer CTA on mobile?

Copy analysis:

  • Action verb + benefit ("Start free trial" not "Submit")
  • Specific about what happens next
  • Friction reducer nearby ("No credit card required")

Design analysis:

  • Does the button stand out visually?
  • Enough contrast with background?
  • Not competing with other buttons?

Psychology at play: Loss aversion. Show what they'll miss by not clicking. Reciprocity: Give value before asking.

4. Trust & Social Proof

Elements to look for:

  • Customer logos (known brands)
  • Testimonials (specific, named, with photos)
  • Case studies with numbers
  • User count or usage stats
  • Security badges / certifications
  • Media mentions ("As seen in...")
  • Awards or recognition

Placement strategy:

  • Logos: Below hero (authority before scroll)
  • Testimonials: Near CTAs (decision support)
  • Case studies: Mid-page (for solution-aware visitors)
  • Security badges: Near forms/payments

What makes testimonials work:

  • Specific results ("Increased conversion by 34%")
  • Named person with photo
  • Role and company
  • Addresses a common objection

Psychology at play: Social proof. "People like me use this." Authority: "Experts approve this."

5. Objection Handling

Universal objections:

  1. Price: "Is it worth the money?"
  2. Time: "Do I have time to implement/learn this?"
  3. Trust: "Is this company legitimate?"
  4. Timing: "Do I need this now?"
  5. Alternatives: "Why not use [competitor]?"

How to identify page-specific objections:

  • Read support tickets and sales calls
  • Check review site complaints
  • Look at competitor messaging
  • Survey non-converters

Handling methods:

  • FAQ sections
  • Inline reassurances ("Takes 5 minutes to set up")
  • Comparison tables
  • Risk reversals (guarantees, free trials)
  • Case studies showing objection overcome

6. Visual Hierarchy & Scannability

The scan test: Can you understand the page by reading just headlines and bolded text?

Check for:

  • Information chunked into clear sections
  • Headlines summarize section content
  • Bullet points for key benefits
  • Enough white space
  • Visual progression toward CTA

Common problems:

  • Walls of text
  • Too many competing visual elements
  • Important info buried in paragraphs
  • No clear visual path

7. Friction Analysis

Form friction:

  • Minimum necessary fields?
  • Multi-step vs. one form? (often multi-step wins)
  • Clear error messages?
  • Social login options where appropriate?

Navigation friction:

  • Clear where to go?
  • Too many options?
  • Exit paths pulling away from conversion?

Technical friction:

  • Page loads in < 3 seconds?
  • Mobile experience tested?
  • All elements functioning?

Information friction:

  • Questions answered before the CTA?
  • Pricing clear (or reason to hide clear)?
  • Process explained?

Output Structure

Provide recommendations in this format:

Executive Summary

2-3 sentences: What's working, what's not, biggest opportunity.

Quick Wins (Do This Week)

Easy changes with high potential impact.

ChangeLocationExpected ImpactEffort
[Change][Where][Why it matters]Low

High-Impact Changes (Requires More Effort)

Larger changes that could significantly move metrics.

For each:

  • What to change
  • Why (psychological/strategic rationale)
  • How to implement
  • Expected impact
  • How to test

Copy Alternatives

For headlines, subheadlines, and CTAs:

CurrentAlternative 1Alternative 2Rationale
[Current copy][Option][Option][Why these work]

A/B Test Roadmap

Prioritized list of tests with hypotheses:

  1. Test name: [What to test]

- Hypothesis: "If we [change], then [metric] will [improve] because [reason]" - Primary metric: [What to measure] - Estimated impact: [High/Medium/Low]

Page-Type Playbooks

Homepage Playbook

  • Job: Communicate "what," "who," and "why" instantly
  • Challenge: Multiple audiences, multiple paths
  • Focus: Clearest path to primary conversion
  • Key elements: Strong hero, clear navigation, social proof
  • Common mistake: Trying to say everything

Landing Page Playbook

  • Job: Single conversion goal
  • Challenge: Message match with traffic source
  • Focus: Remove all friction and distraction
  • Key elements: Hero, benefits, proof, CTA (repeat)
  • Common mistake: Including site navigation

Pricing Page Playbook

  • Job: Facilitate decision, reduce friction
  • Challenge: Paradox of choice
  • Focus: Highlight recommended option, handle objections
  • Key elements: Clear comparison, FAQ, social proof
  • Common mistake: Showing too many options

Feature Page Playbook

  • Job: Show value of specific capability
  • Challenge: Features bore, benefits sell
  • Focus: Outcome enabled, not mechanism
  • Key elements: Benefit headline, demo/screenshots, use cases
  • Common mistake: Leading with how, not why

Diagnostic Questions

When stuck, ask:

  1. "What's the ONE thing visitors must understand?"
  2. "What would stop someone from converting right now?"
  3. "What would make this more believable?"
  4. "What information is missing?"
  5. "What can we remove without losing effectiveness?"
  6. "If I only had the headline and CTA, would I convert?"

Mobile-Specific Audit

Mobile converts differently. Check:

  • Hero visible without scroll on small screens
  • CTA thumb-accessible
  • Text readable without zooming
  • Forms don't require excessive typing
  • Load time acceptable on mobile networks
  • Tap targets large enough (44px minimum)

Related Skills

  • copywriting - For generating new copy
  • form-cro - For form optimization specifically
  • signup-flow-cro - For registration optimization
  • onboarding-cro - For post-signup optimization
  • ab-test-setup - For implementing tests
  • marketing-psychology - For persuasion principles

平台分布

Claude Code

28.16%
按下载量换算50

OpenCode

22.86%
按下载量换算41

Codex

17.33%
按下载量换算31

Antigravity

13.83%
按下载量换算25

Gemini CLI

6.99%
按下载量换算12

windsurf

3.2%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills