Team culture frameworks drawn from 138 product leaders at startups through Google and Airbnb.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbuilding-team-cultureExecute the skills CLI command in your project's root directory to begin installation:
Fetches building-team-culture from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate building-team-culture. Access via /building-team-culture in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
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.
When the user asks for help with team culture:
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.
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.
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.
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.
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.
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.
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.
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.
For all 212 insights from 138 guests, see references/guest-insights.md
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
Keeps context tight: building-team-culture is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for building-team-culture matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in building-team-culture — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
building-team-culture has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend building-team-culture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: building-team-culture is focused, and the summary matches what you get after install.
building-team-culture is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
building-team-culture fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added building-team-culture from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
building-team-culture fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 32