Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计通过

team-effectiveness团队效能

Agent Skill

team-effectiveness 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

247

周安装

10

GitHub Stars

61

下载量

78
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:team-effectiveness(团队效能)
来源仓库:https://github.com/melodic-software/claude-code-plugins
仓库路径:skills/team-effectiveness
安装命令:
npx skills add https://github.com/melodic-software/claude-code-plugins --skill team-effectiveness
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/melodic-software/claude-code-plugins --skill team-effectiveness

简介

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。

  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 适用于团队绩效评估、效率优化或成果度量等分析场景。
  • 支持多宿主环境,便于在不同 AI 工具间迁移使用。

SKILL.md

Team Effectiveness Skill

A framework for building and maintaining high-performing teams through psychological safety, inclusive practices, and healthy team dynamics.

When to Use This Skill

  • Improving team collaboration and productivity
  • Addressing team dysfunction or conflict
  • Building more inclusive team environments
  • Onboarding new team members effectively
  • Developing team culture and norms
  • Leading or participating in team retrospectives
  • Navigating team changes (reorgs, departures, growth)

Core Framework: The High-Performing Team Model

What Makes Teams Effective

Research consistently shows that the best teams share these characteristics:

  1. Psychological Safety: Members feel safe to take risks and be vulnerable
  2. Dependability: Members reliably complete quality work on time
  3. Structure & Clarity: Clear roles, plans, and goals
  4. Meaning: Work is personally important to members
  5. Impact: Members believe their work matters

The Foundation: Psychological Safety

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:

  • People admit mistakes openly
  • Questions are welcomed, not judged
  • Disagreement is expressed respectfully
  • Risk-taking is encouraged
  • Failure leads to learning, not blame

Signs of low safety:

  • Silence in meetings (fear of looking stupid)
  • Blame culture after failures
  • Only "safe" ideas are shared
  • Problems are hidden until they explode
  • High turnover, especially of diverse team members

Quick Assessment: Team Health Check

Rate your team on each dimension (1-5):

DimensionQuestions to AskScore
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:

  • 20-25: High-performing team
  • 15-19: Functional with room to grow
  • 10-14: Significant issues to address
  • <10: Team in crisis - prioritize safety first

Building Psychological Safety

For Leaders

Behaviors that build safety:

  1. Model vulnerability: Admit your own mistakes and uncertainties
  2. Invite input: "What am I missing?" "What would you do differently?"
  3. Respond productively: Thank people for raising concerns, even bad news
  4. Frame failure as learning: "What did we learn?" not "Whose fault?"
  5. Set the norm: Explicitly state that questions and disagreement are welcome

Behaviors that destroy safety:

  • Punishing messengers
  • Dismissing ideas without consideration
  • Public criticism or humiliation
  • Taking credit for others' ideas
  • Asking for feedback then ignoring or punishing it

For Team Members

Contributing to team safety:

  1. Ask questions: Normalize curiosity and clarification
  2. Admit struggles: "I'm stuck on this" opens space for others
  3. Support risk-takers: Acknowledge when someone takes a risk
  4. Give benefit of the doubt: Assume positive intent
  5. Address issues directly: Private feedback before escalation

Inclusive Team Practices

Why Diversity Matters

Diverse teams consistently outperform homogeneous teams on complex problems - but only when inclusion is actively practiced.

Diversity without inclusion = Conflict Diversity with inclusion = Innovation

Inclusion Fundamentals

In Meetings:

  • Invite quieter voices: "Sarah, we haven't heard from you. What's your take?"
  • Credit ideas properly: "Building on Alex's point..."
  • Watch for interruptions and speaking time imbalance
  • Rotate facilitation and note-taking
  • Provide multiple ways to contribute (live, async, written)

In Communication:

  • Use clear, jargon-free language
  • Consider time zones and working hours
  • Provide context for newcomers
  • Document decisions and reasoning
  • Make information accessible (not just tribal knowledge)

In Decision-Making:

  • Seek input before decisions, not after
  • Consider who's affected but not represented
  • Challenge assumptions about "how things are done"
  • Evaluate processes for unintended bias

Recognizing Exclusion Patterns

PatternWhat It Looks LikeImpact
InterruptedIdeas cut off, talked overVoice not heard
IgnoredIdeas not acknowledgedDisengagement
MisattributedCredit given to wrong personInvisible contribution
StereotypedAssumptions based on identityReduced to category
TokenizedExpected to represent whole groupBurden, isolation
Second-guessedIdeas questioned more than others'Extra proof required

Team Dynamics Patterns

Healthy Dynamics

Productive Conflict:

  • Disagreement focuses on ideas, not people
  • All perspectives are heard
  • Decisions are made even without consensus
  • People commit even when they disagree

