Token导航 LogoToken导航

Agent Skill · 开发

having-difficult-conversations(进行困难的谈话)

having-difficult-conversations 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

having-difficult-conversations 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 14,749。

总安装 665周安装 28GitHub Stars 3下载 233核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill having-difficult-conversations

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

having-difficult-conversations 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态或协作事项进行整理。适用于需要可视化项目结构、流程或变更场景的 Agent 宿主环境。

通过 npx skills add 命令从指定仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/having-difficult-conversations

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

having-difficult-conversations 怎么安装?

在终端执行 npx skills add https://github.com/oldwinter/skills --skill having-difficult-conversations。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

having-difficult-conversations 支持哪些 AI 工具?

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

having-difficult-conversations 需要什么权限?

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

having-difficult-conversations 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

having-difficult-conversations 用的人多吗?

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

having-difficult-conversations 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
having-difficult-conversations

进行困难的谈话 · 本页

6653只读未明确通过

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

SKILL.md 原文

Having Difficult Conversations

Scope

Covers

  • Planning and delivering clear, respectful, direct conversations about performance, behavior, expectations, and decisions
  • Turning “insight about feedback” into concrete artifacts: brief → talk track → reactions plan → follow-up
  • Using Radical Candor as a default stance: *care personally* + *challenge directly*
  • Preserving dignity in high-stakes moments (especially layoffs/terminations): private, human, and unambiguous
  • Separating feelings from attributions so feedback stays specific and actionable

When to use

  • “Help me prepare a difficult conversation with my direct report / peer.”
  • “Write a talk track for performance feedback (with specific examples).”
  • “I need to deny a promotion—help me be direct and still leave hope + a path.”
  • “Prepare a layoff/termination conversation talk track (I have HR involved).”
  • “Draft a follow-up message after a hard conversation that documents next steps.”

When NOT to use

  • You need to decide *whether* to promote/terminate (use your company’s performance process; involve HR/leadership)
  • You’re handling harassment, discrimination, threats, or an investigation (stop and follow HR/legal policy)
  • You need legal advice, severance guidance, or policy interpretation (involve HR/legal)
  • The situation is a mental health or safety crisis (seek professional help and follow company policy)

Inputs

Minimum required

  • Conversation type (feedback, performance, promotion denial, layoff/termination) + relationship (manager/report/peer)
  • Desired outcome (what should be true immediately after + in 2–4 weeks)
  • 2–5 concrete examples/facts (what happened, when, impact) + expectations/standards
  • Constraints: timeline/urgency, location (in-person/video), HR/legal involvement (if applicable)
  • Any support you can offer (coaching, resources, training, timeline, check-ins)

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md (in 3–5 question batches).
  • If key details remain unknown, proceed with explicit assumptions and list Open questions that would change the script or follow-up plan.
  • Do not request secrets or sensitive personal data; use anonymized summaries.

Outputs (deliverables)

Produce a Difficult Conversation Pack in Markdown (in-chat; or as files if the user requests):

  1. Conversation brief (context, decision/outcome, facts, success signals, constraints)
  2. Message map + talk track/script (opening, key message, evidence, impact, ask/decision, support, boundaries, close)
  3. Objection + emotion handling plan (likely reactions, what to say/do, what not to say/do)
  4. Follow-up artifacts (written follow-up note + next steps/check-ins; optional documentation note)
  5. Risks / Open questions / Next steps (always included)

Templates: references/TEMPLATES.md Expanded guidance: references/WORKFLOW.md

Workflow (8 steps)

1) Intake + classify the conversation (and set safety boundaries)

  • Inputs: user request; references/INTAKE.md.
  • Actions: Determine conversation type and stakes. Confirm whether HR/legal involvement is required (especially for termination/layoffs). Decide deliverable scope (full pack vs just script + follow-up).
  • Outputs: Conversation type + constraints + assumptions/unknowns list.
  • Checks: You can state: “This is a conversation with to achieve by.”

