菜单
Use when analyzing conversion funnels across ordered business steps, such as registration, activation, payment, signup, retention, onboarding, or checkout. Identifies drop-off points, segment differences, tracking risks, and action recommendations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | funnel-analysis |
| description | Use when analyzing conversion funnels across ordered business steps, such as registration, activation, payment, signup, retention, onboarding, or checkout. Identifies drop-off points, segment differences, tracking risks, and action recommendations. |
分析一个有明确步骤顺序的转化漏斗，找出用户从入口到目标行为之间在哪里流失、为什么可能流失、下一步应该验证什么。
这个 Skill 关注漏斗分析方法和业务解释，不负责直接审查埋点方案或写完整看板需求。
使用这个 Skill，当用户需要分析：
典型输入：
帮我分析注册到首购的转化漏斗，看看哪个环节掉得最多。
不要用这个 Skill 直接完成：
exploratory-data-analysisretention-cohort-analysisab-test-analysismetric-definition-reviewerdata-analysis-report-writer如果漏斗步骤没有先后顺序，先帮助用户重新定义事件路径。
最少输入：
可选输入：
推荐使用 数据分析上下文模板，也可以参考 电商增长分析示例上下文。
最有价值的上下文是：漏斗步骤、事件定义、统计对象、时间窗口、去重规则和分群维度。步骤顺序或事件定义不清楚时，先定义漏斗，不要直接解释流失。
## 漏斗分析结果
### 1. 结论摘要
### 2. 漏斗定义
| 步骤 | 事件/状态 | 统计对象 | 时间窗口 |
| --- | --- | --- | --- |
### 3. 漏斗表现
| 步骤 | 人数/对象数 | 单步转化率 | 累计转化率 | 流失量 |
| --- | --- | --- | --- | --- |
### 4. 关键流失点
### 5. 分群对比
### 6. 可能原因
### 7. 数据口径与埋点风险
### 8. 建议动作
### 9. 待确认问题
输出必须：
请用 funnel-analysis 分析这个新用户首购漏斗：
时间：2026-05-01 到 2026-05-14
步骤：注册 -> 浏览商品 -> 加购 -> 提交订单 -> 支付成功
对象：user_id 去重
维度：渠道、设备、新客来源
Use when writing a concise daily report, daily worklog, standup update, shift handoff, or end-of-day summary for data analysis, data development, BI, governance, or operations work.
Use when writing or improving data documentation for warehouse tables, metrics, dashboards, SQL jobs, data products, or handover materials so other people and agents can understand data purpose, grain, fields, logic, ownership, and usage constraints.
Use when analyzing upstream and downstream impact for table changes, metric changes, field deprecation, pipeline migration, dashboard breakage, data governance review, or data asset dependency communication.
Use when planning integration with databases, BI tools, data platforms, APIs, workflow systems, storage services, or third-party tools, including connection requirements, API availability, auth strategy, configuration questions, and validation steps.
Use when planning or writing market research for a specific industry, product category, competitor set, business opportunity, user segment, or go-to-market question with structured evidence and clear assumptions.
Use when diagnosing business metric changes or anomalies such as GMV decline, conversion drop, retention loss, churn increase, revenue change, lead decline, or active user fluctuation with a structured root cause analysis plan.