Token导航 LogoToken导航

Agent Skill · 待分类

designing-growth-loops(设计增长循环)

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

designing-growth-loops 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 4,476。

总安装 734周安装 30GitHub Stars 3下载 238核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill designing-growth-loops

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

designing-growth-loops 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。通过 npx skills add 命令从指定仓库安装并使用。

使用前需确认权限范围、维护状态,避免触发联网或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/designing-growth-loops

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

designing-growth-loops 怎么安装?

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

designing-growth-loops 支持哪些 AI 工具?

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

designing-growth-loops 需要什么权限?

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

designing-growth-loops 是免费的吗?

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

designing-growth-loops 用的人多吗?

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

designing-growth-loops 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

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

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
designing-growth-loops

设计增长循环 · 本页

7343只读未明确通过

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

SKILL.md 原文

Designing Growth Loops

Scope

Covers

  • Turning a growth goal into a loop-based growth model (micro loops + macro loops)
  • Designing and documenting loops: viral/referral, content/UGC, SEO, partner/integration, sales-assisted, and paid acquisition loops
  • Choosing channels using a Customer × Business × Medium fit check
  • Validating paid loops with unit economics (LTV, CAC, payback) gating
  • Producing an actionable loop plan: loop map → scorecard → experiments → measurement

When to use

  • “Design a growth loop / viral loop / referral loop”
  • “Create a growth flywheel for ”
  • “Map our micro + macro growth loops and prioritize which to build”
  • “We need new growth loops (not just optimize ads/onboarding)”
  • “Decide whether a paid acquisition loop is viable”

When NOT to use

  • You haven’t clarified the ICP/problem or value proposition (use problem-definition).
  • You’re still establishing PMF and need a PMF signal set (use measuring-product-market-fit).
  • You only need an experiment list/prioritization, not loop design (use prioritizing-roadmap).
  • You’re making a one-way-door launch decision (use shipping-products / running-decision-processes).

Inputs

Minimum required

  • Product + target user/ICP (and 1–2 key segments)
  • Current stage (pre-PMF / early PMF / growth / mature) and current primary growth channel(s)
  • The core value moment (what users do when they “get value”)
  • A baseline snapshot of the growth system (best available): acquisition sources, conversion funnel, retention/engagement, referrals/sharing
  • Constraints: budget, timebox, brand/safety, platform policy, legal/privacy, engineering capacity
  • For paid loops: rough unit economics (LTV, gross margin, CAC/payback targets) or a proxy

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md, then proceed.
  • If data is missing, proceed with explicit assumptions and label confidence.
  • Do not request secrets or PII; prefer aggregated metrics or redacted excerpts.

Outputs (deliverables)

Produce a Growth Loop Design Pack (Markdown in-chat; or as files if requested) containing:

  1. Context snapshot (goal, ICP/segments, constraints, timebox)
  2. Loop inventory + baseline (current loops and where the system currently gets growth)
  3. Loop map (qualitative model) (micro loops + macro loop; how loops connect)
  4. Loop candidates + mechanism library (platform/channel mechanisms; ethical/policy-compliant)
  5. Loop scorecard + selection (top 1–2 loops to build/scale; optimize vs innovate recommendation)
  6. Measurement plan (loop KPIs, leading indicators, required instrumentation)
  7. Experiment backlog + 30/60/90 plan (tests, sequencing, dependencies, owners if known)
  8. Risks / Open questions / Next steps (always included)

Templates and checklists:

Workflow (7 steps)

1) Intake + growth goal framing

  • Inputs: User context; references/INTAKE.md.
  • Actions: Clarify the growth goal (what metric, by when), the target segment(s), and constraints (budget, brand, platform rules, capacity). Decide whether the priority is innovation (new loop) vs optimization (existing loop).
  • Outputs: Context snapshot + “decision this work informs.”
  • Checks: A stakeholder can answer: “Which metric changes by when, and what will we do differently if it doesn’t?”

2) Baseline the current growth system (loops + funnel)

  • Inputs: Current acquisition sources, funnel, retention, referral/share, unit economics (if any).
  • Actions: Inventory existing loops (even if weak). Identify the core value moment and the “loop output” that could feed back (invites, content, word-of-mouth, spend, integrations).
  • Outputs: Loop inventory + baseline table.
  • Checks: Baseline includes at least one number for each: acquisition volume, activation rate, retention/engagement proxy.

3) Generate loop candidates (micro + macro)

  • Inputs: Baseline + constraints.
  • Actions: Create 6–10 loop hypotheses across categories (viral/referral, content/UGC, SEO, partner/integration, sales, paid). For each, specify: input → action → output → feedback. Include at least one “bigger bet” loop if in a fast-moving category.
  • Outputs: Loop candidates list + draft mechanism library.
  • Checks: Each candidate has a plausible “self-reinforcing” feedback path and a likely cycle time.

4) Model loops qualitatively (shared understanding)

  • Inputs: Loop candidates; stakeholder context.
  • Actions: Produce a qualitative loop map: micro loops connected into a macro loop. Document assumptions, bottlenecks, and where you expect compounding.
  • Outputs: Loop map (diagram or table) + bottleneck hypotheses.
  • Checks: Someone unfamiliar with the product can explain “how we grow” in 60 seconds using the map.

5) Quantify + prioritize (scorecard + gates)

  • Inputs: Qual loop map; best-available metrics.
  • Actions: Estimate loop throughput with simple math (conversion × frequency × invites/content × acceptance). Score loops using a scorecard (impact, confidence, effort, cycle time). Apply gates:

- Paid loops: only proceed if LTV/margin supports CAC/payback targets. - Channel fit: ensure Customer × Business × Medium alignment.

  • Outputs: Loop scorecard + top 1–2 loop picks + innovate/optimize split recommendation.
  • Checks: Each chosen loop has (a) a measurable KPI, (b) a first experiment, and (c) a reason it wins vs alternatives.

6) Design the measurement plan (metrics + instrumentation)

  • Inputs: Selected loop(s).
  • Actions: Define loop KPIs and leading indicators; specify required events/properties and dashboards. Identify instrumentation gaps and the minimum tracking needed to learn.
  • Outputs: Measurement + instrumentation plan.
  • Checks: Every experiment metric is traceable to an event definition and a data source.

7) Build the experiment plan + quality gate

  • Inputs: Draft pack; references/CHECKLISTS.md and references/RUBRIC.md.
  • Actions: Create an experiment backlog and 30/60/90 plan (sequencing, dependencies, owners if known). Run the checklist and score with the rubric. Always include Risks / Open questions / Next steps.
  • Outputs: Final Growth Loop Design Pack.
  • Checks: Next 2 weeks of work are unblocked and measurable; risks include policy/ethics considerations.

Quality gate (required)

Examples

Example 1 (B2B SaaS, partner/integration loop): “Use designing-growth-loops. Product: AI onboarding assistant for mid-market HR teams. Goal: +30% WAU in 90 days. Channels today: outbound + partnerships. Output: a Growth Loop Design Pack with an integration/partner loop and a referral loop, including metrics and a 30/60/90 experiment plan.”

Example 2 (B2C, viral/content loop): “We’re building a mobile photo editor for creators. Goal: grow from 20k to 60k MAU in 8 weeks. Output a loop map, a mechanism library for Instagram/TikTok sharing, and a prioritized experiment backlog.”

Boundary example (not a loop problem): “Write copy for our landing page headline.” Response: this is primarily copywriting/positioning, not loop design; clarify the goal and use copywriting or a messaging skill instead.

平台分布

Codex

35.38%
按下载量换算84

Claude

29.52%
按下载量换算70

Cursor

17.5%
按下载量换算42

Gemini CLI

9.27%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills