
Community Building
Design and grow user communities using Lenny guest playbooks—from seed groups and norms to ubiquity that supports expansion and retention.
Overview
Community Building is an agent skill most often used in Grow (also Launch, Validate) that applies Lenny-guest community tactics for norms, seed groups, and advocacy-led growth.
Install
npx skills add https://github.com/refoundai/lenny-skills --skill community-buildingWhat is this skill?
- Curated insights: 18 guests and 30 mentions on community building
- Internal 'seed crystal' groups with explicit collaborative norms (e.g. yes-and debate salons)
- Tactics for low-stakes ideation filters, wonder-statement critiques, and facilitator reinforcement
- Enterprise motion angle: community-driven ubiquity and name recognition enabling upmarket moves
- Applicable to external user communities and internal strategy salons
- 18 guests, 30 mentions
Adoption & trust: 1.4k installs on skills.sh; 1k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You have scattered users but no repeatable community motion—norms, facilitation, or recognition—that turns engagement into retention and distribution.
Who is it for?
Solo founders running founder-led communities, template ecosystems, or dev-tool niches where members co-create value and word of mouth matters.
Skip if: Teams that only need paid ads or SEO playbooks with zero community operations bandwidth.
When should I use this skill?
Starting or scaling a user or internal community, setting collaboration norms, or using community pull for distribution and upmarket motion.
What do I get? / Deliverables
You get actionable community patterns (seed groups, yes-and norms, facilitator plays, upmarket ubiquity stories) tailored in conversation to your product stage.
- Community operating principles adapted from guest insights
- Facilitation and scaling tactics for seed-then-expand motion
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Community compounding is shelved under grow because the skill targets engagement, recognition, and lifecycle motion that turns users into advocates. Lifecycle fits rituals, norms, facilitation, and long-term member behavior—not one-off launch posts.
Where it fits
Define norms and facilitation for a small power-user group before opening a public community.
Plan advocate-led launches using ubiquity and shareable member creations.
Test a narrow community engagement loop before scaling marketing spend.
How it compares
Use as a community strategy reference skill—not a hosted forum product or automation MCP for moderation.
Common Questions / FAQ
Who is community-building for?
Indie builders growing SaaS, content, or tool communities who want Lenny-podcast community tactics inside their coding agent.
When should I use community-building?
During grow lifecycle planning, at launch distribution when leaning on advocates, or in validate when testing a narrow community-led wedge.
Is community-building safe to install?
It provides textual guidance only; review the Security Audits panel on this Prism page for the parent Lenny-skills package before install.
SKILL.md
READMESKILL.md - Community Building
# Community Building - All Guest Insights *18 guests, 30 mentions* --- ## Alex Komoroske *Alex Komoroske* > "I created a secret group that I called Navel Gazers... you set the norms very explicitly and say, 'This is a collaborative debate environment. This is only yes, and.'... This sounds by the way very non-rigorous... It turns out there's limited amounts of time and so people will choose to build on the things they find most interesting." **Insight:** Internal 'Nerd Clubs' or strategy salons create high-value insights by using 'yes, and' norms to filter for the most resonant ideas in a low-stakes environment. **Tactical advice:** - Start with a small 'seed crystal' of highly engaged people to establish norms before scaling. - Use 'I wonder' statements to offer critiques without triggering defensive reactions. - Actively facilitate by encouraging people to share their ideas in the group and providing positive reinforcement (emojis, notes). *Timestamp: 00:49:17* ## Camille Ricketts *Camille Ricketts* > "it's when your community helps you achieve such ubiquity and such name recognition that it actually allows you to start moving upmarket into the enterprise. And I know that might be very specific to enterprise oriented companies, but that's how we defined it at Notion was the fact that so many people were talking about this, sharing what they had built about it, honestly starting businesses of their own around it to formalize the relationship with teams that I think it de-risked Notion as a choice for a lot of companies" **Insight:** Community-led growth creates ubiquity and name recognition that de-risks the product for enterprise buyers. **Tactical advice:** - Focus on achieving ubiquity to move upmarket - Encourage users to build their own businesses or formalize relationships around your product *Timestamp: 00:13:09* --- > "I think that community lends itself particularly well if you have something that your product creates that people want to share because it exhibits something about themselves. So at Notion it was templates or even people just creating their own workspaces and being really excited to show them off. So Notion really benefited from being a creative product, but the same is true of Figma or Canva or any of these where showing people what it is that you've created is an aspirational thing to do." **Insight:** Community thrives when a product has an 'atomic unit of sharing' that allows for self-expression or aspirational display. **Tactical advice:** - Identify the 'atomic unit of sharing' in your product - Enable users to show off their creations to signal expertise or organization *Timestamp: 00:20:19* --- > "I would really urge people to sit down and really think carefully what is going to be more conducive to our long-term success? Is it going to be that ubiquity or is it going to be revenue now? And I think if we look at a lot of the companies that have been just wildly successful from the start, they're people who have pushed off maybe monetizing every little thing if it's going to really put a damper on that type of enthusiasm and momentum" **Insight:** Prioritize long-term ubiquity and word-of-mouth momentum over immediate monetization of every feature. **Tactical advice:** - Evaluate if organic word-of-mouth is more valuable than short-term revenue - Avoid over-monetizing early if it dampens community enthusiasm *Timestamp: 00:27:45* --- > "I would recommend highly not necessarily coming in with preconceived notions about what a community needs to look like. ... I think that some communities get built where people are like, okay, well we have this community and it's going to be this and this and this... As opposed to I think a lot of listening of the people who are actually participating." **Insight:** Avoid rigid, preconceived structures for community; instead, listen to active participants to shape the experience. **Tactical advice:** - Conduct one-on-one or small group Z