Token导航 LogoToken导航

Agent Skill · 开发

growth(growth 搜索)

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

growth 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 20,111。

总安装 240周安装 10GitHub Stars 167下载 80核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/whawkinsiv/claude-code-skills --skill growth

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

growth 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态或协作事项进行整理。通过 npx skills add 命令从指定仓库安装并使用。安装前需确认权限范围、维护状态,避免触发联网或文件读写。

建议结合原始 README 核验具体用法和功能边界。

来源仓库内路径:skills/growth

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/whawkinsiv/claude-code-skills --skill growth;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

growth 怎么安装?

在终端执行 npx skills add https://github.com/whawkinsiv/claude-code-skills --skill growth。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

growth 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

growth 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

growth 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

growth 用的人多吗?

公开数据是累计安装 240 次,近一周安装 10 次,下载 80 次,GitHub 167 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

growth 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
growth

growth 搜索 · 本页

240167权限未标注未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Growth & Product-Led Growth

In PLG, the product is your best salesperson. This skill helps you design growth into your product — with concrete tactics and prompts you can hand to Claude Code.

Core Principles

  • Growth is a system, not a hack. Build loops, not one-time campaigns.
  • Activation is the most important metric. A user who never experiences value is already lost.
  • Virality is engineered, not accidental. Design sharing into the product.
  • Retention is the foundation. Growing on top of a leaky bucket is a losing game.
  • For a solo founder: pick ONE growth lever, make it work, then add the next.

The PLG Funnel

Acquisition → Activation → Retention → Revenue → Referral

The most common mistake: Founders focus on Acquisition first. Focus on Activation and Retention first — there's no point driving signups into a leaky bucket.


Activation (Start Here)

Define Your Aha Moment

The specific action where users first experience core value:

Product TypeExample Aha Moment
Project managementCreated first project + added a task
Email toolSent first campaign
AnalyticsSaw first dashboard with real data
Design toolExported first design
SchedulingBooked first meeting through the tool

Your aha moment: [Action that makes users say "I get it, this is useful"]

Drive Users to Aha Fast

Every screen between signup and the aha moment is a drop-off risk.

Tell AI:

Design the onboarding flow to get users to [your aha moment] in under 3 minutes:
1. After signup, skip the "check your email" screen — go directly to the product
2. Show a setup wizard (3-5 steps max) that collects only what's needed to deliver value
3. Pre-populate with sample data or templates so the product looks useful immediately
4. Add a progress checklist: "Complete your setup: ☑ Create [X] ☐ [Next step] ☐ [Final step]"
5. Show an empty state with a clear CTA on every empty page ("Create your first [X]")

Activation Emails

Pair your in-product onboarding with a 5-email welcome sequence that nudges unactivated users. See the email skill for the full welcome sequence template with ready-to-paste copy for each email.


Acquisition Strategies

Pick ONE that matches your product. Don't spread across all of them.

StrategyBest ForEffortTime to Results
Free tool / calculatorProducts that solve measurable problemsMedium1-3 months
Template galleryProducts with customizable outputsMedium2-4 months
Content-as-productProducts in information-heavy spacesHigh3-6 months
Community-drivenProducts with passionate niche usersHigh3-6 months
IntegrationsProducts that connect to other toolsMedium1-2 months per integration
FreemiumProducts where free use drives word-of-mouthLowImmediate (but slow growth)

Tell AI:

Build a [free tool / template gallery / calculator] that:
- Solves a specific problem our ICP has (related to our product)
- Requires no signup to use
- Shows a teaser of our full product's value
- Includes a CTA: "Want more? [Product name] does this automatically."
- Is SEO-optimized so it attracts organic traffic

Viral Loop Design

A viral loop has 4 parts: User gets value → Has reason to share → New user sees value → Converts → Loop repeats.

Viral Mechanics for SaaS

MechanicHow It WorksExample
Collaboration invitesProduct requires multiple users"Invite your team to edit this"
Shared outputsUser creates something shareableReports, links, dashboards with "Made with [Product]"
Referral rewardsIncentivized invitations"Give $20, get $20"
Public pagesUser content is SEO-indexablePublic profiles, portfolios, pages
EmbedsWidget on user's site links backBadges, chat widgets, forms

Tell AI:

Add a sharing/invite mechanic to our product:
- After a user completes [key action], prompt: "Share this with your team" or "Invite a collaborator"
- Make shared links show a preview of the output (not just a signup page)
- Add "Made with [Product]" branding on shared/public outputs with a link to our homepage
- Track invite sends, invite accepts, and invite-to-signup conversion

Retention Mechanics

Build Habit Loops

ComponentWhat It IsExample
TriggerWhat brings them backEmail digest, notification, calendar event
ActionWhat they do in the productCheck dashboard, respond to comment, update status
RewardValue they getNew insight, progress indicator, completed task
InvestmentWhat makes leaving harderMore data, more connections, more history

Tell AI:

Build retention mechanics into the product:
1. Weekly email digest: summarize what happened this week + one insight or action item
2. Activity notifications: "[Name] commented on your [item]" — not time-based ("It's been 3 days")
3. Progress indicators: Show users their cumulative value ("You've saved 14 hours this month")
4. Data investment: The more they use it, the more valuable their data becomes (history, reports, trends)

Feature Drips

Don't show everything on day 1. Reveal features as users are ready:

Tell AI:

Implement progressive feature disclosure:
- Week 1: Show only core features (the ones needed for the aha moment)
- Week 2: Surface advanced feature with a tooltip: "Now that you've [done X], try [advanced feature]"
- Week 3+: Unlock remaining features with brief explanations
- Gate premium features with a gentle upgrade prompt at the moment of need

Metrics to Track

Set these up in your analytics tool (see analytics-instrumentation skill):

StageKey MetricHow to Calculate
AcquisitionSignup rateVisitors → Signups
ActivationActivation rateSignups → Completed aha moment
ActivationTime to ahaAverage hours/days from signup to key action
RetentionD1/D7/D30% of users returning on day 1, 7, 30
RevenueFree-to-paidFree users → Paying users
ReferralViral coefficientInvites sent × invite conversion rate

Tell AI:

Set up growth tracking:
- Track signup events with source attribution (organic, paid, referral, direct)
- Track [aha moment action] completion with timestamp
- Calculate time-to-activate for each user
- Build a daily dashboard showing: signups, activations, D7 retention, free-to-paid conversion
- Alert me if activation rate drops below [X]% or D7 retention drops below [Y]%

Growth Experiments

When you want to improve a metric, frame it as a hypothesis:

  1. Hypothesis: "If we [change], then [metric] will [improve] because [reason]."
  2. Metric: What specifically will you measure?
  3. Duration: Run for 1-2 weeks minimum, or until 100+ users have been through the flow.
  4. Decide: Did the metric improve? Ship it or revert.
  5. Document: Write down what you learned, even (especially) from failures.

For A/B test setup, implementation, and reading results, see the conversion skill's A/B testing section.


Common Mistakes

MistakeFix
Focusing on acquisition before activationFix activation first — no point driving users into a broken onboarding
Building viral features nobody usesViral loops must be part of the core workflow, not a sidebar feature
Measuring vanity metrics (signups)Track activation rate and retention, not just signups
Trying all channels at oncePick ONE, make it work, then add another
Complex A/B testing infrastructureUse simple feature flags. You don't need Optimizely at 100 users

Related Skills

  • conversion — Funnel optimization, A/B testing, and signup flow CRO
  • email — Welcome sequences and lifecycle emails that drive activation
  • analytics — Set up the tracking that powers growth metrics
  • retention — Deep-dive on churn prevention and win-back
  • pricing — Pricing tiers and expansion revenue mechanics

平台分布

Codex

36.2%
按下载量换算29

Claude

30.13%
按下载量换算24

Cursor

17.77%
按下载量换算14

Gemini CLI

8.82%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

继续浏览同类 Skills