AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Difficult Conversation

skill-mohitagw15856-pm-claude-skills-difficult-conversation · by mohitagw15856

Prepare for and script a hard conversation — conflict, bad news, a boundary, an apology. Use when asked to prepare for a difficult conversation, address a conflict, deliver bad news, confront a colleague, or have a hard talk with a manager/report/peer. Produces a prep brief — the real goal, the other side's likely view, an opening line, the key points, anticipated reactions with responses, and th…

No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-mohitagw15856-pm-claude-skills-difficult-conversation

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-mohitagw15856-pm-claude-skills-difficult-conversation)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Difficult Conversation? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Difficult Conversation Skill

The conversations we avoid are usually the ones that matter most — and we botch them by winging it or over-rehearsing into a script that shatters on first contact. This skill preps the hard talk the way the research says works: get clear on the actual goal, understand the other person's story, open without triggering defensiveness, and plan for their reactions — so you go in calm and come out with the relationship intact.

Required Inputs

Ask for these only if they aren't already provided:

  • The situation — what's happened, with whom, and the relationship (manager, report, peer, client).
  • What you want — the real outcome (often a changed behaviour or a restored relationship, not "to be right").
  • Their likely view — how they probably see it, and what they care about.
  • The stakes & history — what makes it hard, and anything that's been tried.

Output Format

Difficult Conversation: [topic] with [who]

1. Your real goal — name it plainly (and the un-goal — e.g. "not to win, but to change X"). Conversations go wrong when the unspoken goal is to be proven right.

2. Their story — how they likely see it and what they need to feel (heard, respected, safe). You can't move someone you haven't understood.

3. Open — a specific opening line that states the issue from the facts + your impact, not blame ("When the deadline slipped, I was left explaining it to the client" — not "You always miss deadlines"). The first 30 seconds set the tone.

4. Key points — the 2–3 things you must convey, each separating observation from story/judgement.

5. Likely reactions → your response — defensiveness, deflection, emotion, counterattack — and a calm, non-escalating reply prepared for each.

| If they… | You respond… | |---|---|

6. Land it — the ask or agreement you want, and how to close on a concrete next step.

Stance note — stay curious, not certain; aim for a shared understanding, not a verdict.

Quality Checks

  • [ ] The real goal is named (and separated from the ego-goal of "being right")
  • [ ] The other person's perspective is genuinely represented, not strawmanned
  • [ ] The opening uses facts + impact, not blame or character judgement
  • [ ] Observation is separated from interpretation throughout
  • [ ] Likely reactions each have a prepared, non-escalating response
  • [ ] It closes on a concrete next step or agreement

Anti-Patterns

  • [ ] Do not open with blame or "you always/never" — it triggers defensiveness and ends learning
  • [ ] Do not confuse your story with the facts — "the deadline slipped" is fact; "you don't care" is a story
  • [ ] Do not over-script — plan the open and the points, then stay responsive; a rigid script breaks
  • [ ] Do not aim to win — if the goal is to be right, the relationship loses even if you "win"
  • [ ] Do not avoid the actual ask — name the change or agreement you need, kindly and clearly

Based On

Crucial Conversations (Patterson et al.) and Difficult Conversations (Stone, Patton, Heen) — facts vs. story, the third story, safety.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.