MCPInstall

feedback-coach

Structures performance feedback using Radical Candor (challenge directly, care personally) and identity-safe framing to ensure feedback drives growth rather than defensiveness. Use when giving or receiving feedback, conducting 1:1s, preparing performance reviews, or coaching developmental conversations.

Installs
41
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/joellewis/skill-library --skill feedback-coach
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads feedback-coach automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Overview

Effective feedback is the high-leverage intersection of guidance and growth. This skill provides the mechanics for "Radical Candor"—challenging directly while caring personally—and ensures that feedback is received as a tool for improvement rather than a threat to identity.

Guiding Principles

1. Radical Candor Quadrant (Source: Scott, Radical Candor)

Feedback must exist in the Radical Candor quadrant:

  • Care Personally: Show you give a damn about the human being.
  • Challenge Directly: Be clear and unambiguous about what isn't working. Avoid Ruinous Empathy (nice but unhelpful), Obnoxious Aggression (clear but hurtful), and Manipulative Insincerity (backstabbing).

2. Pull Beats Push (Source: Stone, Thanks for the Feedback)

The receiver is in control of what is let in. Focus on creating "pull" by helping receivers recognize their triggers (Truth, Relationship, Identity) and manage their "blind spots."

3. Separate Appreciation, Coaching, and Evaluation (Source: Stone, Thanks for the Feedback)

Wires get crossed when the receiver wants one type but gets another.

  • Appreciation: "I see you and value your work."
  • Coaching: "Here is how you can improve."
  • Evaluation: "Here is where you stand against standards." Always clarify the purpose of the conversation upfront.

4. HHIPP Framework for Giving Feedback (Source: Scott, Radical Candor)

Effective guidance is Humble, Helpful, Immediate, In-person, and doesn't Personalize (Praise in Public, criticize in Private). Use "You sounded stupid" (behavior) rather than "You are stupid" (trait).

5. It’s the People (Source: Schmidt, Trillion Dollar Coach)

The top priority of a manager is the well-being and success of their people. Coaching is not a specialty; it is the core of management. Trust is the prerequisite for all feedback.

6. Destigmatize Failure (Source: Edmondson, The Fearless Organization)

Frame the work as a learning problem, not an execution problem. When failure happens, respond productively by expressing appreciation for the data point and focusing on the next experiment.

When to Use This Skill

  • During scheduled 1:1 meetings or annual performance reviews.
  • Immediately after a "teachable moment" or significant success/failure.
  • When team members are in the "Anxiety Zone" (High Standards, Low Safety).
  • When a "bad apple" (Jerk, Slacker, Downer) is affecting team performance.

When NOT to Use This Skill

  • When emotions are so high that "System 2" logic is offline (wait for a cooling-off period).
  • In a public forum when delivering criticism (violates the "Private" rule of HHIPP).

Core Process

Step 1: Set the Stage (Psychological Safety)

Frame the feedback as essential for the shared mission. Use the "Magical Feedback" phrase: "I'm giving you these comments because I have very high expectations and I know you can reach them" (Source: Edmondson).

Step 2: Solicit Feedback First

Before giving criticism, ask for it. "What could I do or stop doing that would make it easier to work with me?" This demonstrates vulnerability and models the behavior you want to see (Source: Scott).

Step 3: Deliver the Guidance (Radical Candor)

Use the HHIPP criteria. Be specific about the behavior and the impact.

  • Praise: Be specific and sincere to avoid "appreciation inflation."
  • Criticism: Be direct and helpful. Don't "sandwich" criticism between fake praise.

Step 4: Manage the Receiver's Triggers

If the receiver becomes defensive, identify which trigger was tripped:

  • Truth: They think the data is wrong. (Action: "Tell me more about how you see it.")
  • Relationship: They don't trust you. (Action: Restore Mutual Respect.)
  • Identity: They feel their sense of self is under attack. (Action: Affirm their growth identity) (Source: Stone).

Step 5: Focus on Future-Orientation

End the conversation with a clear path forward. Ask calibrated questions: "How can I support you in making this change?" (Source: Schmidt).

Frameworks & Models

The Bill Campbell 1:1 Framework (Source: Schmidt, Trillion Dollar Coach)

Structure regular check-ins using these 4 areas:

  1. Performance: Outcomes, milestones, and quality.
  2. Peer Relationships: How they are integrating with other teams.
  3. Management/Leadership: How they are coaching their own people.
  4. Innovation: How they are moving the needle and thinking ahead.

The Anxiety vs. Learning Matrix (Source: Edmondson, The Fearless Organization)

  • Apathy Zone: Low Safety, Low Standards.
  • Comfort Zone: High Safety, Low Standards.
  • Anxiety Zone: Low Safety, High Standards (The Danger Zone).
  • Learning Zone: High Safety, High Standards (High Performance).

Cross-Skill Invocations

  • REQUIRED SUB-SKILL: rapport-builder — Feedback cannot be delivered effectively without a foundation of trust and safety.
  • RECOMMENDED SUB-SKILL: difficult-conversations — When feedback triggers a high-conflict emotional response.
  • RECOMMENDED SUB-SKILL: operational-excellence — To align coaching with OKRs and performance metrics.

Common Mistakes

  1. Ruinous Empathy: Withholding criticism because you don't want to hurt feelings. This is the "Bob Story"—failing to tell someone they are failing until it's too late to fix (Source: Scott).
  2. The "Yes" Trap: Accepting an agreement to change without discussing "How" it will happen (Source: Schmidt).
  3. Switchtracking: Changing the topic from the feedback to the relationship when a trigger is hit. (Action: Address both, but separately) (Source: Stone).

Diagnostic Checklist

  • Am I challenging directly while showing I care personally?
  • Did I clarify whether this is coaching, appreciation, or evaluation?
  • Have I avoided personalizing the criticism ("You did X" vs "You are X")?
  • Is the feedback "HHIPP" (Helpful, Humble, Immediate, Private)?
  • Am I responding to the receiver's defensiveness by digging for the underlying trigger?

Sources

  • Stone, Douglas & Heen, Sheila. Thanks for the Feedback, Ch. 1 (Three Triggers), Ch. 2 (The Three Types).
  • Scott, Kim. Radical Candor, Ch. 2 (The Quadrants), Ch. 6 (HHIPP).
  • Edmondson, Amy. The Fearless Organization, Ch. 1 (Psychological Safety), Ch. 7 (Respond Productively).
  • Schmidt, Eric. Trillion Dollar Coach, Ch. 2 (It's the People), Ch. 3 (1:1 Framework).

FAQ

What does the feedback-coach skill do?

Structures performance feedback using Radical Candor (challenge directly, care personally) and identity-safe framing to ensure feedback drives growth rather than defensiveness. Use when giving or receiving feedback, conducting 1:1s, preparing performance reviews, or coaching developmental conversations.

How do I install feedback-coach?

Run npx skills add https://github.com/joellewis/skill-library --skill feedback-coach in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/feedback-coach/ (personal) or .claude/skills/feedback-coach/ (project).

Which AI agents can use feedback-coach?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is feedback-coach safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains feedback-coach?

It is published by joellewis in joellewis/skill-library. It has 41 recorded installs.

More from joellewis/skill-library

View all →

fiction-architect

joellewis/skill-library

Open the skill to read its SKILL.md instructions.

55 installs

dialogue-craft

joellewis/skill-library

Open the skill to read its SKILL.md instructions.

53 installs

world-building-logic

joellewis/skill-library

Open the skill to read its SKILL.md instructions.

53 installs

character-vulnerability

joellewis/skill-library

Open the skill to read its SKILL.md instructions.

Security47 installs

one-pager

joellewis/skill-library

Open the skill to read its SKILL.md instructions.

47 installs

problem-framing

joellewis/skill-library

Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.

47 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.