hard-conversation
Skill1 starsChanged 7 months agoMITView on GitHub
Prep for a charged conversation. NVC structure (observation, feeling, need, request) + Brené Brown rumble language + most-generous-interpretation. Usage is /hard-conversation [topic or person]. Drafts the opener and surfaces what you are not seeing.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- CSPulse/customer-success-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- CSPulse/customer-success-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- accountability-mirrorSkill
- annual-physicalSkill
- bills-and-subsSkill
- brotherhoodSkill
- conscious-spendingSkill
- date-nightSkill
- decision-journalSkill
- discomfort-doseSkill
- emotion-coachSkill
- enough-checkSkill
- errand-batchSkill
- evening-examenSkill
- father-reviewSkill
- friend-reach-outSkill
- gratitudeSkill
- home-maintenanceSkill
- kid-oneononeSkill
- love-map-refreshSkill
- mentor-touchSkill
- money-dateSkill
- morning-resetSkill
- parent-checkinSkill
- partner-checkinSkill
- partner-reviewSkill
- repairSkill
- resetSkill
- screwupSkill
- shutdown-ritualSkill
- sleep-protocolSkill
- training-planSkill
- values-checkSkill
- virtue-reviewSkill
- weekly-reviewSkill
- weekly-serviceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
If you are avoiding a conversation, you are having it anyway.
- Distinctive: line 16
If missing, ask: "Who is this with, and what is it about?"
- Distinctive: line 20
Before any prep, a 3-minute regulation check.
- Very specific: line 22
Run 3 rounds of physiological sigh (see /reset).
- Distinctive: line 26
Do not skip this.
- Distinctive: line 32
Ask the user: "Describe what happened in a way a neutral observer would agree with.
- Distinctive: line 49
Ask the user: "What is the underlying feeling, named as a feeling?"
- Distinctive: line 51
Use real feeling words: hurt, lonely, scared, angry, disappointed, ashamed, anxious, exhausted, powerless, sad.
- Distinctive: line 88
Ask the user: "What is the most generous story about why this person is doing what they are doing?"
- Distinctive: line 90
Not an excuse. An explanation.
- Distinctive: line 95
If you can enter the conversation holding a generous story about them, you will not need to "win." You will need to understand.
- Distinctive: line 113
Write the single sentence you are most afraid to say.
- Distinctive: line 121
If the sentence scares you, you probably have the right one.
- Distinctive: line 130
If you pick the second, do not have the conversation.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/hard-conversation
If you are avoiding a conversation, you are having it anyway. The version you are having is the one in your head, alone, at 2 a.m., with the worst version of the other person.
This skill takes you through structured prep. 15 minutes, tops. The payoff is huge.
Usage
$ARGUMENTS should be: who and what. "With my partner about the trip to her parents'." "With my cofounder about his direct reports." "With my dad about his drinking."
If missing, ask: "Who is this with, and what is it about?"
Step 1: Regulate first
Before any prep, a 3-minute regulation check. If the user is activated right now, this prep will get warped.
- Run 3 rounds of physiological sigh (see
/reset). - Drink water. Walk 5 minutes if possible.
- Come back when the adrenaline has left the body.
Do not skip this.
Step 2: The observation (not evaluation)
Rosenberg (Nonviolent Communication): observations are what a video camera would see. Evaluations are what your mind added.
Ask the user: "Describe what happened in a way a neutral observer would agree with. No interpretations, no 'always' or 'never', no character judgments."
Wrong: "You're always on your phone at dinner." Right: "The last three dinners together, the phone was in your hand for most of the meal."
Wrong: "He's being passive-aggressive." Right: "He hasn't replied to my last two direct questions and responded to a third by CC-ing his manager."
Capture this one observation.
Step 3: The feeling (not the thought)
Many "I feel..." statements are thoughts in disguise:
- "I feel attacked" — thought. (Real feeling: hurt, afraid, angry.)
- "I feel ignored" — thought. (Real feeling: lonely, sad, invisible.)
- "I feel like you don't care" — thought. (Real feeling: scared, alone.)
Ask the user: "What is the underlying feeling, named as a feeling?"
Use real feeling words: hurt, lonely, scared, angry, disappointed, ashamed, anxious, exhausted, powerless, sad.
Step 4: The need
Behind every hard feeling is an unmet need. Ask: "What do you need here? Underneath the complaint, the reaction, the irritation — what is the actual need?"
Common ones:
- Respect
- Predictability
- Partnership / not being alone in this
- Rest
- Trust
- Honesty
- Autonomy
- To matter
- Safety
Step 5: The request
Requests must be:
- Specific (not vague).
- Doable (in the person's power).
- Present-tense (not "you should have").
- Answerable with yes or no.
Wrong: "Be more supportive." Right: "When I come home late from work, could we skip the phone for the first 15 minutes and just sit together?"
Wrong: "Stop being controlling." Right: "I'd like to make the call on my own work schedule without checking in first. Would you be willing to try that for a month and see how it goes?"
A real request survives a "no." If you cannot hear "no," you are making a demand, and the other person will feel it.
Step 6: The most generous interpretation
Dr. Becky's move, adapted for adults.
Ask the user: "What is the most generous story about why this person is doing what they are doing?"
Not an excuse. An explanation. Examples:
- "He is scared of losing his role, not trying to hurt me."
- "She has been sleeping badly and is running on empty."
- "My dad is afraid of being forgotten, and the only way he knows to stay central is to make decisions for everyone."
If you can enter the conversation holding a generous story about them, you will not need to "win." You will need to understand.
Step 7: The story I'm telling myself
Brené Brown. Write it down: "The story I'm telling myself is..."
- "The story I'm telling myself is that you don't care about me anymore."
- "The story I'm telling myself is that you think I'm failing at my job."
- "The story I'm telling myself is that I am less important to you than your work."
This is NOT what you say to them as a fact. It is what you say to them as a story you are running, to own that it is YOUR story.
In the conversation: "The story I'm telling myself is [...]. Is any part of that true?"
This is one of the most disarming phrases in the English language. It transforms accusations into something both people can look at together.
Step 8: The one-sentence opener
Write the single sentence you are most afraid to say. That is your opener. Clear is kind. Unclear is unkind.
Examples:
- "I don't feel close to you right now, and I want to."
- "I think you're drinking more than is good for you, and I love you too much not to say it."
- "I think we've been pretending this will work out, and I don't think it's going to."
- "I don't trust this decision, and I need you to hear why before you make it."
If the sentence scares you, you probably have the right one.
Step 9: The outcome you actually want
Two options. Pick one.
- Connection. I want us to understand each other and keep moving together.
- Being right. I want them to admit I was correct.
If you pick the second, do not have the conversation. You will not get what you want anyway, and you will damage something in the process.
Step 10: The logistics
- Where and when? Not at the end of an already exhausted day. Not in the car with kids in the back.
- A walk can be better than a face-to-face. Side-by-side lowers the temperature.
- How long do you have? (Guard against the conversation running into something else and getting cut off at the worst moment.)
- Phones away.
Output
Produce this structured prep sheet. Save to ~/adulting-data/journal/hard-conversation-YYYY-MM-DD.md:
# Hard conversation prep — <date>
With: <person>
About: <topic>
## Observation
<what happened, video-camera style>
## Feeling
<real feeling words>
## Need
<underneath>
## Request
<specific, doable, yes/no-answerable>
## Most generous interpretation of them
<...>
## The story I'm telling myself
<...>
## Opener (the sentence I'm afraid to say)
<...>
## Outcome I want
<connection | being right> → <restate as one sentence>
## Logistics
When: <...>
Where: <...>
How long: <...>Before the user goes
End with a single question: "After doing this, do you still need to have this conversation this week, or do you now see it differently?"
Sometimes the prep itself changes the answer. Either way, the prep was worth it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

