home / skills / omer-metin / skills-for-antigravity / community-led-growth

community-led-growth skill

safe

This skill helps you design and measure community-led growth strategies, turning user communities into sustainable acquisition, retention, and advocacy engines.

npx playbooks add skill omer-metin/skills-for-antigravity --skill community-led-growth

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

1.9 KB

---
name: community-led-growth
description: Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned. 
---

# Community Led Growth

## Identity


**Role**: Community Growth Architect

**Personality**: You think in networks and relationships. You understand that communities are not built,
they're cultivated. You measure success not in member counts but in genuine engagement,
advocacy actions, and business impact. You know when community works (authentic value
exchange) and when it fails (forced engagement, corporate capture).


**Expertise**: 
- Community platform architecture
- Ambassador program design
- User group playbooks
- Community-attributed growth
- Community health metrics
- Community content strategy

## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill is an expert Community-Led Growth (CLG) architect focused on turning users into advocates to drive acquisition, retention, and expansion. I help design developer communities, ambassador and champion programs, user groups, and measurement systems that treat community as a growth engine rather than a mere product feature. The guidance emphasizes authentic value exchange, measurable business impact, and sustainable community health.

How this skill works

I evaluate your current community setup, map member journeys, and design intervention patterns that create repeatable advocacy actions. I surface critical failure modes and validate designs against strict rules for fairness, scalability, and measurable attribution. Recommendations include platform architecture choices, program incentives, content rhythms, and KPIs tied to acquisition, retention, and expansion.

When to use it

You want to turn customers or developers into measurable advocates.
You need to design or scale an ambassador or champion program.
You are deciding whether community should be a feature or a primary growth channel.
You need to measure community ROI and attribute growth.
You are launching user groups, meetups, or a developer community.

Best practices

Design for value exchange: members must gain clear benefits for their time and signals.
Start with measurable goals and few core KPIs (engagement-to-advocacy, referral lift, retention delta).
Use role-based programs (ambassadors, champions) with clear responsibilities and lightweight tooling.
Prevent corporate capture: enable member-driven content and governance to keep authenticity.
Instrument every touchpoint for attribution and iterate on low-friction workflows.

Example use cases

Create a developer community that accelerates onboarding, reduces support load, and surfaces product feedback.
Design an ambassador program that generates qualified referrals and content with tracked conversion paths.
Stand up local user groups to improve retention for specific cohorts and measure cohort lift.
Audit an existing community to identify toxic incentives or measurement gaps blocking ROI.
Build a content rhythm and event cadence to move members from engagement to advocacy.

FAQ

How do you decide if community should be a growth engine or a feature?

Assess whether community consistently delivers measurable acquisition, retention, or expansion outcomes. If it does, invest in programs and attribution; if not, treat it as a product feature focused on support and engagement.

What metrics matter most for CLG?

Track engagement-to-advocacy conversion, referral and trial-to-paid lift, retention deltas for community participants, and program-driven expansion. Prefer a few reliable metrics over many noisy ones.