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

onboarding-optimization入职优化

Agent Skill

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

总安装

13,635

周安装

557

GitHub Stars

1,102

下载量

4,411
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/eronred/aso-skills --skill onboarding-optimization

简介

onboarding-optimization 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 它支持基于上下文过滤内容、提取关键实体并生成结构化摘要。
  • 通过 npx skills add 命令从指定仓库安装,需确认权限范围和操作边界。
  • 安装前建议核实维护状态、是否会触发联网或文件读写,避免误操作影响生产环境。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Onboarding Optimization

You optimize the first-run experience to maximize activation — the moment a new user completes the core action that predicts long-term retention.

The Activation Principle

Activation ≠ sign-up. Activation is the first time the user gets real value from your app. Identify it before anything else.

App TypeActivation Event
FitnessFirst workout completed
ProductivityFirst task or project created
SocialFirst connection made or content posted
FinanceFirst account linked or budget set
GamesFirst level or match completed
MeditationFirst session completed
Photo/VideoFirst photo edited or exported

Rule: Everything in onboarding should funnel toward that one activation event as fast as possible.

Initial Assessment

  1. Check for app-marketing-context.md
  2. Ask: What is your activation event?
  3. Ask: What % of new users reach it within 24 hours? (baseline)
  4. Ask: Where do users drop off? (which step, if known)
  5. Ask: How long does your current onboarding take? (steps, screens)
  6. Ask: Do you have Firebase/Mixpanel funnels set up?

Onboarding Audit Framework

Step 1 — Map the Current Flow

List every screen from app open to activation:

App open → [Screen 1] → [Screen 2] → ... → Activation event

Flag each screen: Required | Value-adding | Friction only

Remove or defer everything that is friction-only.

Step 2 — Score Each Screen

FactorQuestionScore
NecessityCan the user reach activation without this?0 = skip it
TimingIs this the right moment for this ask?
Value exchangeDoes the user understand why this benefits them?
Cognitive loadHow many decisions does this require?

Step 3 — Permission Prompt Timing

Permissions are the #1 drop-off point. Rules:

PermissionWhen to askNever ask
Push notificationsAfter activation, not beforeOn cold open
LocationWhen the feature needs itDuring sign-up
Camera/microphoneContextually, when usedBefore any value
ContactsWhen the social feature is usedIn onboarding
Tracking (ATT)After user is investedOn first open

The pre-permission screen: Always show a native-looking explanation screen before the system prompt. Users who understand the "why" grant at 2–3× the rate.

Step 4 — Sign-Up Friction

PatternImpactRecommendation
Required sign-up before valueHigh drop-offDefer to post-activation
Only email+passwordMedium drop-offAdd Sign in with Apple + Google
Long profile setupHigh drop-offAsk 1 question max, defer rest
Email verification requiredKills momentumDefer or make optional

Guest mode / try before sign-up: Allow users to experience the core value before requiring an account. Conversion from guest → registered is typically 40–60% vs. a hard gate at 15–30%.

Onboarding Patterns by App Type

Value-First (recommended for most apps)

Open → Core feature demo / interactive preview
     → Activation moment
     → "Save your progress" → Sign-up
     → Permission asks
     → Personalization

Personalization-First (works for health, fitness, AI apps)

Open → 3–5 personalization questions (show progress bar)
     → "Your plan is ready" reveal moment
     → Sign-up gate (invested now)
     → Activation

Social-First (social apps)

Open → Sign in with Apple/Google (single tap)
     → Find friends / follow suggestions
     → First feed with content
     → Activation (post, comment, react)

Funnel Benchmarks

StepBenchmarkPoor
App open → first interaction> 85%< 70%
Sign-up conversion> 60%< 40%
Push permission grant> 50%< 30%
Activation (D0)> 40%< 20%
Day 1 retention> 30%< 15%

Personalization Questions

If you include personalization, follow these rules:

  • Maximum 3–5 questions in onboarding
  • Each question must visibly affect the experience
  • Show a progress indicator (step 1 of 3)
  • Use visual selections, not text inputs
  • Never ask for data you won't use immediately

Paywall Placement in Onboarding

Rule: Show value before the paywall.

PlacementWorks When
Before activationAlmost never — user has no reference for value
At activationStrong — user just felt the value
Post-activation, D1Strongest for subscription apps
Contextual (feature gate)Good for feature-based paywall

See monetization-strategy for paywall design details.

Output Format

Onboarding Audit

Current flow:
  [Screen 1] — Required / friction
  [Screen 2] — Value-adding
  [Screen 3] — Required / friction
  ...
  [Activation event] — Step N

Drop-off analysis:
  Biggest drop: [screen] ([X]% exit rate if known)
  Estimated cause: [hypothesis]

Recommended changes:
1. [Remove / defer X] — Expected impact: [lift in activation]
2. [Reorder Y before Z] — Expected impact: [rationale]
3. [Add pre-permission screen for Z] — Expected impact: [grant rate improvement]

Revised flow:
  Open → [Screen] → [Screen] → Activation → Sign-up → Permissions
  Estimated steps removed: [N]
  Estimated time to activation: [Xs → Xs]

Permission Screen Copy Template

[Icon representing the permission]

[Benefit headline — what the user gets]
e.g., "Get notified when your goal is complete"

[One-line explanation]
e.g., "We'll only send you reminders you set — no spam."

[Allow button]     [Not now]

Related Skills

  • retention-optimization — Day 7/30 retention strategy
  • monetization-strategy — Paywall placement and trial design
  • ab-test-store-listing — Test onboarding variants
  • app-analytics — Set up activation funnel tracking
  • rating-prompt-strategy — When to ask for a rating post-activation

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

32.02%
按下载量换算1,412

Claude

30.16%
按下载量换算1,330

Cursor

19.49%
按下载量换算860

Gemini CLI

9.55%
按下载量换算421

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills