Team Culture logo

Team Culture

OrganizationPopular
RefoundAI
team-culture

Help users design and maintain a high-performing culture by balancing radical transparency, psychological safety, and a relentless focus on customer delight.

Overview

PublisherRefoundAI
Repositorylenny-skills
Skill nameteam-culture
Stars
1.4K
Forks
175
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by RefoundAI on GitHub. Read the source before you install it.

Installation

Install the Team Culture AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/RefoundAI/lenny-skills/tree/main/skills/team-culture
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/RefoundAI/lenny-skills.git /tmp/lenny-skills
mkdir -p .claude/skills
cp -r /tmp/lenny-skills/skills/team-culture .claude/skills/team-culture
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Team Culture in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Team Culture on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Team Culture is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Building High-Performing Team Culture

Establish a culture of ownership, transparency, and intensity to drive long-term product success.

Help the user with building high-performing team culture using insights from 26 guests and posts across Lenny's Podcast and Newsletter.

How to Help

  1. Audit Cultural DNA - Help the leader analyze their current team dynamics and founder strengths to identify the inherent traits that define their culture.
  2. Define Actionable Values - Guide the user in drafting team values that include specific behavioral trade-offs rather than generic aspirational statements.
  3. Design Team Rituals - Suggest specific rituals for building trust, sharing work, and celebrating wins based on the team's specific remote or in-person setup.
  4. Diagnose Intensity Gaps - Assist the leader in identifying where organizational velocity or accountability is slipping and provide scripts for correcting those teams.

Core Principles

Results Over Popularity

Alisa Cohn: "They're trying now to be the leader who everyone loves, but what really needs to happen very often is, we need to drive towards results. This employee continuing to not really do a great job at their job, you don't want to push them because you don't want to upset them. You don't want to give them difficult feedback, so you're just going to keep hoping it works out. Ultimately, that leads to the demise of your company."

High-performing leaders must prioritize organizational results and performance standards over the desire to be liked by every individual. Avoiding difficult feedback to preserve popularity ultimately jeopardizes the long-term survival of the company.

Radical Business Transparency

Daniel Lereya: "We really have an approach of very radical transparency about everything. Before we went public, we actually shared every bit of information with our employees. Instead of demoralizing people, I think that this is something that gives them a sense of deep partnership."

Sharing core business financials and strategy creates a sense of deep partnership between leadership and employees. When everyone has full context, they are empowered to solve problems independently as owners.

Fanatical Customer Love

Jag Duggal: "When there are hard decisions to be made, we bias in favor of the customer. The customer's love, will they want to tell their friends, and neighbors, and family about it? And so I think that's the heart of it."

High-growth cultures are fueled by a commitment to customer delight that outweighs short-term operational compromises. Leaders should bias decision-making in favor of the user emotional experience over local convenience.

Low-Stakes Psychological Safety

Megan Cook: "So we divided the team into these smaller groups for peer feedback groups and the idea is that they meet every two weeks or so, somebody brings something that's in a pretty rough draft that they want to get reviewed and then everyone's expected to give feedback. And because we've got people in there who are different leadership levels, it's a really good opportunity to model the kind of feedback that's helpful and the culture there is one of everyone lifting that person up to make their work stronger."

To move fast, teams need low-stakes environments where they can share rough, early-stage work. Normalizing the presentation of 'unfinished' drafts helps catch directional errors early and builds collective confidence.

Comfort as a Failure Signal

Matt MacInnis: "If you want to be in the 99th percentile in terms of outcomes, it's going to be really difficult. You got to sort of remind people that if they ever find themselves in the comfort zone at work, they are definitely making a mistake. It's supposed to be really fricking exhausting."

Top-tier success requires a culture that views staying in the comfort zone as a strategic mistake. Exhaustion and high pressure are often necessary precursors to 99th-percentile progress.

Values as Explicit Trade-offs

Patrick Campbell: "I think really defining that in your values, and values aren't values unless there's an actual trade-off. And so we had things like optimize for the long-term. There's a clear trade-off when we optimize for the long-term, you probably give up short-term revenue."

Authentic values must involve clear trade-offs where one positive behavior is prioritized over another. This makes the values useful for decision-making rather than just being decorative plaques.

Templates & Frameworks

  • Three Criteria for Good Values (Will Larson) - A litmus test for evaluating whether company/team values will actually be useful: they must be honest, applicable, and reversible.
  • Miro's Product Team Rituals (How Miro builds product) - Four recurring team rituals that build culture, drive innovation, and foster cross-functional learning
  • BB Time (Brené Brown Vulnerability Segment) (Ideal sprint length, designer vs. PM roles, running PM team meetings, running post-mortems, best product/executive coaches, and much more) - A meeting segment where team members vulnerably share what feels hard, fostering psychological safety and early blocker identification
  • Life Story Friday Ritual (How Notion builds product) - A weekly team-building ritual where one team member shares their personal life story over Friday lunch, serving as a 'working with me' guide through personal na
  • Context, No Control (Ray Cao) - TikTok's core operating principle where employees are given full business context and encouraged to think like business owners across the whole business problem
  • Airbnb's Three Ingredients of Strong Culture (What Seven Years at Airbnb Taught Me About Building a Business) - A framework for building company culture with three key components.
  • Team Culture Building Tactics (How to ship like a startup) - Practical tactics for building cult-like team culture that drives execution
  • Seven Product Principles for Building Great Products (How Ramp builds product) - Ramp's core product philosophy covering speed, empowerment, selling, first principles, bets, simplicity, and culture

See references/artifacts.md for the full list with details.

Questions to Help Users

  • "What are the specific trade-offs your team makes when following your core values?"
  • "How often do your engineers directly observe users struggling with your product friction?"
  • "What rituals do you have in place to normalize sharing rough, early-stage work?"
  • "In what ways are you sharing core business financials or strategy with the entire team?"
  • "What is the 'Day One' mentality you are trying to preserve as you scale?"
  • "When was the last time you admitted a mistake or a gap in understanding to your team?"

Common Mistakes to Flag

  • Prioritizing popularity over performance - Leaders who fear being disliked often avoid the difficult feedback necessary for maintaining high organizational standards.
  • Defining values without trade-offs - Generic values like 'integrity' provide no guidance for difficult decisions where two positive outcomes are in conflict.
  • Relying on extrinsic motivators for morale - Visible product progress and shipping momentum are more effective at sustaining spirits during downturns than speeches or perks.
  • Siloing customer support - When engineers and designers are shielded from customer struggle, they lose the empathy required to build truly great products.

Deep Dive

For all 47 sourced insights from 26 guests, see references/guest-insights.md

Related Skills

  • Hiring Product Talent
  • Interviewing Evaluating Candidates
  • Org Design
  • Building Growth Team

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Team Culture AI skill do?

Help users design and maintain a high-performing culture by balancing radical transparency, psychological safety, and a relentless focus on customer delight.

Why use Team Culture on TypingMind?

Because you install it once and use it with any model. Team Culture is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Team Culture in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RefoundAI/lenny-skills/tree/main/skills/team-culture. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Team Culture?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Team Culture?

As many as you like. As long as a model supports skills, you can use Team Culture with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Team Culture AI skill free?

Yes. It is published on GitHub by RefoundAI under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