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

difficult-workplace-conversations困难的职场对话

Agent Skill

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

总安装

85,536

周安装

3,636

GitHub Stars

1,726

下载量

29,952
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:difficult-workplace-conversations(困难的职场对话)
来源仓库:https://github.com/softaworks/agent-toolkit
仓库路径:skills/difficult-workplace-conversations
安装命令:
npx skills add https://github.com/softaworks/agent-toolkit --skill difficult-workplace-conversations
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/softaworks/agent-toolkit --skill difficult-workplace-conversations

简介

用于准备、交付和跟进具有挑战性的工作场所对话的结构化框架。

  • 三阶段方法,包括准备(澄清问题、检查情绪、考虑观点)、交付(中立开放、分享观点、积极倾听、寻求解决方案)和后续(记录协议、检查进度、维护关系)
  • 包括 SBI 模型(情境-行为-影响),用于在困难的对话之前构建反馈和管理自己情绪的指导
  • 涵盖特定对话类型:绩效反馈、冲突解决、敏感主题和接收反馈
  • 提供启动脚本、要避免的反模式以及对话需要管理层参与时的升级标准

SKILL.md

name
difficult-workplace-conversations
description
Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.
allowed-tools
Read, Glob, Grep

Difficult Conversations Skill

A structured framework for approaching challenging workplace conversations including conflicts, performance issues, sensitive feedback, and emotionally charged discussions.

When to Use This Skill

  • Preparing for a challenging conversation with a colleague
  • Addressing performance issues with a team member
  • Delivering difficult feedback to a peer or manager
  • Navigating conflict between team members
  • Discussing sensitive topics (salary, promotion, termination)
  • Handling emotional or defensive reactions
  • Following up after difficult discussions

Core Framework: Preparation-Delivery-Followup

Difficult conversations succeed or fail based on three phases:

Phase 1: Preparation (Before)

Purpose: Set yourself up for a productive conversation

  1. Clarify the Issue

- What specifically happened? (Observable facts only) - What is the impact? (On you, team, work) - What do you need to change?

  1. Check Your Emotions

- What am I feeling? Why? - Am I calm enough to have this conversation? - What might trigger me during this conversation?

  1. Consider Their Perspective

- How might they see this situation? - What constraints or pressures might they have? - What do they care about that I can acknowledge?

  1. Define Your Goal

- What outcome do I want? - What is the minimum acceptable result? - What am I willing to compromise on?

Phase 2: Delivery (During)

Purpose: Have the conversation effectively

  1. Open Neutrally

- Start with facts, not judgments - Express intent to understand, not accuse - Create psychological safety

  1. Share Your Perspective

- Describe behavior, not character - Focus on impact, not intention - Use "I" statements, not "you always"

  1. Listen Actively

- Ask clarifying questions - Acknowledge their viewpoint - Look for shared interests

  1. Seek Resolution

- Propose specific actions - Agree on next steps - Set check-in timeline

Phase 3: Followup (After)

Purpose: Ensure lasting resolution

  1. Document Agreements

- What was agreed? - Who does what by when? - How will you measure success?

  1. Check Progress

- Follow up as promised - Acknowledge improvements - Address continued issues promptly

  1. Maintain Relationship

- Separate issue from person - Rebuild trust over time - Watch for regression

Key Principles

Separate Impact from Intent

What happened: Observable behavior What I felt: Your emotional response What I assume: Their intention (often wrong)

Focus conversation on behavior and impact, not assumed intentions.

The SBI Model

Situation: When and where did this happen? Behavior: What specifically did they do/say? Impact: What was the effect on you, the team, or the work?

Managing Emotions

If You FeelBefore Acting
AngryWait 24 hours, write but don't send
HurtTalk to neutral party first
AnxiousPractice the conversation
DefensiveIdentify your contribution

When to Escalate

Escalate when:

  • Safety is at risk
  • Legal issues involved
  • Repeated conversations haven't worked
  • Power dynamics prevent resolution
  • You need documentation

Conversation Types

Performance Feedback

  • Lead with specific examples
  • Connect to expectations/standards
  • Focus on future improvement
  • Offer support and resources

Conflict Resolution

  • Hear both sides separately first
  • Identify underlying interests
  • Look for win-win solutions
  • Document agreements

Sensitive Topics

  • Choose private, neutral setting
  • Allow time for processing
  • Be direct but compassionate
  • Respect confidentiality

Receiving Feedback

  • Thank them for feedback
  • Ask clarifying questions
  • Don't defend immediately
  • Reflect before responding

References (Load When Needed)

Detailed Frameworks

See Also

  • feedback-mastery skill - SBI feedback model (overlaps but more feedback-focused)
  • professional-effective-communication skill - General communication patterns

Example Scenarios

Scenario 1: Addressing Missed Deadlines

**Issue:** Team member missed 3 deadlines in past month
**Impact:** Project delayed, others blocked
**Goal:** Understand root cause, agree on prevention plan

**Opening:** "I wanted to check in about the recent deliverables. I've noticed
the last three have come in past deadline, and I'd like to understand what's
happening and how we can address it together."

Scenario 2: Peer Conflict

**Issue:** Colleague publicly criticized your work in meeting
**Impact:** Embarrassed, trust damaged
**Goal:** Address behavior, rebuild working relationship

**Opening:** "I'd like to talk about what happened in yesterday's standup.
When you said my code 'missed obvious issues,' I felt called out in front
of the team. I'd like to understand your concerns and find a better way
to handle code quality feedback."

Scenario 3: Asking Manager for Raise

**Issue:** Feel underpaid relative to market/contribution
**Impact:** Demotivation, considering leaving
**Goal:** Discuss compensation, get timeline or adjustment

**Opening:** "I'd like to discuss my compensation. I've been here two years,
taken on the payments project leadership, and want to make sure my salary
reflects my contributions and the current market."

Anti-Patterns to Avoid

In Preparation

  • Scripting every word - You'll sound robotic; prepare themes, not scripts
  • Building a case - This isn't a trial; seek understanding, not winning
  • Waiting too long - Issues compound; address promptly

In Delivery

  • Starting with "You always..." - Triggers defensiveness immediately
  • Burying the lead - Get to the point; don't soften excessively
  • Asking leading questions - "Don't you think..." isn't asking

In Followup

  • Forgetting to check in - Without follow-up, nothing changes
  • Holding grudges - Issue resolved means relationship continues
  • Over-documenting - Not everything needs written record

Success Metrics

A successful difficult conversation:

  • Both parties feel heard
  • Specific actions are agreed
  • Relationship is preserved or improved
  • The issue doesn't recur (or has clear escalation)
  • Neither party is blindsided later

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

Claude Code

27.58%
按下载量换算8,261

Cursor

23.88%
按下载量换算7,153

Codex

18.82%
按下载量换算5,637

Gemini CLI

11.82%
按下载量换算3,540

OpenCode

8.32%
按下载量换算2,492

goose

3.88%
按下载量换算1,162

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills