Difficult Workplace Conversations logo

Difficult Workplace Conversations

OrganizationPopular
softaworks
difficult-workplace-conversations

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.

Overview

Publishersoftaworks
Repositoryagent-toolkit
Skill namedifficult-workplace-conversations
Stars
2.5K
Forks
226
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by softaworks on GitHub. Read the source before you install it.

Installation

Install the Difficult Workplace Conversations AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/softaworks/agent-toolkit.git /tmp/agent-toolkit
mkdir -p .claude/skills
cp -r /tmp/agent-toolkit/skills/difficult-workplace-conversations .claude/skills/difficult-workplace-conversations
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Difficult Workplace Conversations in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Difficult Workplace Conversations on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Difficult Workplace Conversations is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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?
  2. Check Your Emotions

    • What am I feeling? Why?
    • Am I calm enough to have this conversation?
    • What might trigger me during this conversation?
  3. 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?
  4. 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
  2. Share Your Perspective

    • Describe behavior, not character
    • Focus on impact, not intention
    • Use "I" statements, not "you always"
  3. Listen Actively

    • Ask clarifying questions
    • Acknowledge their viewpoint
    • Look for shared interests
  4. 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?
  2. Check Progress

    • Follow up as promised
    • Acknowledge improvements
    • Address continued issues promptly
  3. 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

markdown
**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

markdown
**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

markdown
**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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Difficult Workplace Conversations AI skill do?

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.

Why use Difficult Workplace Conversations on TypingMind?

Because you install it once and use it with any model. Difficult Workplace Conversations is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Difficult Workplace Conversations in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/softaworks/agent-toolkit/tree/main/skills/difficult-workplace-conversations. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Difficult Workplace Conversations?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Difficult Workplace Conversations?

As many as you like. As long as a model supports skills, you can use Difficult Workplace Conversations with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Difficult Workplace Conversations AI skill free?

Yes. It is published on GitHub by softaworks under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