by 安全扫描
OpenClaw
安全
high confidenceThis is an instruction-only signup optimization skill whose requested actions and resources are consistent with its stated purpose and do not request credentials or install code.
评估建议
This skill is instruction-only and coherent for signup optimization. Before installing or enabling it, review the SKILL.md yourself and note: (1) it will read a local product marketing context file if present (.agents/product-marketing-context.md or .claude/product-marketing-context.md) — ensure that file does not contain secrets or sensitive credentials; (2) it does not require any API keys, installs, or external downloads (lower risk); (3) because the agent can invoke skills autonomously by de...详细分析 ▾
✓ 用途与能力
The name/description (signup-flow-cro) matches the instructions: guidance and audit steps for signup/registration flows. There are no unrelated env vars, binaries, or installs requested.
ℹ 指令范围
The SKILL.md instructs the agent to read a local product marketing context file if present (.agents/product-marketing-context.md or .claude/product-marketing-context.md). Reading that workspace context is reasonable for providing tailored recommendations, but it does mean the skill will look for and consume local project files if they exist. The instructions otherwise stay on-topic (form fields, UX, verification, experiments) and do not direct access to other system paths, credentials, or external endpoints.
✓ 安装机制
No install spec and no code files — instruction-only. Nothing is written to disk or downloaded by the skill itself.
✓ 凭证需求
The skill declares no required environment variables, no credentials, and no config paths beyond the optional product-marketing-context file; requested access is proportional to its purpose.
✓ 持久化与权限
always is false and default autonomy is allowed (normal for skills). The skill does not request permanent presence or modification of other skills or system-wide settings.
安全有层次，运行前请审查代码。
运行时依赖
无特殊依赖
版本
latestv1.0.02026/3/19
Initial release of the signup-flow-cro skill providing structured guidance for optimizing signup and registration flows. - Comprehensive assessment checklist covering flow type, current state, and business constraints. - Field-by-field best practices for email, password, name, social auth, company, and more. - Principles for minimizing friction, reducing required data, and showing value early. - Specific mobile optimization recommendations. - Structured output format for audits and actionable recommendations. - Experiment ideas and common flow patterns for B2B, B2C, waitlists, and e-commerce scenarios.
● 无害
安装命令
点击复制官方npx clawhub@latest install abm-signup-flow-cro
镜像加速npx clawhub@latest install abm-signup-flow-cro --registry https://cn.longxiaskill.com
技能文档
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
Check 对于 product marketing context 第一个:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, understand:
- Flow 类型
- Current State
- Business Constraints
Core Principles
1. Minimize 必填 Fields
Every field reduces conversion. For each field, ask:- 做 我们 absolutely 需要 之前 它们 可以 使用 product?
- 可以 我们 collect later 通过 progressive profiling?
- 可以 我们 infer 从 其他 data?
Typical 字段 priority:
- Essential: Email (或 phone), 密码
- Often needed: Name
- Usually deferrable: Company, 角色, Team size, Phone, Address
2. Show 值 之前 Asking 对于 Commitment
- 什么 可以 您 show/give 之前 requiring signup?
- 可以 它们 experience product 之前 creating 账户?
- Reverse order: 值 第一个, signup 第二个
3. 归约 Perceived Effort
- Show progress 如果 multi-step
- 分组 related fields
- 使用 smart defaults
- Pre-fill 当...时 possible
4. 移除 Uncertainty
- 清除 expectations ("Takes 30 seconds")
- Show 什么 happens 之后 signup
- 否 surprises (hidden requirements, unexpected steps)
字段-由-字段 Optimization
Email 字段
- Single 字段 (否 email confirmation 字段)
- Inline validation 对于 格式
- Check 对于 common typos (gmial.com → gmail.com)
- 清除 错误 messages
密码 字段
- Show 密码 切换 (eye icon)
- Show requirements upfront, 不 之后 failure
- Consider passphrase hints 对于 strength
- 更新 requirement indicators 在...中 real-时间
Better 密码 UX:
- Allow paste (don't disable)
- Show strength meter 代替 的 rigid rules
- Consider passwordless options
Name 字段
- Single "满 name" 字段 vs. 第一个/最后的 split (test )
- 仅 require 如果 immediately used (personalization)
- Consider making 可选
Social Auth Options
- Place prominently (often higher conversion 比 email)
- Show 最多 relevant options 对于 audience
- 清除 visual separation 从 email signup
- Consider "签名 up 带有 Google" 作为 primary
Phone 数字
- Defer unless essential (SMS verification, calling leads)
- 如果 必填, explain 为什么
- 使用 proper 输入框 类型 带有 country code handling
- 格式 作为 它们 类型
Company/Organization
- Defer 如果 possible
- Auto-suggest 作为 它们 类型
- Infer 从 email domain 当...时 possible
使用 Case / 角色 Questions
- Defer 到 onboarding 如果 possible
- 如果 needed 在 signup, keep 到 one question
- 使用 progressive disclosure (don't show 所有 options 在 once)
Single-Step vs. Multi-Step
Single-Step Works 当...时:
- 3 或 fewer fields
- Simple B2C products
- High-intent visitors (从 ads, waitlist)
Multi-Step Works 当...时:
- 更多 比 3-4 fields needed
- Complex B2B products needing segmentation
- 您 需要 到 collect 不同 types 的 info
Multi-Step Best Practices
- Show progress indicator
- Lead 带有 easy questions (name, email)
- Put harder questions later (之后 psychological commitment)
- 每个 step 应该 feel completable 在...中 seconds
- Allow back 导航
- 保存 progress (don't lose data 在...上 刷新)
Progressive commitment pattern:
- Email 仅 (lowest barrier)
- 密码 + name
- Customization questions (可选)
Trust 和 Friction Reduction
在 表单 Level
- "否 credit card 必填" (如果 真)
- "Free forever" 或 "14-day free trial"
- Privacy note: "我们'll never 分享 email"
- Security badges 如果 relevant
- Testimonial near signup 表单
错误 Handling
- Inline validation (不 只是 在...上 submit)
- Specific 错误 messages ("Email 已经 registered" + recovery path)
- Don't 清除 表单 在...上 错误
- Focus 在...上 problem 字段
Microcopy
- Placeholder text: 使用 对于 examples, 不 labels
- Labels: Keep visible (不 只是 placeholders) — placeholders disappear 当...时 typing, leaving users unsure 什么 它们're filling 在...中
- Help text: 仅 当...时 needed, placed 关闭 到 字段
Mobile Signup Optimization
- Larger touch targets (44px+ height)
- Appropriate keyboard types (email, tel, etc.)
- Autofill support
- 归约 typing (social auth, pre-fill)
- Single 列 布局
- Sticky CTA 按钮
- Test 带有 actual devices
Post-Submit Experience
成功 State
- 清除 confirmation
- Immediate 下一个 step
- 如果 email verification 必填:
Verification Flows
- Consider delaying verification until necessary
- Magic 链接 作为 alternative 到 密码
- 让 users explore 当...时 awaiting verification
- 清除 re-engagement 如果 verification stalls
Measurement
键 Metrics
- 表单 开始 rate (landed → started filling)
- 表单 completion rate (started → submitted)
- 字段-level drop-off (哪个 fields lose people)
- 时间 到 complete
- 错误 rate 由 字段
- Mobile vs. desktop completion
什么 到 Track
- 每个 字段 interaction (focus, blur, 错误)
- Step progression 在...中 multi-step
- Social auth vs. email signup ratio
- 时间 之间 steps
输出 格式
Audit Findings
For each issue found:- Issue: 什么's wrong
- Impact: 为什么 matters (带有 estimated impact 如果 possible)
- Fix: Specific recommendation
- Priority: High/Medium/Low
Recommended Changes
Organized by:- Quick wins (相同-day fixes)
- High-impact changes (week-level effort)
- Test hypotheses (things 到 /B test)
表单 Redesign (如果 requested)
- Recommended 字段 设置 带有 rationale
- 字段 order
- 复制 对于 labels, placeholders, buttons, errors
- Visual 布局 suggestions
Common Signup Flow Patterns
B2B SaaS Trial
- Email + 密码 (或 Google auth)
- Name + Company (可选: 角色)
- → Onboarding flow
B2C App
- Google/Apple auth 或 Email
- → Product experience
- 个人资料 completion later
Waitlist/Early Access
- Email 仅
- 可选: 角色/使用 case question
- → Waitlist confirmation
E-commerce 账户
- 访客 checkout 作为 默认
- 账户 creation 可选 post-purchase
- 或 Social auth 带有 single click
Experiment Ideas
表单 Design Experiments
布局 & Structure
- Single-step vs. multi-step signup flow
- Multi-step 带有 progress bar vs. 没有
- 1-列 vs. 2-列 字段 布局
- 表单 embedded 在...上 page vs. separate signup page
- Horizontal vs. vertical 字段 alignment
字段 Optimization
- 归约 到 minimum fields (email + 密码 仅)
- 添加 或 移除 phone 数字 字段
- Single "Name" 字段 vs. "第一个/最后的" split
- 添加 或 移除 company/organization 字段
- Test 必填 vs. 可选 字段 balance
Authentication Options
- 添加 SSO options (Google, Microsoft, GitHub, LinkedIn)
- SSO prominent vs. email 表单 prominent
- Test 哪个 SSO options resonate (varies 由 audience)
- SSO-仅 vs. SSO + email 选项
Visual Design
- Test 按钮 colors 和 sizes 对于 CTA prominence
- Plain background vs. product-related visuals
- Test 表单 container styling (card vs. minimal)
- Mobile-optimized 布局 testing
复制 & Messaging Experiments
Headlines & CTAs
- Test headline variations 上面 signup 表单
- CTA 按钮 text: "创建 账户" vs. "开始 Free Trial" vs. "获取 Started"
- 添加 clarity 周围 trial length 在...中 CTA
- Test 值 proposition emphasis 在...中 表单 页头
Microcopy
- 字段 labels: minimal vs. descriptive
- Placeholder text optimization
- 错误 消息 clarity 和 tone
- 密码 requirement display (upfront vs. 在...上 错误)
Trust Elements
- 添加 social proof 下一个 到 signup 表单
- Test trust badges near 表单 (security, compliance)
- 添加 "否 credit card 必填" messaging
- Include privacy assurance 复制
Trial & Commitment Experiments
Free Trial Variations
- Credit card 必填 vs. 不 必填 对于 trial
- Test trial length impact (7 vs. 14 vs. 30 days)
- Freemium vs. free trial 模型
- Trial 带有 limited features vs. 满 access
Friction Points
- Email verification 必填 vs. delayed vs. removed
- Test CAPTCHA impact 在...上 completion
- Terms acceptance checkbox vs. implicit acceptance
- Phone verification 对于 high-值 accounts
Post-Submit Experiments
- 清除 下一个 steps messaging 之后 signup
- Instant product access vs. email confirmation 第一个
- Personalized welcome 消息 based 在...上 signup data
- Auto-登录 之后 signup vs. require 登录
Task-Specific Questions
- 什么's current signup completion rate?
- 做 您 有 字段-level analytics 在...上 drop-off?
- 什么 data absolutely 必填 之前 它们 可以 使用 product?
- 那里 compliance 或 verification requirements?
- 什么 happens immediately 之后 signup?
Related Skills
- onboarding-cro: 对于 optimizing 什么 happens 之后 signup
- 表单-cro: 对于 non-signup forms (lead capture, contact)
- page-cro: 对于 landing page leading 到 signup
- ab-test-setup: 对于 testing signup flow changes