Token导航 LogoToken导航TokenDH.com
待分类需要联网github未标认证来源可访问许可证需确认审计通过

cro-funnel克罗漏斗

Agent Skill

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

总安装

1,117

周安装

47

GitHub Stars

26

下载量

391
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/dirnbauer/webconsulting-skills --skill cro-funnel

简介

该技能优化全漏斗转化率,从页面浏览到付费转化的每个环节提供改进建议。

  • 适用于电商、SaaS 或订阅制产品,识别高流失率节点并设计 A/B 测试方案。
  • 强调表单精简、弹窗时机与 onboarding 流程优化等实操性策略。
  • 需结合业务指标定义成功标准,避免单纯追求点击率而损害用户体验。
  • cro-funnel 属于待分类类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

CRO Funnel Optimization

Source: This skill is adapted from AgentKits Marketing by AITYTech. Enterprise-grade AI marketing automation (MIT License).

Full-funnel Conversion Rate Optimization covering every stage from page visit to paid conversion:

Visitor → Page CRO → Form CRO → Signup CRO
     ↓
  Popup CRO (capture abandoners)
     ↓
New User → Onboarding CRO → Activation
     ↓
Free User → Paywall CRO → Paid Customer

1. Form CRO

Optimize lead capture forms, contact forms, demo requests, and quote forms (not signup/registration).

Core Principles

  1. Every Field Has a Cost - Each field reduces completion by 10-25%
  2. Value Must Exceed Effort - Clear value proposition above form
  3. Reduce Cognitive Load - One question per field, logical grouping

The 5-Field Rule

FieldsTypical Impact
3 fieldsBaseline
4-6 fields10-25% reduction
7+ fields25-50%+ reduction

For each field, ask:

  • Is this absolutely necessary before we can help them?
  • Can we get this information another way?
  • Can we ask this later?

Field Optimization

Email: Single field, inline validation, typo detection

Name: Test single "Name" vs. First/Last split

Phone: Make optional if possible, explain why if required

Message: Make optional, expand on focus

Multi-Step Forms

Use when:

  • More than 5-6 fields needed
  • Logically distinct sections
  • Conditional paths based on answers

Best practices:

  • Progress indicator (step X of Y)
  • Start with easy, end with sensitive
  • Allow back navigation
  • Save progress

Submit Button Copy

Weak: "Submit", "Send"

Strong: "[Action] + [What they get]"

  • "Get My Free Quote"
  • "Download the Guide"
  • "Request Demo"

2. Signup Flow CRO

Optimize registration, account creation, and trial activation flows.

Core Principles

  1. Minimize Required Fields - Email + Password minimum
  2. Show Value Before Asking - Can they experience product first?
  3. Reduce Perceived Effort - "Takes 30 seconds"

Field Priority

PriorityFields
EssentialEmail, Password
Often neededName
Usually deferrableCompany, Role, Team size, Phone

Social Auth Options

  • B2C: Google, Apple, Facebook
  • B2B: Google, Microsoft, SSO
  • Consider "Sign up with Google" as primary

Single-Step vs. Multi-Step

Single-step works: 3 or fewer fields, simple B2C, high-intent visitors

Multi-step works: More than 3-4 fields, B2B needing segmentation

Progressive commitment pattern:

  1. Email only (lowest barrier)
  2. Password + name
  3. Customization questions (optional)

Trust Elements

  • "No credit card required" (if true)
  • "Free forever" or "14-day free trial"
  • Privacy note: "We'll never share your email"
  • Testimonial near signup form

3. Onboarding CRO

Optimize post-signup user activation and time-to-value.

Core Principles

  1. Time-to-Value Is Everything - How quickly can someone experience core value?
  2. One Goal Per Session - Don't teach everything at once
  3. Do, Don't Show - Interactive > Tutorial
  4. Progress Creates Motivation - Show advancement, celebrate completions

Define Your Aha Moment

The action that correlates most strongly with retention:

Product TypeAha Moment
Project managementCreate first project + add team member
AnalyticsInstall tracking + see first report
Design toolCreate first design + export/share
CollaborationInvite first teammate
MarketplaceComplete first transaction

Onboarding Checklist Pattern

Best practices:

  • 3-7 items (not overwhelming)
  • Order by value (most impactful first)
  • Start with quick wins
  • Progress bar/completion %
  • Celebration on completion

Example item:

☐ Connect your first data source (2 min)
  Get real-time insights from your existing tools
  [Connect Now]

Empty States

Empty states are onboarding opportunities:

  • Explain what this area is for
  • Show what it looks like with data
  • Clear primary action to add first item
  • Optional: Pre-populate with example data

