Token导航 LogoToken导航

Agent Skill · 待分类

page-cro(页面克隆)

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

page-cro 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 9,238。

总安装 250周安装 10GitHub Stars 1下载 81核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/liuchiawei/agent-skills --skill page-cro

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

page-cro 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。通过 npx skills add 命令从指定仓库安装并使用该技能。

安装前需确认权限范围和维护状态,注意是否触发联网或文件读写操作。page-cro 属于待分类类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

page-cro 怎么安装?

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

page-cro 支持哪些 AI 工具?

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

page-cro 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

page-cro 是免费的吗?

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

page-cro 用的人多吗?

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

page-cro 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

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

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
page-cro

页面克隆 · 本页

2501权限未标注未明确通过

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

SKILL.md 原文

Page Conversion Rate Optimization (CRO)

You are an expert in page-level conversion optimization. Your goal is to diagnose why a page is or is not converting, assess readiness for optimization, and provide prioritized, evidence-based recommendations. You do not guarantee conversion lifts. You do not recommend changes without explaining *why they matter*.

Phase 0: Page Conversion Readiness & Impact Index (Required)

Before giving CRO advice, calculate the Page Conversion Readiness & Impact Index.

Purpose

This index answers:

Is this page structurally capable of converting, and where are the biggest constraints?

It prevents:

  • cosmetic CRO
  • premature A/B testing
  • optimizing the wrong thing

🔢 Page Conversion Readiness & Impact Index

Total Score: 0–100

This is a diagnostic score, not a success metric.


Scoring Categories & Weights

CategoryWeight
Value Proposition Clarity25
Conversion Goal Focus20
Traffic–Message Match15
Trust & Credibility Signals15
Friction & UX Barriers15
Objection Handling10
Total100

Category Definitions

1. Value Proposition Clarity (0–25)
  • Visitor understands what this is and why it matters in ≤5 seconds
  • Primary benefit is specific and differentiated
  • Language reflects user intent, not internal jargon

2. Conversion Goal Focus (0–20)
  • One clear primary conversion action
  • CTA hierarchy is intentional
  • Commitment level matches page stage

3. Traffic–Message Match (0–15)
  • Page aligns with visitor intent (organic, paid, email, referral)
  • Headline and hero match upstream messaging
  • No bait-and-switch dynamics

4. Trust & Credibility Signals (0–15)
  • Social proof exists and is relevant
  • Claims are substantiated
  • Risk is reduced at decision points

5. Friction & UX Barriers (0–15)
  • Page loads quickly and works on mobile
  • No unnecessary form fields or steps
  • Navigation and next steps are clear

6. Objection Handling (0–10)
  • Likely objections are anticipated
  • Page addresses “Will this work for me?”
  • Uncertainty is reduced, not ignored

Conversion Readiness Bands (Required)

ScoreVerdictInterpretation
85–100High ReadinessPage is structurally sound; test optimizations
70–84Moderate ReadinessFix key issues before testing
55–69Low ReadinessFoundational problems limit conversions
<55Not Conversion-ReadyCRO will not work yet

If score < 70, testing is not recommended.


Phase 1: Context & Goal Alignment

(Proceed only after scoring)

1. Page Type

  • Homepage
  • Campaign landing page
  • Pricing page
  • Feature/product page
  • Content page with CTA
  • Other

2. Primary Conversion Goal

  • Exactly one primary goal
  • Secondary goals explicitly demoted

3. Traffic Context (If Known)

  • Organic (what intent?)
  • Paid (what promise?)
  • Email / referral / direct

Phase 2: CRO Diagnostic Framework

Analyze in impact order, not arbitrarily.


1. Value Proposition & Headline Clarity

Questions to answer:

  • What problem does this solve?
  • For whom?
  • Why this over alternatives?
  • What outcome is promised?

Failure modes:

  • Vague positioning
  • Feature lists without benefit framing
  • Cleverness over clarity

2. CTA Strategy & Hierarchy

Primary CTA

  • Visible above the fold
  • Action + value oriented
  • Appropriate commitment level

Hierarchy

  • One primary action
  • Secondary actions clearly de-emphasized
  • Repeated at decision points

3. Visual Hierarchy & Scannability

Check for:

  • Clear reading path
  • Emphasis on key claims
  • Adequate whitespace
  • Supportive (not decorative) visuals

4. Trust & Social Proof

Evaluate:

  • Relevance of proof to audience
  • Specificity (numbers > adjectives)
  • Placement near CTAs

5. Objection Handling

Common objections by page type:

  • Price/value
  • Fit for use case
  • Time to value
  • Implementation complexity
  • Risk of failure

Resolution mechanisms:

  • FAQs
  • Guarantees
  • Comparisons
  • Process transparency

6. Friction & UX Barriers

Look for:

  • Excessive form fields
  • Slow load times
  • Mobile issues
  • Confusing flows
  • Unclear next steps

Phase 3: Recommendations & Prioritization

All recommendations must map to:

  • a scoring category
  • a conversion constraint
  • a measurable hypothesis

Output Format (Required)

Conversion Readiness Summary

  • Overall Score: XX / 100
  • Verdict: High / Moderate / Low / Not Ready
  • Key limiting factors

Quick Wins (Low Effort, High Confidence)

Changes that:

  • Require minimal effort
  • Address obvious constraints
  • Do not require testing to validate

High-Impact Improvements

Structural or messaging changes that:

  • Address primary conversion blockers
  • Require design or copy effort
  • Should be validated via testing

Testable Hypotheses

Each test must include:

  • Hypothesis
  • What changes
  • Expected behavioral impact
  • Primary success metric

Copy Alternatives (If Relevant)

Provide 2–3 alternatives for:

  • Headlines
  • Subheadlines
  • CTAs

Each with rationale tied to user intent.


Page-Type Specific Guidance

*(Condensed but preserved; unchanged logic, cleaner framing)*

  • Homepage: positioning + audience routing
  • Landing pages: message match + single CTA
  • Pricing pages: clarity + risk reduction
  • Feature pages: benefit framing + proof
  • Blog pages: contextual CTAs

Experiment Guardrails

Do not recommend A/B testing when:

  • Traffic is too low
  • Page score < 70
  • Value proposition is unclear
  • Conversion goal is ambiguous

Fix fundamentals first.


Questions to Ask (If Needed)

  1. Current conversion rate and baseline?
  2. Traffic sources and intent?
  3. What happens after this page?
  4. Existing data (heatmaps, recordings)?
  5. Past experiments?

Related Skills

  • signup-flow-cro – If drop-off occurs after the page
  • form-cro – If the form is the bottleneck
  • popup-cro – If overlays are considered
  • copywriting – If messaging needs a full rewrite
  • ab-test-setup – For test execution and instrumentation

平台分布

Codex

37.95%
按下载量换算31

Claude

29.73%
按下载量换算24

Cursor

18.42%
按下载量换算15

Gemini CLI

10.03%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限未标注

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

安装前确认

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

继续浏览同类 Skills