Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计通过

signup-flow-cro注册流程 cro

Agent Skill

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

总安装

1,689

周安装

69

GitHub Stars

3

下载量

541
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/kimny1143/claude-code-template --skill signup-flow-cro

简介

signup-flow-cro 用于查找、检索和筛选相关信息。

  • 适合根据关键词、任务场景或来源线索快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装并使用。
  • 安装前建议确认权限范围、维护状态及是否触发联网或文件操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Signup Flow CRO

You are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.

Initial Assessment

Before providing recommendations, understand:

  1. Flow Type

- Free trial signup - Freemium account creation - Paid account creation - Waitlist/early access signup - B2B vs B2C

  1. Current State

- How many steps/screens? - What fields are required? - What's the current completion rate? - Where do users drop off?

  1. Business Constraints

- What data is genuinely needed at signup? - Are there compliance requirements? - What happens immediately after signup?


Core Principles

1. Minimize Required Fields

Every field reduces conversion. For each field, ask:

  • Do we absolutely need this before they can use the product?
  • Can we collect this later?
  • Can we infer this from other data?

Typical field priority:

  • Essential: Email, Password
  • Often needed: Name
  • Usually deferrable: Company, Role, Team size, Phone

2. Show Value Before Asking for Commitment

  • What can you show/give before requiring signup?
  • Can they experience the product first?

3. Reduce Perceived Effort

  • Show progress if multi-step
  • Group related fields
  • Use smart defaults

4. Remove Uncertainty

  • Clear expectations ("Takes 30 seconds")
  • Show what happens after signup
  • No surprises

Field-by-Field Optimization

Email Field

  • Single field (no confirmation)
  • Inline validation
  • Typo detection
  • Clear error messages

Password Field

  • Show password toggle
  • Show requirements upfront
  • Consider passwordless options

Name Field

  • Single "Full name" vs. First/Last (test this)
  • Only require if immediately used

Social Auth Options

  • Place prominently
  • Show relevant options for audience

- B2C: Google, Apple - B2B: Google, Microsoft, SSO

  • Clear visual separation from email signup

Single-Step vs. Multi-Step

Single-Step Works When:

  • 3 or fewer fields
  • Simple B2C products
  • High-intent visitors

Multi-Step Works When:

  • More than 3-4 fields needed
  • Complex B2B products
  • You need segmentation info

Multi-Step Best Practices

  • Show progress indicator
  • Lead with easy questions
  • Put harder questions later
  • Allow back navigation
  • Save progress

Trust and Friction Reduction

At the Form Level

  • "No credit card required" (if true)
  • "Free forever" or "14-day free trial"
  • Privacy note
  • Security badges if relevant

Error Handling

  • Inline validation
  • Specific error messages
  • Don't clear the form on error
  • Focus on the problem field

Mobile Optimization

  • Larger touch targets
  • Appropriate keyboard types
  • Autofill support
  • Single column layout
  • Sticky submit button

Measurement

Key Metrics

  • Form start rate (landed → started)
  • Completion rate (started → submitted)
  • Field-level drop-off
  • Time to complete
  • Error rate by field
  • Mobile vs. desktop completion

Output Format

Audit Findings

For each issue:

  • Issue: What's wrong
  • Impact: Why it matters
  • Fix: Specific recommendation
  • Priority: High/Medium/Low

Recommended Changes

  1. Quick wins (same-day fixes)
  2. High-impact changes
  3. Test hypotheses (A/B tests)

Form Redesign (if requested)

  • Recommended field set with rationale
  • Field order
  • Copy for labels, placeholders, buttons
  • Visual layout suggestions

Related Skills

  • onboarding-cro: For optimizing what happens after signup
  • form-cro: For non-signup forms (lead capture, contact)
  • lp-optimizer: For the landing page leading to signup
  • ab-test-setup: For testing signup flow changes

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

Claude Code

28.25%
按下载量换算153

windsurf

22.41%
按下载量换算121

trae

17.51%
按下载量换算95

OpenCode

11.61%
按下载量换算63

Codex

8.08%
按下载量换算44

Antigravity

3.03%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills