Skip to main content
skill CX Codex

performance-review-360-peer — Claude Code skill: peer feedback

The performance-review-360-peer Claude Code skill guides a colleague through peer feedback using Nonviolent Communication. It asks about strengths, growth areas, leadership principles, and future collaboration.

MIT ★ 107 updated 2026-11-08

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add thedesignproject/agent-skills --skill performance-review-360-peer -a claude-code
Open on GitHub

What performance-review-360-peer does

The skill collects peer feedback for a quarterly performance review and helps make it specific and considerate. It first asks who is giving feedback and who it concerns, then walks through questions about strengths, areas to improve, leadership principles, and whether they would work together again.

The prompts help turn judgments into observations, blame into a description of impact, and criticism into a concrete request. Before saving, the agent reads back a summary and applies requested edits. The feedback goes into the reviewed person’s sources directory at <quarter>/<person-reviewed>/sources/<person-reviewed>-from-<person-giving>.md.

The team list comes from subdirectories in the quarter folder, such as Q12026/. If that folder does not exist, the manager supplies the list. The saved file has sections for strengths, improvements, leadership principles, and willingness to work together again.

What it helps with

  • write specific feedback about a colleague’s work
  • replace labels with observations and their impact
  • describe a growth area as a need and a concrete request
  • save peer feedback in a quarterly review format

Example prompts for the agent

  • Help me write peer feedback for a colleague’s quarterly review.
  • Help me describe what a colleague could improve without using personal labels.
  • Collect my feedback on how a colleague demonstrates the leadership principles.

How to install performance-review-360-peer

1Skills CLI (Vercel)

npx skills add thedesignproject/agent-skills --skill performance-review-360-peer -a claude-code

2Manually: put the files in place

~/.claude/skills/performance-review-360-peer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/performance-review-360-peer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about performance-review-360-peer

How do I install performance-review-360-peer in Claude Code?

Run npx skills add thedesignproject/agent-skills --skill performance-review-360-peer -a claude-code. The skill file is at ~/.claude/skills/performance-review-360-peer/SKILL.md.

What does performance-review-360-peer do?

It guides a peer through review questions and helps express feedback as observations, impact, and concrete requests. It then saves the result in the reviewed colleague’s folder.

How does the skill find the team member list?

It reads names from subdirectories in the quarter folder, such as Q12026/. If the folder does not exist, the manager provides the list.

Source text

SKILL.md · MIT
---
name: performance-review-360-peer
description: Help someone give peer feedback for a colleague using the Non-Violent Communication framework
disable-model-invocation: true
---

# Peer Feedback Collection

You are helping someone give peer feedback about a colleague as part of a quarterly performance review. Guide them using Marshall B. Rosenberg's Non-Violent Communication (NVC) framework to produce feedback that is honest, specific, and compassionate.

For detailed NVC guidance, see [nvc-guide.md](nvc-guide.md).

## Process

### Step 1: Identify who is giving feedback and who it's about

Ask: "Who are you, and who are you giving feedback for?"

Look up the current team member list in the quarter folder (e.g. `Q12026/`) — each subdirectory name is a team member. If no quarter folder exists yet, ask the manager to provide the list of team members.

Confirm both names before proceeding. If the person being reviewed isn't on this list, let them know who's on it and ask them to pick from it.

### Step 2: Walk through each feedback question

For each question below, have a conversation. Ask the question, then help the person refine their answer using NVC principles. Coach them gently — don't lecture. If their answer is vague, ask a follow-up. If it contains judgments or labels, help them reframe into observations and feelings.

**Question 1: What does this person do well?**

Help them ground praise in specific observations:
- "Can you think of a specific moment or project where you saw this?"
- "What did they actually do or say that made an impact?"
- Encourage them to describe the concrete behavior and how it affected them or the team.

**Question 2: What could this person improve?**

This is where NVC matters most. Help them:
- Separate **observations** from **evaluations** ("They don't care" → "In the last 3 sprints, they didn't attend the design review meetings")
- Express **impact** rather than blame ("When X happened, it affected the team by Y")
- Frame as **unmet needs** rather than character flaws ("I need more predictability in deadlines" rather than "They're unreliable")
- Offer a **concrete request** if possible ("It would help if they could flag blockers in standup earlier")

**Question 3: How well do they embody our Leadership Principles?**

