Official agent skill

Gtm Product Led Growth

by github in github/awesome-copilot

Build self-serve acquisition and expansion motions. An agent skill from github/awesome-copilot.

OfficialMITAuto-check passedMarketing & SEO

Install Gtm Product Led Growth

skills CLI
$ npx skills add github/awesome-copilot --skill gtm-product-led-growth -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot gtm-product-led-growth --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gtm-product-led-growth .claude/skills/gtm-product-led-growth && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gtm-product-led-growth
GitHub stars
40k
Used in
1 other repo
Token cost
~3.1k tokens
SKILL.md length
1,557 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

Build self-serve acquisition and expansion motions. An agent skill from github/awesome-copilot.

  • Works in 7 steps: The PLG Reality Check (Test Before You… → The Growth Equation (Map Inputs to… → Channel Economics (Kill Losers, Double… → …
  • Deciding PLG vs sales-led
  • SKILL.md covers When to Use, Core Frameworks, Decision Trees and Common Mistakes, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gtm Product Led Growth is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Build self-serve acquisition and expansion motions. Use when deciding PLG vs sales-led, optimizing activation, driving freemium conversion, building growth equations, or recognizing when product complexity demands human touch. Includes the parallel test where sales-led won 10x on revenue.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Go-to-market strategy. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • Deciding PLG vs sales-led
  • Optimizing activation
  • Driving freemium conversion
  • Building growth equations

Example prompts

  • “/gtm-product-led-growth”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. The PLG Reality Check (Test Before You Commit)
  2. The Growth Equation (Map Inputs to Outputs)
  3. Channel Economics (Kill Losers, Double Down on Winners)
  4. Time to First Value (The Only Activation Metric)
  5. The $5K → $50K Inflection (When PLG Breaks)
  6. Growth Forecasting (Plan for Uncertainty)
  7. The Playbook Documentation Habit

What it can do on your machine

Read from SKILL.md and the folder at commit 82701c2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gtm Product Led Growth loads about 3.1k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 1,557 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 82701c2, republished under its MIT licence (© github). 1,557 words, ~3,127 tokens.

Download SKILL.mdSave it as .claude/skills/gtm-product-led-growth/SKILL.md (or your agent's skills folder).
name
gtm-product-led-growth
description
Build self-serve acquisition and expansion motions. Use when deciding PLG vs sales-led, optimizing activation, driving freemium conversion, building growth equations, or recognizing when product complexity demands human touch. Includes the parallel test where sales-led won 10x on revenue.
license
MIT
metadata.author
Smit Patel (https://linkedin.com/in/smitkpatel)
metadata.source
https://github.com/beingsmit/technical-product-gtm

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.


Show full SKILL.md (694 more words)Show less
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


  • 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.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/gtm-product-led-growth of github/awesome-copilot.

Open the folder on GitHubat commit 82701c2

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Gtm Product Led Growth next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gtm Product Led Growth compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gtm Product Led Growth this skillgithub/awesome-copilot40k1 repos~3.1kAutomated safety check: PassMIT
Marketing PlanNexus-JPF/note-companion8705 repos~5.2kAutomated safety check: PassMIT
Revenue Centric Designheliocosta-dev/revenue-centric-design740—~1.6kAutomated safety check: PassCustom licence
Startup Designferdinandobons/startup-skill1.2k—~8.1kAutomated safety check: PassMIT
Jaredrhod Marketingjaredrhod/ai-marketing-skills282—~584Automated safety check: PassCC-BY-SA-4.0
Traffic Acquisitionvivy-yi/xiaohongshu-skills4781 repos~4kAutomated safety check: PassNone

Similar skills

  • Marketing Plan

    Nexus-JPF/note-companion

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

    870 GitHub starsUsed in 5 repos~5.2k tokens
    Marketing & SEOAuto-check passed
  • Revenue Centric Design

    heliocosta-dev/revenue-centric-design

    Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…

    740 GitHub stars~1.6k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Startup Design

    ferdinandobons/startup-skill

    Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.

    1.2k GitHub stars~8.1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • Jaredrhod Marketing

    jaredrhod/ai-marketing-skills

    Run any marketing task the way jaredrhod actually runs it. An agent skill from jaredrhod/ai-marketing-skills.

    282 GitHub stars~584 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Traffic Acquisition

    vivy-yi/xiaohongshu-skills

    A skill your agent uses when driving traffic to Xiaohongshu account from external sources, acquiring new followers beyond organic discovery, implementing multi-platform growth strategy, or scaling…

    478 GitHub starsUsed in 1 repo~4k tokens
    Marketing & SEOAuto-check passed
  • Amazon Product Research

    nexscope-ai/Amazon-Skills

    Comprehensive product research and opportunity analysis for Amazon sellers.

    741 GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo
  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Gtm Product Led Growth

What does Gtm Product Led Growth do?

Build self-serve acquisition and expansion motions. An agent skill from github/awesome-copilot. Gtm Product Led Growth is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Build self-serve acquisition and expansion motions.

When should I use Gtm Product Led Growth?

Gtm Product Led Growth fits situations like: deciding PLG vs sales-led; optimizing activation; driving freemium conversion; building growth equations.

How do I install Gtm Product Led Growth in Claude Code?

Run `npx skills add github/awesome-copilot --skill gtm-product-led-growth -a claude-code`. Or copy the skill folder (skills/gtm-product-led-growth in github/awesome-copilot) into .claude/skills/gtm-product-led-growth in your project. Claude Code loads it when a task matches its description.

How do I install Gtm Product Led Growth in Codex?

Run `npx skills add github/awesome-copilot --skill gtm-product-led-growth -a codex`. Or copy the skill folder (skills/gtm-product-led-growth in github/awesome-copilot) into .agents/skills/gtm-product-led-growth in your project. Codex loads it when a task matches its description.

Can I use Gtm Product Led Growth in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill gtm-product-led-growth -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gtm-product-led-growth, .gemini/skills/gtm-product-led-growth, .github/skills/gtm-product-led-growth and .opencode/skills/gtm-product-led-growth in your project.

What does Gtm Product Led Growth need to run?

SKILL.md names no scripts, command-line tools or credentials: Gtm Product Led Growth is instructions for the agent only.

Does Gtm Product Led Growth access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gtm Product Led Growth safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gtm Product Led Growth use?

Gtm Product Led Growth is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gtm Product Led Growth use?

About 3.1k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gtm Product Led Growth?

Skills that share tags, products or a category with Gtm Product Led Growth: Marketing Plan (Nexus-JPF/note-companion, 870 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Design (ferdinandobons/startup-skill, 1.2k stars) and Jaredrhod Marketing (jaredrhod/ai-marketing-skills, 282 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gtm Product Led Growth?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,830 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 9, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.