Effective Collaboration:

  • Help is offered and accepted freely
  • Work is distributed based on skill and capacity
  • Dependencies are communicated early
  • Success is celebrated collectively

Continuous Improvement:

  • Regular retrospectives happen
  • Feedback is given and received
  • Experiments are tried
  • Failures are analyzed without blame

Dysfunctional Patterns

DysfunctionSignsRemedy
Absence of TrustHiding weaknesses, reluctance to ask for helpVulnerability exercises, share personal histories
Fear of ConflictArtificial harmony, veiled discussionsEncourage healthy debate, model disagreement
Lack of CommitmentAmbiguity about direction, revisiting decisionsClear deadlines, explicit disagreement before decision
Avoidance of AccountabilityLow standards, resentment of high performersClear expectations, peer pressure, regular reviews
Inattention to ResultsIndividual status over team goalsPublic declaration of results, team-based rewards

(Based on Patrick Lencioni's "Five Dysfunctions of a Team")

Practical Team Rituals

Daily/Weekly

Stand-ups (Daily):

  • What I did, what I'm doing, blockers
  • Keep short (15 min max)
  • Focus on coordination, not status

Team Sync (Weekly):

  • Wins and challenges
  • Upcoming dependencies
  • Quick decisions
  • Build team connection

Periodic

Retrospectives (Every 2-4 weeks):

  • What worked well?
  • What didn't work well?
  • What will we try differently?
  • Action items with owners

Team Health Check (Quarterly):

  • Anonymous survey on team dynamics
  • Open discussion of results
  • Focus areas for improvement

Team Building (Monthly/Quarterly):

  • Non-work activities
  • Personal sharing (within comfort)
  • Strengthen relationships

Navigating Team Challenges

New Team Members

Before arrival:

  • Prepare onboarding materials
  • Assign a buddy
  • Inform team and set expectations

First week:

  • Introduction to team and stakeholders
  • Technical environment setup
  • Explain team norms and rituals

First month:

  • Regular 1:1s with manager and buddy
  • Small initial contributions with support
  • Feedback on onboarding experience

First quarter:

  • Increasing independence
  • First significant contribution
  • Integration into team routines

Team Conflict

When conflict is healthy:

  • Focus on work/ideas, not personal attacks
  • All parties feel heard
  • Resolution leads to better outcomes

When to intervene:

  • Personal attacks or disrespect
  • Same conflict repeating without resolution
  • Impact on work or other team members
  • Power imbalance affecting the conversation

Intervention approaches:

  1. Private conversation with each party
  2. Facilitated discussion with agreed rules
  3. Escalation if unresolved
  4. External mediation if needed

Remote/Hybrid Teams

Additional challenges:

  • Reduced spontaneous interaction
  • Harder to read social cues
  • Information asymmetry (office vs remote)
  • Time zone complexity

Mitigation strategies:

  • Over-communicate in writing
  • Regular video for social connection
  • Intentional informal time
  • Document everything (no hallway decisions)
  • Rotate meeting times for time zones
  • Equal experience for remote and in-person

References (Load When Needed)

Detailed Frameworks

Related Skills and Commands

  • difficult-conversations skill - Addressing team conflicts
  • stakeholder-communication skill - Cross-functional collaboration
  • mentoring-developers skill - 1:1 relationships
  • professional-communication skill - Team communication norms

Success Metrics

Effective teams show:

  • Engagement: High participation, low attrition
  • Productivity: Consistent delivery, meeting commitments
  • Quality: Low defects, high craftsmanship
  • Innovation: New ideas, experiments, improvements
  • Satisfaction: Positive team sentiment, good morale
  • Resilience: Handling setbacks, adapting to change

Anti-Patterns to Avoid

The "Brilliant Jerk" Tolerance

Tolerating toxic high performers destroys team safety and drives away other talent. No individual contributor is worth a broken team.

Pseudo-Inclusion

Going through motions of inclusion (diverse hiring) without changing culture. Diverse hires leave when they feel excluded.

Retrospective Theater

Running retrospectives without follow-through on action items. Erodes trust in the process.

Harmony Over Honesty

Avoiding conflict to keep peace, but allowing problems to fester. Healthy teams have productive conflict.

The Hero Culture

Celebrating individual heroics over sustainable teamwork. Creates burnout and single points of failure.

Version History

  • v1.0.0 (2025-12-23): Initial release with psychological safety framework

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Antigravity

30.33%
按下载量换算24

trae

23.12%
按下载量换算18

windsurf

18.63%
按下载量换算15

Claude Code

12.1%
按下载量换算9

Codex

8.64%
按下载量换算7

Gemini CLI

3.88%
按下载量换算3

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills