| name | rejection-sensitivity-reframe |
| description | Reread a harsh message, criticism, or perceived slight without the emotional spike — separate what was actually said from what your brain is amplifying. Use when asked this message really stung, am I overreacting to this, help me not spiral over this feedback, or did they mean it that way. Produces a calm read of what was literally said vs the story you've layered on, a check on the most likely (usually more neutral) intent, whether any action is actually warranted, and a grounded response option — easing the disproportionate sting that rejection-sensitive brains feel. |
| homepage | https://mohitagw15856.github.io/pm-claude-skills/skill/rejection-sensitivity-reframe.html |
| metadata | {"openclaw":{"emoji":"🧠"}} |
Rejection-Sensitivity Reframe
A curt reply or a piece of feedback can land like a gut-punch far bigger than the words warrant — especially for rejection-sensitive brains, where a neutral "ok." reads as fury. This separates the literal message from the catastrophe your mind is building on top of it, checks the likely real intent, and tells you whether anything actually needs doing — so you respond to what happened, not to the spike.
What This Skill Produces
- What was literally said — the actual words, stripped of interpretation
- The story you've added — the meaning your brain layered on (the rejection, the anger, the "they hate me") that isn't in the text
- The likely real intent — the most probable, usually more neutral, explanation
- Is action warranted? — whether this genuinely needs a response/repair, or just needs to be let go
- A grounded response — if one's needed, a calm option that isn't driven by the spike
Required Inputs
Ask for these if not provided:
- The message or event — what was said or happened (paste it)
- How it landed — what you felt and the story you're telling
- The relationship & context — who it's from and what's normal for them
- What you're tempted to do — so we can check it against the reality
Framework: Separate The Words From The Wound
- Read only the words. State what was literally said or done, with zero interpretation — the text, not the meaning.
- Name the added story. Surface the interpretation the brain has layered on ("they're angry," "I've failed," "they're pulling away") and mark it as story, not fact.
- Offer the likely intent. Give the most probable neutral explanation — brevity is usually busyness, not fury; feedback is usually about the work, not you.
- Test if action is needed. Most stings need no action — just time. Distinguish the rare real issue from the spike that will pass.
- Ground any response. If a response is warranted, offer a calm one written from the reframe, not from the raw reaction — and counsel waiting before sending if it's hot.
Output Format
The thing that stung: [the message/event]
What was literally said: [the words, no interpretation].
The story you've added: [the amplified meaning — which isn't in the text].
Most likely intent: [the neutral, probable explanation].
Does this need action? [probably just let it settle / yes — here's why].
If you respond: [a calm, grounded option] — and maybe wait an hour first.
Quality Checks
Anti-Patterns
- Dismissing the feeling ("you're overreacting") — invalidating.
- Endorsing the catastrophe as if the story were fact.
- Pushing a hot response instead of counseling a pause.
- Assuming action is needed when letting it settle is right.
Example Trigger Phrases
- "This message from my boss really stung — am I overreacting?"
- "My friend replied 'k.' and I'm spiraling. Help."
- "This feedback crushed me — help me reread it calmly."
- "Did they mean it the harsh way, or is it just me?"
- "Help me not catastrophize this text."