The leadership principles are:
1. Ownership
2. Transparency
3. Customer Obsession
4. Strive for Excellency
5. Be Curious and Open Minded
6. Drive Results

Ask them to pick 1-2 principles where this person stands out (positively or as a growth area) and give a specific example for each.

**Question 4: Would you want to work with them again? Why or why not?**

Encourage an honest, specific answer. If hesitation comes up, help them articulate the underlying need or concern without making it personal.

### Step 3: Review and save

After collecting all answers:

1. Read back a summary of their feedback and ask if it captures what they meant.
2. Make any adjustments they request.
3. Save the feedback to the reviewed person's sources directory: `<quarter>/<person-reviewed>/sources/<person-reviewed>-from-<person-giving>.md` (lowercase, hyphens for spaces). For example: `Q12026/alex/sources/alex-from-dianne.md`.

The file should follow this format:

```markdown
# Peer Feedback: [Person Reviewed]
**From:** [Person Giving Feedback]
**Date:** [Today's date]

## What does this person do well?
[Their answer, refined with NVC]

## What could this person improve?
[Their answer, refined with NVC]

## Leadership Principles
[Their observations on 1-2 principles with examples]

## Would you want to work with them again?
[Their answer]
```

## Tone guidelines

- Be warm and conversational, like a trusted coach sitting next to them.
- Never make them feel judged for their initial phrasing — just gently help them find a more specific, compassionate way to say it.
- Use phrases like "That's a great start — can we make it even more specific?" or "What was the impact of that on you or the team?"
- Keep it efficient. Don't over-explain NVC theory. Just model it through your questions.

## Philosophy: Be kind, not nice

This is critical. There is a difference between being **kind** and being **nice**:

- **Nice** avoids discomfort. It protects the giver's feelings, not the receiver's growth.
- **Kind** tells the truth with care. It prioritizes the other person's development even when it's uncomfortable to say.

Withholding honest feedback because it feels awkward is not generosity — it's selfishness. It denies the other person the chance to grow. If someone is struggling to give constructive feedback, or says "I can't think of anything they could improve," push back gently but firmly:

- "Everyone has growth areas. What's one thing that, if they changed, would make them even more effective?"
- "Think about a moment where something felt off — even slightly. What happened?"
- "If you truly care about this person's career, what would you want them to hear that nobody else is telling them?"
- "Avoiding tough feedback feels protective, but it actually holds them back. What's the kind thing to say here?"

The NVC framework is not about softening the message — it's about delivering hard truths in a way that can actually be heard. Specific, observation-based, compassionate honesty. That's the goal.

© thedesignproject · MIT · thedesignproject/agent-skills

Similar skills

SKILL.md skills catalog →

From the same set13

The whole set →
presentation This Claude Code skill builds slide decks as HTML presentations. It activates for requests to create a presentation, pitch deck, or slide-based version of some material. CX Codex +1 ★ 107repo stars pr-branch-naming The pr-branch-naming Claude Code skill suggests a Git branch name and matching PR title from a feature description. It activates for requests to start a branch, open a PR, or choose either name. CX Codex +1 ★ 107repo stars performance-review-self-assessment The performance-review-self-assessment Claude Code skill guides employees through a quarterly self-assessment. It covers accomplishments, challenges, leadership principles, and progress on development goals. CX Codex +1 ★ 107repo stars performance-review-manager The performance-review-manager Claude Code skill guides a manager through a quarterly employee review. It gathers peer feedback and helps assess performance, potential, and development. CX Codex +1 ★ 107repo stars create-skill This Claude Code skill helps create Cursor skills and explains the structure of SKILL.md. It applies to requests for a new skill or questions about its instruction file. CX Codex +1 ★ 107repo stars create-prd create-prd is a Claude Code skill that turns a feature request or transcript into a PRD. It examines the codebase and can create a Linear project with issues. CX Codex +1 ★ 107repo stars business-kickoff-workshop The business-kickoff-workshop Claude Code skill prepares a Business Model Canvas workshop and turns call notes into a completed canvas. It activates for kickoff planning, customer discovery questions, or post-call canvas work. CX Codex +1 ★ 107repo stars build-my-designer-brain The build-my-designer-brain Claude Code skill builds a designer’s personal collection of methods, preferences, and lessons. It runs to create or revise that collection, or to apply it while working on a feature. CX Codex +1 ★ 107repo stars

Project sponsors

Companies that keep this analytics open