Token导航 LogoToken导航

Agent Skill · 研究检索

team-effectiveness(团队效能)

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

team-effectiveness 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 67,317。

总安装 247周安装 10GitHub Stars 61下载 78核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

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

适用于团队绩效评估、效率优化或成果度量等分析场景。支持多宿主环境,便于在不同 AI 工具间迁移使用。

来源仓库内路径:skills/team-effectiveness

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/melodic-software/claude-code-plugins --skill t…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

team-effectiveness 怎么安装?

在终端执行 npx skills add https://github.com/melodic-software/claude-code-plugins --skill team-effect…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

team-effectiveness 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

team-effectiveness 需要什么权限?

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

team-effectiveness 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

team-effectiveness 用的人多吗?

公开数据是累计安装 247 次,近一周安装 10 次,下载 78 次,GitHub 61 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

team-effectiveness 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
team-effectiveness

团队效能 · 本页

24761只读MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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

平台分布

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