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

gtm-product-led-growthGTM 产品引领增长

Agent Skill

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

总安装

30,264

周安装

1,337

GitHub Stars

31,678

下载量

10,608
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/github/awesome-copilot --skill gtm-product-led-growth

简介

gtm-product-led-growth 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果时使用。

  • 它支持产品驱动增长策略,提供用户获取和功能推广方案。
  • 可通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。
  • 安装前建议确认权限范围和维护状态,避免触发不必要的联网或文件操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Product-Led Growth

Build self-serve acquisition and expansion motions. But first, figure out if PLG is even the right motion for your product.

When to Use

Triggers:

  • "Should we build PLG or sales-led?"
  • "How do we drive self-serve adoption?"
  • "Freemium to paid conversion isn't working"
  • "Developer-led adoption strategy"
  • "Which growth channels should we invest in?"
  • "How do I know if PLG will work?"

Context:

  • Developer tools and platforms
  • B2B SaaS with self-serve potential
  • Products where value is obvious without demo
  • Bottom-up adoption motions
  • Growth channel prioritization

Core Frameworks

1. The PLG Reality Check (Test Before You Commit)

What I Learned Running Both Motions in Parallel:

Classic startup debate. PLG camp: "Developers want self-serve." Sales camp: "Enterprises need hand-holding." Instead of arguing, we tested both for 6 months. Same product, two GTM motions, tracked everything.

The Results:

PLG: High volume, low ACV ($5K), fast time-to-revenue, higher churn. Sales-led: Lower volume, high ACV ($50K), slower time-to-revenue, lower churn. Sales won 10x on dollars despite 10x less volume.

Why: Product complexity + buyer seniority = sales-led wins. The product required integration with existing infrastructure, change management across teams, and multi-stakeholder alignment. Developers loved self-serve. But they weren't the economic buyer.

PLG works when:

  • Value is obvious in first 5 minutes
  • Implementation is trivial
  • Individual user gets value without team buy-in
  • No procurement/legal hurdles
  • Buyer = user

Sales-led works when:

  • Product requires integration/setup
  • Multiple stakeholders need alignment
  • Buyer ≠ user
  • Deal size justifies human touch
  • Customer needs education to see value

Before building PLG, test your motion. Don't assume PLG is better because it's trendy. PLG is efficient at volume, but sales-led can be more profitable with complexity.


2. The Growth Equation (Map Inputs to Outputs)

The Pattern:

Growth compounds when you systematize the relationship between activities and user acquisition. Not "do more marketing" — map specific inputs to measurable outputs.

How to Build Your Growth Equation:

For each channel, define: Activity (input) → Traffic (output) → Conversions.

  • Organic Search: 1 quality blog post → 400 users/month → 5% conversion = 20 new users
  • Paid Ads: $1K spend at 8% conversion on 100K impressions = 8K clicks → conversions at X%
  • Community Events: 1 event → 60 attendees → 35% conversion = 21 users
  • Referral: 1 integration partner → N referred users → conversions at Y%

Why This Matters:

Once you validate the equation, scaling becomes math. "I need 200 more users next month" → "I need 10 more blog posts" or "I need $5K more ad spend." Without the equation, you're guessing.

Testing the Equation:

  1. Start with hypothesis: "If I create X, it drives Y conversion"
  2. Test with small sample: 1 blog post, measure actual conversion
  3. Validate: Does reality match hypothesis?
  4. Scale with confidence: If yes, increase input
  5. Kill if not: 4 weeks of data is enough to decide

Common Mistake:

Guessing at conversion rates without testing. Assuming all users from the same channel are equal quality. Scaling before validating the equation.


3. Channel Economics (Kill Losers, Double Down on Winners)

The Pattern:

Every channel has economics. Without tracking them, you over-invest in losers and under-invest in winners.

Track Per Channel:

  1. CAC: Total spend / new users
  2. Conversion rate: Signups → paying
  3. Retention: 30-day, 90-day by source
  4. LTV: Revenue over customer lifetime, by channel
  5. Payback period: How long to recoup CAC

The Decision Framework:

  • CAC < (LTV × margin) → Scale aggressively
  • CAC ≈ (LTV × margin) → Optimize, don't scale
  • CAC > (LTV × margin) → Kill within 4 weeks

Monthly channel review: Which channels are profitable? Which are drains? Quarterly reallocation: 3x budget to winners, kill losers.

Critical Insight: Channel Quality Varies

Cheap CAC doesn't mean good CAC. Organic search might deliver users at $0 CAC with 85% 30-day retention. Paid search might deliver users at $12 CAC with 45% 30-day retention. The "free" channel is 10x more valuable when you factor in retention and LTV.

Systematic Testing:

Test 2 new channels monthly. Give each 4 weeks of data. Kill decisively if economics don't work. Document learnings regardless of outcome — what didn't work is as valuable as what did.

Common Mistake:

Tracking CAC without retention. A cheap channel that churns users costs more than an expensive channel that retains them.


4. Time to First Value (The Only Activation Metric)

The Pattern:

Users decide product value in the first 5-10 minutes. If they don't reach the aha moment fast, they abandon.

The Activation Audit:

  1. Sign up for your own product as a new user
  2. Time how long to first value
  3. Count steps to aha moment
  4. Where did you get stuck?

If TTFV > 10 minutes, you have an activation problem.

Before: Sign up → confirm email → fill profile → configure settings → read docs → first action

After: Sign up → pre-loaded sample data → first action (immediate aha moment)

Specific Fixes:

  1. Pre-load sample data. Users want to see value, not set up. Give them a working example immediately.
  2. Skip non-essential setup. Email confirmation, profile, settings — all can wait until after the aha moment.
  3. Progressive disclosure. Don't show all features upfront. Start with one core workflow. Reveal complexity gradually.
  4. Show, don't tell. Interactive tutorial > video > text docs. Let them click through a workflow.

Common Mistake:

Assuming users will read documentation. They won't. They'll click around for 5 minutes, and if nothing works, they leave.


5. The $5K → $50K Inflection (When PLG Breaks)

The Pattern:

PLG works for $1K-$10K ARR. Between $20K-$50K, the motion breaks because organizational friction kicks in: procurement, legal, security, multi-stakeholder buy-in.

The Hybrid Approach:

PLG ($0-$10K): Self-serve sign-up → free tier → paid tier → credit card checkout → automated onboarding

Sales-Assisted ($10K-$50K): Self-serve discovery → sales engages on usage signals → human-negotiated contract → dedicated onboarding

Enterprise ($50K+): Outbound or inbound lead → demo → POC → proposal → legal/security review → executive sponsor

PQL Signals (When to Trigger Sales):

  • Usage depth: Daily active, core features used, approaching limits
  • Expansion signals: Multiple users from same company, team features, integrations
  • Buying signals: Requests for SSO/compliance/SLAs, asks about team pricing

The Handoff:

Bad: "Hey, I saw you signed up." (Cold, generic, kills trust) Good: "Your team is using [specific feature] across 12 repos. We can help you [specific value]. Want 15 minutes?" (Warm, specific, offers value)

Common Mistake:

Sales engaging too early on <$5K deals. Kills PLG motion, scares users. Let them self-serve until they need help.


6. Growth Forecasting (Plan for Uncertainty)

The Pattern:

Forecasts are always wrong. Plans are still valuable because they force thinking and create accountability.

Model Three Scenarios:

Baseline (current trajectory continues):

  • Organic search: 35% growth → 40K new users
  • Paid: Flat → 2K new users
  • Community: 10% growth → 400 new users
  • Total: 42.4K

Upside (if all growth initiatives execute):

  • Organic: 50% growth (3x content) → 48K
  • Paid: 2x spend, same efficiency → 4K
  • New initiative (partnerships): ramp → 3K
  • Total: 55K

Downside (if key channels fail):

  • Organic: 0% growth → 26K
  • Paid: CPA doubles → 1K
  • Total: 27K

Use This For:

  • Setting baseline targets (baseline scenario)
  • Stretch goals (upside scenario)
  • Escalation triggers (if you hit downside, something needs to change)
  • Resource allocation (what inputs change to hit upside?)

Monthly Update: Compare forecast to actual. Adjust model. Don't forecast-and-forget.

Common Mistake:

Overly optimistic forecasts that assume everything works. Not updating monthly. Treating forecast as target (it's a range, not a number).


7. The Playbook Documentation Habit

The Pattern:

Knowledge dies with people. The goal isn't one-off wins — it's systematizing what works.

After every successful campaign or experiment, write a 1-page playbook:

PLAYBOOK: [Channel/Tactic Name]

Goal: [What outcome]
Steps: [Numbered, specific enough for someone unfamiliar]
Expected Output: [Specific metrics]
Metrics to Track: [How to measure]
Risks & Mitigations: [What could go wrong]
Owner: [Name]
Last Updated: [Date]

The Test: Could someone who wasn't involved execute this playbook? If not, it's too vague.

Review quarterly. Remove playbooks that no longer work. Update ones that have evolved. This becomes your growth operating system.

Common Mistake:

Running experiments without documenting learnings. Scaling before you understand the mechanism. Having growth knowledge trapped in one person's head.


Decision Trees

Should We Build PLG or Sales-Led?

Can users get value in <10 min without docs?
├─ No → Sales-led required
└─ Yes → Can they self-serve implementation?
    ├─ No → Sales-led required
    └─ Yes → Is buyer = user?
        ├─ No → Hybrid (PLG + sales-assist)
        └─ Yes → Pure PLG viable

Keep, Scale, or Kill This Channel?

CAC < (LTV × margin)?
├─ No → Kill within 4 weeks
└─ Yes → 90-day retention > 60%?
    ├─ No → Optimize (improve activation/onboarding)
    └─ Yes → Scale aggressively (3x budget)

Common Mistakes

1. Assuming PLG always works Product complexity + buyer seniority = sales-led wins. Test before committing.

2. No channel economics Every channel has CAC, retention, and LTV. Track them or you're flying blind.

3. Free tier too generous or too limited Too generous: no conversion. Too limited: no activation. Allow 10-20 aha moments.

4. No growth equation "Do more marketing" isn't a strategy. Map inputs → outputs → conversions per channel.

5. Scaling before validating 4 weeks of data before scaling any channel. Kill decisively if economics don't work.

6. Growth knowledge in one person's head Document every successful experiment as a playbook.


Quick Reference

PLG readiness: Value in <10 min + self-serve implementation + buyer = user

Growth equation: Activity (input) → Traffic (output) → Conversions, per channel

Channel economics: CAC, conversion, 30/90-day retention, LTV, payback — per channel, monthly review

Kill criteria: CAC > (LTV × margin) → 4 weeks to improve, then kill

PQL signals: Usage depth + expansion (multi-user) + buying (SSO/compliance requests)

Sales handoff: <$10K: PLG → $10K-$50K: Sales-assist → >$50K: Full sales

Forecast: Baseline + Upside + Downside, updated monthly


Related Skills

  • technical-product-pricing: Freemium thresholds and pricing gates
  • developer-ecosystem: Developer-specific adoption programs
  • 0-to-1-launch: Finding first customers before PLG scales

*Based on experience across multiple platform companies — leading a growth team building PLG and sales-led motions from scratch, and operating inside successful PLG + sales-led machines at hypergrowth companies. The combination taught both sides: what it takes to establish these motions early (when resources are thin and every bet matters) and what the mature version looks like at scale (growth equations, channel economics systems, freemium pricing gates, and systematic A/B testing that documents every win and loss into executable playbooks). Not theory — lessons from building the machine and operating inside ones that worked.*

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

35.63%
按下载量换算3,780

Claude

28.34%
按下载量换算3,006

Cursor

19.32%
按下载量换算2,049

Gemini CLI

9.18%
按下载量换算974

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

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

安装前确认

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

来源信息

继续浏览同类 Skills