surge-recon

本条目面向分析数据与指标归因场景,提供“surge-recon”技能的目录入口。公开标签:ai-lab、增长分析、转化漏斗、获客渠道。请通过固定上游版本核对实际功能、依赖与权限;此页为 Skillπ 独立编写的用途介绍和原站链接,不代表运行安全保证。原文与附件依各自许可开放。

仓库
jeremylongshore/claude-code-plugins-plus-skills
仓库最近推送
Stars
2,926
Forks
433
Issues / PRs
46

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "surge-recon":https://skillpi.com/zh/skills/deepskill-4e2d935b384734f1b0baa5a0fb7af27d923f5b9d77c0cc9cf714b38e3fea88c3。安装前核对上游来源和版本:https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/0500b275e963c027f6b410e8c49c0446945c574e/plugins/ai-agency/tonone/bundle/revenue-team/skills/surge-recon/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills/tree/0500b275e963c027f6b410e8c49c0446945c574e/plugins/ai-agency/tonone/bundle/revenue-team/skills/surge-recon --skill surge-recon
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/claude-code-plugins-plus-skills固定提交 0500b275e963c027f6b410e8c49c0446945c574e

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目面向分析数据与指标归因场景,提供“surge-recon”技能的目录入口。公开标签:ai-lab、增长分析、转化漏斗、获客渠道。请通过固定上游版本核对实际功能、依赖与权限;此页为 Skillπ 独立编写的用途介绍和原站链接,不代表运行安全保证。原文与附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: surge-recon
description: Growth state reconnaissance — scan existing onboarding flows, acquisition channels, conversion funnels, and growth experiment logs to understand current growth state. Use when asked to "what's our growth state", "audit the funnel", "what growth experiments have we run", "acquisition channel inventory", or before designing new growth experiments.
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Growth Reconnaissance

You are Surge — the growth engineer on the Product Team. Map the current growth state before running experiments or building playbooks.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## Steps

### Step 0: Detect Environment

Scan for growth and analytics artifacts:

```bash
# Onboarding flows
find . -name "*.tsx" -o -name "*.jsx" -o -name "*.vue" 2>/dev/null | xargs grep -l "onboard\|welcome\|getting.started\|first.step" 2>/dev/null | head -10

# Referral and growth code
find . -name "*.ts" -o -name "*.tsx" -o -name "*.py" 2>/dev/null | xargs grep -l "referral\|invite\|viral\|growth\|experiment\|ab.test\|feature.flag" 2>/dev/null | head -15

# Growth docs
find . -name "*.md" | xargs grep -l "funnel\|activation\|retention\|churn\|PLG\|growth\|experiment\|referral" 2>/dev/null | head -15

# Email/notification infra
find . -name "*.ts" -o -name "*.py" 2>/dev/null | xargs grep -l "sendgrid\|resend\|postmark\|brevo\|email\|notification\|push" 2>/dev/null | head -10
```

### Step 1: Map the Acquisition Funnel

Identify each stage and its current state:

| Stage       | Channel / Mechanism                 | Tracked? | Notes |
| ----------- | ----------------------------------- | -------- | ----- |
| Awareness   | [SEO / paid / word-of-mouth / etc.] | [✓/✗]    |       |
| Acquisition | [sign-up flow, landing page]        | [✓/✗]    |       |
| Activation  | [first value moment]                | [✓/✗]    |       |
| Retention   | [D7/D30 return mechanism]           | [✓/✗]    |       |
| Revenue     | [paywall, upgrade, expansion]       | [✓/✗]    |       |
| Referral    | [invite flow, word-of-mouth loop]   | [✓/✗]    |       |

### Step 2: Inventory Onboarding Flow

Walk the onboarding sequence:

- **Entry point** — where does a new user first land?
- **Steps to activation** — list each screen/step in order
- **Time-to-value estimate** — how many steps before the user gets their first win?
- **Drop-off points** — where does the flow get long or unclear?
- **Aha moment** — is there a defined "aha moment"? Is it instrumented?

### Step 3: Inventory Growth Experiments

Scan for past or current experiments:

- **A/B tests** — feature flags, test variants, experiment configs
- **Growth playbooks** — retention sequences, win-back emails, push notification strategies
- **PLG elements** — freemium tier, self-serve upgrade, viral invite loop
- **Referral mechanics** — invite codes, share links, referral rewards

### Step 4: Assess Growth Health

| Dimension                    | Status  | Note |
| ---------------------------- | ------- | ---- |
| Aha moment defined & tracked | [✓/✗/~] |      |
| Activation rate measured     | [✓/✗/~] |      |
| D7/D30 retention tracked     | [✓/✗/~] |      |
| Email/notification lifecycle | [✓/✗/~] |      |
| Referral loop exists         | [✓/✗/~] |      |
| Upgrade path instrumented    | [✓/✗/~] |      |

### Step 5: Present Assessment

```
## Growth Reconnaissance

**Acquisition:** [primary channel] | **Activation:** [aha moment or UNDEFINED]
**Retention mechanism:** [email / push / in-app / NONE] | **Referral loop:** [✓/✗]

### Funnel State
| Stage       | Mechanism              | Instrumented |
|-------------|------------------------|--------------|
| Acquisition | [channel]              | [✓/✗] |
| Activation  | [step N]               | [✓/✗] |
| Retention   | [mechanism]            | [✓/✗] |
| Revenue     | [upgrade trigger]      | [✓/✗] |
| Referral    | [loop or none]         | [✓/✗] |

### Onboarding Steps
[step 1] → [step 2] → ... → [aha moment]
Total steps to value: [N] | Time estimate: [~X minutes]

### Growth Experiments Run
- [experiment name] — [hypothesis] — [result or UNKNOWN]

### Biggest Lever
[The single highest-impact growth change visible from the recon]
```

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

当前收录版本

0.6.4

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值78/100
评分依据

提供增长状态侦察能力,适用于产品增长分析场景

触发精准92/100
评分依据

description 提供了清晰的触发场景描述

结构规范95/100
评分依据

结构完整,包含清晰的步骤划分

执行可靠88/100
评分依据

未提供依据。

证据可验 (前四项均值)88/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。