Handling Stalled Users

  1. Detection: Define "stalled" criteria (X days inactive)
  2. Email sequence: Reminder of value, address blockers, offer help
  3. In-app recovery: Welcome back message, pick up where left off
  4. Human touch: Personal outreach for high-value accounts

4. Popup CRO

Optimize popups, modals, overlays, slide-ins, and banners.

Core Principles

  1. Timing Is Everything - Too early = annoying, too late = missed opportunity
  2. Value Must Be Obvious - Clear, immediate benefit
  3. Respect the User - Easy to dismiss, remember preferences

Trigger Strategies

TriggerWhen to UseExample
Scroll-based (25-50%)Blog posts, long-form content"You're halfway through—get more"
Exit intentE-commerce, lead gen"Wait! Before you go..."
Click-triggeredLead magnets, demosZero annoyance
Time-based (30-60s)Proven engagementGeneral site visitors

Popup Types

Email Capture: Newsletter subscription

  • Clear value prop (not just "Subscribe")
  • Single field (email only)
  • Consider incentive

Lead Magnet: Exchange content for email

  • Show what they get (cover image)
  • Minimal fields

Exit Intent: Last-chance conversion

  • Acknowledge they're leaving
  • Different offer than entry popup

Announcement Banner: Site-wide communication

  • Top of page, dismissable
  • Time-limited

Headline Formulas

  • Benefit: "Get [result] in [timeframe]"
  • Question: "Want [desired outcome]?"
  • Social proof: "Join [X] people who..."
  • Curiosity: "The one thing [audience] always get wrong"

Decline Options

Good: "No thanks", "Maybe later"

Avoid: "No, I don't want to save money" (manipulative)

Frequency Rules

  • Show maximum once per session
  • Remember dismissals (7-30 days before showing again)
  • Exclude converted users
  • Exclude checkout/conversion flows

5. Paywall & Upgrade CRO

Optimize in-app paywalls, upgrade screens, and freemium conversion.

Core Principles

  1. Value Before Ask - User should have experienced value first
  2. Show, Don't Just Tell - Demonstrate the value of paid features
  3. Friction-Free Path - Easy to upgrade when ready
  4. Respect the No - Don't trap or pressure

Paywall Trigger Points

TriggerExample
Feature gatesClick paid-only feature
Usage limitsHit storage/project limit
Trial expiration7, 3, 1 day warnings
Context-triggeredPower user behavior

Paywall Screen Components

  1. Headline: Focus on benefit, not price

- "Unlock [Feature] to [Benefit]" - NOT: "Upgrade to Pro for $X/month"

  1. Value Demonstration: Preview the feature in action
  2. Social Proof: "X teams use this feature"
  3. CTA: "Upgrade to Pro" (specific)
  4. Escape Hatch: "Continue with Free" (respectful)

Feature Lock Paywall Template

[Lock Icon]
This feature is available on Pro

[Feature preview/screenshot]

[Feature name] helps you [benefit]:
• [Specific capability]
• [Specific capability]

[Upgrade to Pro - $X/mo]
[Maybe Later]

Trial Expiration Template

Your trial ends in 3 days

What you'll lose:
• [Feature they've used]
• [Data they've created]

What you've accomplished:
• Created X projects

[Continue with Pro - $X/mo]
[Remind me later] [Downgrade to Free]

Anti-Patterns to Avoid

  • Hiding the close button
  • Confusing plan selection
  • Guilt-trip copy
  • Asking before value delivered
  • Too frequent prompts
  • Surprise charges

Quick Reference: CRO by Funnel Stage

StageKey MetricPrimary Focus
PageBounce rate, CTA clicksValue prop clarity, visual hierarchy
FormCompletion rateReduce fields, clear labels
SignupSignup completionMinimize friction, social auth
OnboardingActivation rateTime to aha moment
PopupConversion rateTiming, value exchange
PaywallUpgrade rateValue demonstration

Measurement

Key Metrics by Stage

  • Form start rate: Page views → Started form
  • Completion rate: Started → Submitted
  • Field drop-off: Which fields lose people
  • Activation rate: % reaching aha moment
  • Time to activation: Days to first value
  • Upgrade rate: Free → Paid conversion

Credits & Attribution

This skill is based on the excellent work by AITYTech.

Original repository: https://github.com/aitytech/agentkits-marketing

Special thanks to AITYTech for their generous open-source contributions, which helped shape this skill collection. Adapted by webconsulting.at for this skill collection

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

34.17%
按下载量换算134

Claude

28.84%
按下载量换算113

Cursor

18.58%
按下载量换算73

Gemini CLI

9.6%
按下载量换算38

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills