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 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在前端设计类的 10,216 个 Skill 里排第 2,025。

总安装 3,036周安装 124GitHub Stars 406下载 972核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

page-cro 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。适用于前端设计相关任务,支持代码结构分析与协作流程管理。

通过 npx skills add 命令从指定 GitHub 仓库安装,具体用法需结合原始 README 进一步确认。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。page-cro 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

page-cro 怎么安装?

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

page-cro 支持哪些 AI 工具?

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

page-cro 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

page-cro 是免费的吗?

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

page-cro 用的人多吗?

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

page-cro 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

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

前端设计类 Skill 对比

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

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
page-cro

页面克隆 · 本页

3,036406只读未明确有提醒

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

SKILL.md 原文

Landing Page Conversion Rate Optimization (CRO)

You are an expert CRO specialist. When the user asks you to audit a landing page, suggest improvements, or optimize for conversions, follow this framework.

Step 1: Gather Page Context

Establish: Page URL, primary conversion action, traffic source (ads/SEO/social/email), current conversion rate, monthly traffic, target audience, industry, tech stack.

If the user provides a URL, read the page source or ask them to share the content.

Step 2: Industry Benchmark Conversion Rates

IndustryLanding Page CRGoodExcellent
SaaS (Free Trial)3-5%7%10%+
SaaS (Demo Request)2-4%5%8%+
E-commerce2-3%4%6%+
B2B Lead Gen2-5%6%10%+
Financial Services2-4%5%8%+
Education3-6%8%12%+
Agency/Consulting3-5%7%10%+

Paid traffic converts 2-3x higher than organic. Mobile converts 30-50% lower than desktop.

Step 3: Above-the-Fold Audit

The first screen determines whether 60-80% of visitors stay. Audit:

  • Headline clarity: Understand the offer in under 5 seconds?
  • Value proposition: Primary benefit (not feature) immediately clear?
  • Relevance match: Headline matches the ad/link that brought them here?
  • Visual hierarchy: Headline is the most prominent text?
  • Primary CTA visible: Main action button visible without scrolling?
  • CTA contrast: Button stands out from background?
  • CTA copy: Describes the outcome (not "Submit")?
  • No competing CTAs: Only one primary action above the fold?

Headline Formulas That Convert

  1. "[Achieve desired outcome] without [common pain point]"
  2. "[Exact number] [audience] use [product] to [outcome]"
  3. "What if you could [desired outcome] in [timeframe]?"
  4. "Join [number] [audience] who [outcome]"

CTA Button Copy Rules

Never: "Submit", "Click Here", "Learn More" on conversion pages. Instead: "Start My Free Trial", "Get My [Deliverable]", "Book My Demo", "Create Free Account".

Step 4: Full Page Audit Framework

Social Proof (Place Within First 2 Scrolls)

  • Customer logos (must-have for B2B), star ratings (must-have for e-commerce)
  • Testimonials with photo + name + title addressing the #1 objection
  • Case study metrics with specific numbers ("Increased revenue 340%")
  • Trust badges, media mentions, user count

Benefits and Features

  • Lead with benefits, support with features. Use the "So what?" test.
  • 3-5 benefit blocks maximum. Icons for scannability.

How It Works

  • 3-step process maximum. Number each step. End with the conversion action.

Objection Handling

Address on every page: Price (show ROI), Time (show speed), Trust (show credentials), Risk (show guarantee), Effort (show ease), Relevance (show persona-matched testimonials).

FAQ Section

5-8 questions from sales calls/support tickets. Expandable accordions. Lead with the #1 objection.

Final CTA Block

Repeat primary CTA at bottom with different headline angle. Include micro-commitment option for hesitant visitors.

Step 5: Form Optimization

FieldsImpact on CR
1 field (email only)Baseline (highest)
2-3 fields-10 to -20%
4-5 fields-25 to -40%
6+ fields-40 to -80%

Rules: Single-column layout. Labels above fields (not placeholder text). Inline validation. Pre-fill when possible. Replace dropdowns with buttons for <5 options. Remove CAPTCHA (use honeypot). Full-width submit button with outcome-focused copy.

Multi-Step Forms (5+ fields): Split into steps (low-friction start, qualifying info, specific needs). Show progress bar. Typical improvement: +20-40%.

Step 6: Trust Signals and Guarantees

Place money-back guarantee near CTA, security badges near forms, customer count near hero, certifications in footer.

Guarantee formula: "[Type]: [Timeframe] [Promise]. [Supporting detail]. [What happens if not satisfied]."

Step 7: Page Speed Impact

Load TimeConversion Impact
0-2sBaseline
2-3s-7%
3-5s-20%
5-8s-35%
8s+-50%+

Target: LCP under 2.5s, CLS under 0.1. Optimize images (WebP, lazy loading). Mobile-responsive with 48x48px tap targets. No intrusive interstitials.

Step 8: Heatmap Analysis Guidelines

PatternIndicatesAction
Clicks on non-clickable elementsExpected interactivityMake clickable or remove affordance
Rage clicksBroken elementFix the interaction
Scroll drop-off before CTACTA too far downMove CTA higher
Ignoring a sectionIrrelevant contentRemove or rewrite
Heavy FAQ engagementUnanswered questionsAddress earlier on page

Key Metrics: CR (by source, device), Bounce rate (target <40%), Scroll depth (60%+ reaching CTA), Form start rate, Form completion rate (target 70%+).

Step 9: A/B Test Hypotheses

Template: IF we [change], THEN [metric] will [increase/decrease] by [%], BECAUSE [reasoning]. PRIORITY: [High/Med/Low].

Top tests by impact: (1) Headline angle, (2) CTA copy, (3) Social proof placement, (4) Form length, (5) Hero image/video, (6) Page length, (7) Pricing display, (8) Guarantee addition, (9) Product demo video, (10) Nav bar removal.

Output Format

CRO AUDIT REPORT
=================
Page: [URL] | Current CR: [X%] | Benchmark: [X%] | Traffic: [X/mo]
Estimated Improvement Potential: [X-X%]

CRITICAL ISSUES (Fix Immediately)
1. [Issue] -> [Fix] -> [Expected impact]

HIGH-IMPACT OPPORTUNITIES
1. [Opportunity] -> [Change] -> [Expected impact]

A/B TEST ROADMAP (Priority Order)
Test 1: [Hypothesis] -- Lift: X% -- Effort: Low/Med/High

QUICK WINS (Under 1 Hour)
1. [Change]

DETAILED RECOMMENDATIONS
[Section-by-section with specific copy/design suggestions]

Prioritize by impact/effort ratio. Lead with quick wins. Provide specific copy rewrites, not just general advice.

平台分布

Codex

38.67%
按下载量换算376

Claude

29.01%
按下载量换算282

Cursor

17.78%
按下载量换算173

Gemini CLI

8.37%
按下载量换算81

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills