Token导航 LogoToken导航

Agent Skill · 研究检索

page-cro(页面克隆)

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

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

总安装 238周安装 10GitHub Stars 937下载 83核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/freekmurze/dotfiles --skill page-cro

这个 Skill 是做什么的

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

page-cro 技能用于网页页面的转化率优化方案检索与分析。适合电商、内容平台等需要提升页面效果的业务场景。通过 npx skills add 命令从 dotfiles 仓库便捷部署。注意区分通用建议与具体实施细节,避免盲目套用。page-cro 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

page-cro 怎么安装?

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

page-cro 支持哪些 AI 工具?

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

page-cro 需要什么权限?

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

page-cro 是免费的吗?

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

page-cro 用的人多吗?

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

page-cro 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 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

页面克隆 · 本页

238937需要联网未明确通过

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

SKILL.md 原文

Page Conversion Rate Optimization (CRO)

You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.

Initial Assessment

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before providing recommendations, identify:

  1. Page Type: Homepage, landing page, pricing, feature, blog, about, other
  2. Primary Conversion Goal: Sign up, request demo, purchase, subscribe, download, contact sales
  3. Traffic Context: Where are visitors coming from? (organic, paid, email, social)

CRO Analysis Framework

Analyze the page across these dimensions, in order of impact:

1. Value Proposition Clarity (Highest Impact)

Check for:

  • Can a visitor understand what this is and why they should care within 5 seconds?
  • Is the primary benefit clear, specific, and differentiated?
  • Is it written in the customer's language (not company jargon)?

Common issues:

  • Feature-focused instead of benefit-focused
  • Too vague or too clever (sacrificing clarity)
  • Trying to say everything instead of the most important thing

2. Headline Effectiveness

Evaluate:

  • Does it communicate the core value proposition?
  • Is it specific enough to be meaningful?
  • Does it match the traffic source's messaging?

Strong headline patterns:

  • Outcome-focused: "Get [desired outcome] without [pain point]"
  • Specificity: Include numbers, timeframes, or concrete details
  • Social proof: "Join 10,000+ teams who..."

3. CTA Placement, Copy, and Hierarchy

Primary CTA assessment:

  • Is there one clear primary action?
  • Is it visible without scrolling?
  • Does the button copy communicate value, not just action?

- Weak: "Submit," "Sign Up," "Learn More" - Strong: "Start Free Trial," "Get My Report," "See Pricing"

CTA hierarchy:

  • Is there a logical primary vs. secondary CTA structure?
  • Are CTAs repeated at key decision points?

4. Visual Hierarchy and Scannability

Check:

  • Can someone scanning get the main message?
  • Are the most important elements visually prominent?
  • Is there enough white space?
  • Do images support or distract from the message?

5. Trust Signals and Social Proof

Types to look for:

  • Customer logos (especially recognizable ones)
  • Testimonials (specific, attributed, with photos)
  • Case study snippets with real numbers
  • Review scores and counts
  • Security badges (where relevant)

Placement: Near CTAs and after benefit claims

6. Objection Handling

Common objections to address:

  • Price/value concerns
  • "Will this work for my situation?"
  • Implementation difficulty
  • "What if it doesn't work?"

Address through: FAQ sections, guarantees, comparison content, process transparency

7. Friction Points

Look for:

  • Too many form fields
  • Unclear next steps
  • Confusing navigation
  • Required information that shouldn't be required
  • Mobile experience issues
  • Long load times

Output Format

Structure your recommendations as:

Quick Wins (Implement Now)

Easy changes with likely immediate impact.

High-Impact Changes (Prioritize)

Bigger changes that require more effort but will significantly improve conversions.

Test Ideas

Hypotheses worth A/B testing rather than assuming.

Copy Alternatives

For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.


Page-Specific Frameworks

Homepage CRO

  • Clear positioning for cold visitors
  • Quick path to most common conversion
  • Handle both "ready to buy" and "still researching"

Landing Page CRO

  • Message match with traffic source
  • Single CTA (remove navigation if possible)
  • Complete argument on one page

Pricing Page CRO

  • Clear plan comparison
  • Recommended plan indication
  • Address "which plan is right for me?" anxiety

Feature Page CRO

  • Connect feature to benefit
  • Use cases and examples
  • Clear path to try/buy

Blog Post CRO

  • Contextual CTAs matching content topic
  • Inline CTAs at natural stopping points

Experiment Ideas

When recommending experiments, consider tests for:

  • Hero section (headline, visual, CTA)
  • Trust signals and social proof placement
  • Pricing presentation
  • Form optimization
  • Navigation and UX

For comprehensive experiment ideas by page type: See references/experiments.md


Task-Specific Questions

  1. What's your current conversion rate and goal?
  2. Where is traffic coming from?
  3. What does your signup/purchase flow look like after this page?
  4. Do you have user research, heatmaps, or session recordings?
  5. What have you already tried?

Related Skills

  • signup-flow-cro: If the issue is in the signup process itself
  • form-cro: If forms on the page need optimization
  • popup-cro: If considering popups as part of the strategy
  • copywriting: If the page needs a complete copy rewrite
  • ab-test-setup: To properly test recommended changes

平台分布

Codex

37.42%
按下载量换算31

Claude

27.88%
按下载量换算23

Cursor

18.11%
按下载量换算15

Gemini CLI

8.13%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills