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.
Build self-serve acquisition and expansion motions. An agent skill from github/awesome-copilot.
$ npx skills add github/awesome-copilot --skill gtm-product-led-growth -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot gtm-product-led-growth --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "gtm-product-led-growth" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-product-led-growth into .claude/skills/gtm-product-led-growth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-product-led-growth", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/gtm-product-led-growthType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add github/awesome-copilot --skill gtm-product-led-growth -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot gtm-product-led-growth --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/gtm-product-led-growth .agents/skills/gtm-product-led-growth && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gtm-product-led-growth" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-product-led-growth into .agents/skills/gtm-product-led-growth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-product-led-growth", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill gtm-product-led-growth -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot gtm-product-led-growth --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/gtm-product-led-growth .cursor/skills/gtm-product-led-growth && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gtm-product-led-growth" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-product-led-growth into .cursor/skills/gtm-product-led-growth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-product-led-growth", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/gtm-product-led-growth--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add github/awesome-copilot --skill gtm-product-led-growth -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot gtm-product-led-growth --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/gtm-product-led-growth .gemini/skills/gtm-product-led-growth && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gtm-product-led-growth" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-product-led-growth into .gemini/skills/gtm-product-led-growth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-product-led-growth", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install github/awesome-copilot gtm-product-led-growthInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add github/awesome-copilot --skill gtm-product-led-growth -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/gtm-product-led-growth .github/skills/gtm-product-led-growth && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gtm-product-led-growth" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-product-led-growth into .github/skills/gtm-product-led-growth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-product-led-growth", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill gtm-product-led-growth -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install github/awesome-copilot gtm-product-led-growth --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/gtm-product-led-growth .opencode/skills/gtm-product-led-growth && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gtm-product-led-growth" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/gtm-product-led-growth into .opencode/skills/gtm-product-led-growth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gtm-product-led-growth", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
gtm-product-led-growthBuild 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. 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.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 82701c2. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from github/awesome-copilot at commit 82701c2, republished under its MIT licence (© github). 1,557 words, ~3,127 tokens.
.claude/skills/gtm-product-led-growth/SKILL.md (or your agent's skills folder).Build self-serve acquisition and expansion motions. But first, figure out if PLG is even the right motion for your product.
Triggers:
Context:
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:
Sales-led works when:
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.
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.
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:
Common Mistake:
Guessing at conversion rates without testing. Assuming all users from the same channel are equal quality. Scaling before validating the equation.
The Pattern:
Every channel has economics. Without tracking them, you over-invest in losers and under-invest in winners.
Track Per Channel:
The Decision Framework:
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.
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:
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:
Common Mistake:
Assuming users will read documentation. They won't. They'll click around for 5 minutes, and if nothing works, they leave.
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):
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.
The Pattern:
Forecasts are always wrong. Plans are still valuable because they force thinking and create accountability.
Model Three Scenarios:
Baseline (current trajectory continues):
Upside (if all growth initiatives execute):
Downside (if key channels fail):
Use This For:
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).
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.
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 viableCAC < (LTV × margin)?
├─ No → Kill within 4 weeks
└─ Yes → 90-day retention > 60%?
├─ No → Optimize (improve activation/onboarding)
└─ Yes → Scale aggressively (3x budget)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.
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
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
Just SKILL.md in skills/gtm-product-led-growth of github/awesome-copilot.
Open the folder on GitHubat commit 82701c2
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gtm Product Led Growth this skillgithub/awesome-copilot | 40k | 1 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Marketing PlanNexus-JPF/note-companion | 870 | 5 repos | ~5.2k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Jaredrhod Marketingjaredrhod/ai-marketing-skills | 282 | — | ~584 | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Traffic Acquisitionvivy-yi/xiaohongshu-skills | 478 | 1 repos | ~4k | Automated safety check: Pass | None |
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
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…
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
jaredrhod/ai-marketing-skills
Run any marketing task the way jaredrhod actually runs it. An agent skill from jaredrhod/ai-marketing-skills.
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…
nexscope-ai/Amazon-Skills
Comprehensive product research and opportunity analysis for Amazon sellers.
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
github/awesome-copilot
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.
github/awesome-copilot
Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.
github/awesome-copilot
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
github/awesome-copilot
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.
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Categories
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.
Gtm Product Led Growth fits situations like: deciding PLG vs sales-led; optimizing activation; driving freemium conversion; building growth equations.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Gtm Product Led Growth is instructions for the agent only.
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.
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.
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.
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.
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.
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.