building-team-culture

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill building-team-culture
0 commentsdiscussion
summary

Team culture frameworks drawn from 138 product leaders at startups through Google and Airbnb.

  • Focuses on articulating existing culture rather than inventing new values; helps identify behaviors in high performers and document what already works
  • Emphasizes culture as a decentralized decision-making tool for remote and distributed teams, enabling sound choices when leadership isn't present
  • Covers psychological safety, trust-building, and feedback loops as foundations for organizational
skill.md

Building Team Culture

Help the user build and sustain high-performing team culture using frameworks from 138 product leaders who have shaped cultures at companies from startups to Google and Airbnb.

How to Help

When the user asks for help with team culture:

  1. Understand the context - Ask about team size, stage, remote vs in-person, and what triggered the culture question
  2. Diagnose the current state - Identify whether the issue is definition, communication, or enforcement of culture
  3. Focus on articulation over creation - Help them describe what's already working rather than inventing new values
  4. Design for decentralized decisions - Ensure culture can guide behavior when leadership isn't present

Core Principles

Articulate, don't create

Dharmesh Shah: "Culture actually already exists... what I'm really trying to do is kind of describe the culture that's there. It's not creating culture, it's articulating the culture." Document the attributes of people who make others happy and successful.

Culture is for when the boss isn't around

Chip Conley: "Culture is what happens around here when the boss is not around. The more distributed a company, the more culture is important." Use culture as a decentralized decision-making guide, especially for remote teams.

Replace management with coaching

Cam Adams: "We don't really have managers, but everyone at Canva has a coach. They're constantly working with you to look at your skills, but also when it might be time to move on to the next level." Coaches focus on skill development and career trajectory, not task oversight.

Earn trust before inflicting change

Katie Dill: "It can be hard to bring feedback forward like that. So it was an extremely valuable learning experience. I took from that to then immediately shift how I was operating." Prioritize listening over "coming in swinging" when joining a new team.

Challenge sacred cows to cure stagnation

Kayvon Beykpour: "We wanted to change the lack of ambition, the lack of creativity, the lack of customers feeling that the product had changed at all." Identify and challenge cultural artifacts that prevent product evolution.

Use culture as a talent magnet

Chip Conley: Culture attracts the right people and repels the wrong ones. Prioritize in-person gatherings for remote teams to reinforce cultural cues that can't be transmitted digitally.

Make culture a living document

Dharmesh Shah: Create a "Culture Code" that acts as an operating system for the company. Update it as you learn what actually works versus what sounds good.

Psychological safety enables feedback

Katie Dill: Building trust through active listening and empathy is the foundation for organizational change. Teams won't give honest feedback if they don't feel safe.

Questions to Help Users

  • "What behaviors do you see in your highest performers that you wish everyone exhibited?"
  • "When has someone made a decision you disagreed with but couldn't fault their reasoning?"
  • "What happens when someone fails publicly on your team?"
  • "How do new hires learn 'how things work around here'?"
  • "What decision would be made differently if you weren't in the room?"

Common Mistakes to Flag

  • Inventing aspirational values - Culture documents should describe what already works, not what you wish were true
  • Values without behaviors - "We value innovation" is meaningless without specific examples of what that looks like in practice
  • Over-engineering for small teams - Startups need shared understanding, not formal culture playbooks
  • Ignoring the distributed challenge - Remote teams need explicit cultural transmission that co-located teams get implicitly
  • Leadership-culture mismatch - Functional orgs require active leadership tiebreaking; if the CEO is hands-off, culture can't fill the gap

Deep Dive

For all 212 insights from 138 guests, see references/guest-insights.md

Related Skills

  • Writing Job Descriptions
  • Conducting Interviews
  • Evaluating Candidates
  • Onboarding New Hires
how to use building-team-culture

How to use building-team-culture on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add building-team-culture
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill building-team-culture

The skills CLI fetches building-team-culture from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/building-team-culture

Reload or restart Cursor to activate building-team-culture. Access the skill through slash commands (e.g., /building-team-culture) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.832 reviews
  • Michael Rahman· Dec 28, 2024

    Keeps context tight: building-team-culture is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Evelyn Anderson· Dec 8, 2024

    Registry listing for building-team-culture matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Maya Bhatia· Nov 23, 2024

    Useful defaults in building-team-culture — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Advait Robinson· Nov 19, 2024

    building-team-culture has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Fatima Bansal· Oct 14, 2024

    I recommend building-team-culture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Advait Choi· Oct 10, 2024

    Solid pick for teams standardizing on skills: building-team-culture is focused, and the summary matches what you get after install.

  • Oshnikdeep· Sep 25, 2024

    building-team-culture is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Tariq Choi· Sep 25, 2024

    building-team-culture fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ren Harris· Sep 1, 2024

    We added building-team-culture from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Fatima Choi· Aug 20, 2024

    building-team-culture fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 32

1 / 4