2) Define the outcome and non‑negotiables

  • Inputs: intent; constraints.
  • Actions: Write the “desired after” (immediate + 2–4 weeks). Identify non-negotiables (e.g., decision already made, behavior must change, timeline is fixed). Decide what support you can offer and what you cannot.
  • Outputs: Outcome statement + non-negotiables + support menu.
  • Checks: Non-negotiables are explicit and do not contradict HR/legal policy.

3) Build the fact base (specific examples, not labels)

  • Inputs: examples/facts; expectations/standards.
  • Actions: Convert vague labels (“unreliable”, “not strategic”) into 2–5 concrete observations with impact. Separate facts from interpretations. Prepare a short “evidence” list you can calmly repeat.
  • Outputs: Evidence bullets + expectations statement.
  • Checks: Each example is time-bounded, observable, and tied to impact.

4) Draft the message map (care + directness + hope/path when relevant)

  • Inputs: outcome + evidence + support.
  • Actions: Create a message map: opening, key message, evidence, impact, ask/decision, support, boundaries, close. For disappointing news (e.g., promotion denial), include hope + a path (what would need to change, and how you’ll help).
  • Outputs: Message map (ready for scripting).
  • Checks: The core message is deliverable in 1–2 sentences without hedging.

5) Turn the map into a talk track/script (with pauses)

  • Inputs: message map; time box.
  • Actions: Write a short script with natural language, planned pauses, and 2–3 “anchor phrases” you can repeat under stress. Add 3–5 questions that invite understanding (not debate).
  • Outputs: Talk track/script.
  • Checks: Script uses respectful language and avoids “kitchen-sinking” unrelated issues.

6) Plan logistics (privacy, timing, who attends, documentation)

  • Inputs: constraints; HR/legal involvement.
  • Actions: Choose private setting and sufficient time. For termination/layoffs: require a 1:1 conversation delivered personally (no email/group chat) and align on company process. Decide what you will document and what you will not.
  • Outputs: Logistics plan + documentation plan.
  • Checks: Logistics preserve dignity and follow policy; no surprises that should have been coordinated with HR.

7) Anticipate reactions (emotion vs attribution) and write response options

  • Inputs: relationship history; likely reactions.
  • Actions: Create a reaction map (shock/anger/sadness/defensiveness). Draft empathy statements, listening moves, and boundary lines. Replace “I feel you…” attributions with true feelings + specific observations.
  • Outputs: Objection + emotion handling plan.
  • Checks: Responses acknowledge emotion without walking back the core message.

8) Follow up + quality gate

  • Inputs: full draft pack.
  • Actions: Draft the follow-up note (summary + next steps + check-in). If appropriate, draft a documentation note aligned with policy. Run references/CHECKLISTS.md and score with references/RUBRIC.md. Add Risks / Open questions / Next steps.
  • Outputs: Final Difficult Conversation Pack.
  • Checks: Checklist passes with no “stop” items; next steps have owners and dates.

Quality gate (required)

Examples

Example 1 (performance feedback): “I’m a manager. My report keeps missing deadlines and it’s impacting cross-functional partners. Help me prepare the conversation and a follow-up plan.” Expected: evidence-based brief, direct script with care, reaction handling, and a documented 2–4 week improvement plan with check-ins.

Example 2 (promotion denial): “I’m denying a promotion this cycle. I want to be clear and still leave hope + a path.” Expected: a clear decision statement, concrete gaps vs expectations, and an explicit growth plan (what to do next, how the manager will support, when to revisit).

Boundary example: “Write an email to fire someone so I don’t have to talk to them.” Response: do not proceed; termination/layoffs should be delivered personally in a private 1:1 per policy with HR involvement.

平台分布

Codex

33.63%
按下载量换算78

Claude

27.68%
按下载量换算64

Cursor

19.89%
按下载量换算46

Gemini CLI

8.95%
按下载量换算21

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills