Harsh feedback skills
10 minutes from spiral to action plan. For the moment right after criticism hits.From the repository description
npx -y skills add mcltyl/harsh-feedback-skillsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.7 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it
Just Got Harsh Feedback
10 minutes from spiral to action plan. For the moment right after criticism hits.
When to Use
You just walked out of a 1:1 or performance review where someone said something that stung. You're not sure if you're overreacting or if it was unfair. Your thoughts are racing. You need to process this before it ruins your day (or week).
Trigger: Within 30 minutes of receiving critical feedback. Emotions are still raw.
The Protocol (10 minutes total)
Phase 1: Ground First (30 seconds)
Before anything else:
"You're not broken. Harsh feedback feels personal because you care about your work. That's actually good. Let's separate the sting from the signal."
Take one breath. We're going to work through this systematically.
Phase 2: Capture Raw (2 minutes)
Write down exactly what was said. Not your interpretation—their actual words.
Prompt the user:
"What did they actually say? Quote it as accurately as you can. Don't paraphrase yet."
If they can't remember exact words:
"What's the core message you heard? We'll separate fact from interpretation in the next step."
Phase 3: Separate Fact from Story (3 minutes)
Create two columns:
| What They Said (Fact) | What You Heard (Story) |
|---|---|
| "Your presentation needed more data" | "They think I'm incompetent" |
| "The deadline was missed" | "They're going to fire me" |
| "This approach won't work" | "They don't trust my judgment" |
Prompt:
"For each thing they said, what's the story you're adding on top? The story is usually about your identity or your future—not about this specific situation."
Key insight to offer:
"The feedback is about this deliverable, not about who you are. If you can separate those, you can hear the useful part."
Phase 4: Extract the Signal (2 minutes)
Ask:
"If a mentor you trusted said the exact same words, what would you take from it? What's the actionable kernel?"
Look for:
- Specific behavior they want changed (not vague "be better")
- Gap between expectation and delivery
- Context you might have been missing
If the feedback was truly vague or unfair:
"Some feedback is more about the giver than the receiver. If you can't find a specific, actionable kernel, it might be projection or poor delivery on their part. Note it, but don't carry it."
Phase 5: One Next Action (2 minutes)
Not "become a better person." One concrete thing you can do in the next 48 hours.
Prompt:
"What's one small thing you could do by Friday that addresses the core of this feedback?"
Examples:
- "Ask [person] for a 15-min clarification on what 'more data' means"
- "Draft an outline before the full doc next time"
- "Set up a check-in midway through the project"
If they're stuck:
"Would it help to talk to the person who gave the feedback? Sometimes a follow-up question ('Can you give me an example?') turns vague criticism into useful direction."
Phase 6: Protect the Container (30 seconds)
"This feedback is now contained in this conversation. You don't need to replay it. You have one action. The rest is noise."
Optional: If they want to vent more, let them. But end with:
"What you're feeling is valid. And you've already done the hard part—you turned it into something actionable. That's more than most people do."
Common Patterns
"They're right and I hate it"
"The sting is proportional to the truth. If it didn't land, you'd shrug it off. This means you already knew—they just said it out loud."
"This is so unfair"
"It might be. Feedback quality varies wildly. But even unfair feedback tells you something—maybe about their expectations, their communication style, or the political landscape. What's the meta-signal?"
"I can't stop replaying it"
"Your brain is trying to rewrite the past. It can't. The only timeline you control is forward. What's the smallest next step?"
"I want to quit"
"That's a valid long-term option. But don't quit because of one conversation. Make a note: 'If this pattern repeats 3x, reassess.' Today, just do the one action."
What This Skill Doesn't Do
- Won't tell you the feedback was wrong (it might be, but that's not useful)
- Won't help you argue back (that's a different skill)
- Won't process deep career dissatisfaction (see: Should I Quit skill)
This is first-response triage. Stabilize → Separate → Act.
Output
By the end, user should have:
- The actual feedback written down (not the story)
- One actionable insight extracted
- One concrete next step for the next 48 hours
- Emotional regulation: "contained, not solved"
For deeper career-fit questions, see Should I Quit
What ships with it: 1 file
2.8 KB alongside SKILL.md
- README.md2.8 KB