Stats
Actions
Tags
From soft-skills
Assesses and improves dev team effectiveness using psychological safety, dependability, clarity, meaning, and impact model. Includes health checks for collaboration, dysfunction, inclusivity, and culture.
How this skill is triggered — by the user, by Claude, or both
Slash command
/soft-skills:team-effectivenessThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
A framework for building and maintaining high-performing teams through psychological safety, inclusive practices, and healthy team dynamics.
A framework for building and maintaining high-performing teams through psychological safety, inclusive practices, and healthy team dynamics.
Research consistently shows that the best teams share these characteristics:
Psychological safety is the #1 predictor of team effectiveness (Google's Project Aristotle research).
Definition: The belief that you won't be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes.
Signs of psychological safety:
Signs of low safety:
Rate your team on each dimension (1-5):
| Dimension | Questions to Ask | Score |
|---|---|---|
| Safety | "Can I admit mistakes without fear?" | /5 |
| Dependability | "Can I count on teammates to deliver?" | /5 |
| Clarity | "Do I know what's expected of me?" | /5 |
| Meaning | "Does this work matter to me personally?" | /5 |
| Impact | "Does our work make a difference?" | /5 |
Interpretation:
Behaviors that build safety:
Behaviors that destroy safety:
Contributing to team safety:
Diverse teams consistently outperform homogeneous teams on complex problems - but only when inclusion is actively practiced.
Diversity without inclusion = Conflict Diversity with inclusion = Innovation
In Meetings:
In Communication:
In Decision-Making:
| Pattern | What It Looks Like | Impact |
|---|---|---|
| Interrupted | Ideas cut off, talked over | Voice not heard |
| Ignored | Ideas not acknowledged | Disengagement |
| Misattributed | Credit given to wrong person | Invisible contribution |
| Stereotyped | Assumptions based on identity | Reduced to category |
| Tokenized | Expected to represent whole group | Burden, isolation |
| Second-guessed | Ideas questioned more than others' | Extra proof required |
Productive Conflict:
Effective Collaboration:
Continuous Improvement:
| Dysfunction | Signs | Remedy |
|---|---|---|
| Absence of Trust | Hiding weaknesses, reluctance to ask for help | Vulnerability exercises, share personal histories |
| Fear of Conflict | Artificial harmony, veiled discussions | Encourage healthy debate, model disagreement |
| Lack of Commitment | Ambiguity about direction, revisiting decisions | Clear deadlines, explicit disagreement before decision |
| Avoidance of Accountability | Low standards, resentment of high performers | Clear expectations, peer pressure, regular reviews |
| Inattention to Results | Individual status over team goals | Public declaration of results, team-based rewards |
(Based on Patrick Lencioni's "Five Dysfunctions of a Team")
Stand-ups (Daily):
Team Sync (Weekly):
Retrospectives (Every 2-4 weeks):
Team Health Check (Quarterly):
Team Building (Monthly/Quarterly):
Before arrival:
First week:
First month:
First quarter:
When conflict is healthy:
When to intervene:
Intervention approaches:
Additional challenges:
Mitigation strategies:
difficult-conversations skill - Addressing team conflictsstakeholder-communication skill - Cross-functional collaborationmentoring-developers skill - 1:1 relationshipsprofessional-communication skill - Team communication normsEffective teams show:
Tolerating toxic high performers destroys team safety and drives away other talent. No individual contributor is worth a broken team.
Going through motions of inclusion (diverse hiring) without changing culture. Diverse hires leave when they feel excluded.
Running retrospectives without follow-through on action items. Erodes trust in the process.
Avoiding conflict to keep peace, but allowing problems to fester. Healthy teams have productive conflict.
Celebrating individual heroics over sustainable teamwork. Creates burnout and single points of failure.
npx claudepluginhub melodic-software/claude-code-plugins --plugin soft-skillsAssesses and improves team psychological safety using Edmondson's 7-item survey and evidence-based leader behaviors. For team leads wanting to increase speaking up, admitting mistakes, and productive disagreement.
Runs structured team health assessments across delivery, culture, process, and cross-functional dimensions. Use for surveys, retrospectives, or facilitation guides.
Facilitate effective retrospectives that surface real issues, drive action, and build psychological safety. Use at sprint end or after major initiatives.