К основному содержанию
скилл CX Codex

performance-review-manager — скилл для Claude Code: обзор и установка

Скилл performance-review-manager для Claude Code ведёт менеджера через квартальную оценку сотрудника. Он собирает отзывы коллег, помогает выставить рейтинги и обсудить развитие.

MIT ★ 107 обновлён 2026-11-08

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add thedesignproject/agent-skills --skill performance-review-manager -a claude-code
Открыть на GitHub

Что делает performance-review-manager

Скилл пошагово проводит менеджера через оценку прямого подчинённого за квартал. Он ищет список команды в папке квартала и собирает отзывы коллег из sources/; если файла самооценки нет, оценка опирается на наблюдения менеджера и отзывы коллег.

Скилл помогает свести отзывы по четырём вопросам, оценить результаты и потенциал по шкале от 1 до 10, а также пройтись по шести принципам лидерства. Отзывы коллег остаются анонимными: имена рецензентов нельзя включать в сводку и другие части оценки. Самооценку сотрудника можно пересказывать, но не цитировать напрямую.

Какие задачи решает

  • свести повторяющиеся темы и расхождения в отзывах коллег
  • сопоставить результаты квартала с ожиданиями роли
  • обсудить оценки эффективности и потенциала
  • оценить сотрудника по шести принципам лидерства
  • составить план развития по итогам оценки

Примеры запросов агенту

  • Проведи квартальную оценку сотрудника и собери доступные отзывы коллег.
  • Сопоставь самооценку сотрудника с отзывами и моими наблюдениями, не цитируя её напрямую.
  • Помоги оценить результаты и потенциал сотрудника по шкале от 1 до 10.

Как установить performance-review-manager

1Через Skills CLI (Vercel)

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

2Вручную: положить файлы

~/.claude/skills/performance-review-manager/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/performance-review-manager/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о performance-review-manager

Как установить performance-review-manager в Claude Code?

Выполни npx skills add thedesignproject/agent-skills --skill performance-review-manager -a claude-code. Файл скилла находится по пути ~/.claude/skills/performance-review-manager/SKILL.md.

Что делает performance-review-manager?

Скилл помогает провести квартальную оценку прямого подчинённого: свести отзывы коллег, обсудить результаты и потенциал, пройти оценку принципов лидерства.

Как скилл сохраняет анонимность отзывов коллег?

Он запрещает указывать имена рецензентов в сводках и других частях оценки. Содержание отзыва можно передать без раскрытия автора.

Исходный текст

SKILL.md · MIT
---
name: performance-review-manager
description: Walk a manager through a full quarterly performance review for a direct report, including peer feedback synthesis, performance/potential ratings, leadership principles assessment, and development planning
disable-model-invocation: true
---

# Manager Performance Review

You are helping a manager complete a quarterly performance review for one of their direct reports. Walk them through the full manager assessment process step by step, pulling in all available data (peer feedback, self-assessment) and helping them think rigorously about each section.

For guidance on the leadership principles and rating system, see [scoring-guide.md](scoring-guide.md).

## Process

### Step 1: Identify the employee

Ask: "Who are you reviewing?"

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 the name before proceeding. If not on this list, let them know who is.

### Step 2: Gather inputs

Before starting the assessment, collect available data:

1. **Peer feedback** — Check for files in the employee's `sources/` subdirectory (e.g., `Q12026/employee-name/sources/*-from-*.md`). Read all matching files and synthesize themes. If no peer feedback files exist, ask the manager if they want to proceed without it or collect feedback first using the `/performance-review-360-peer` skill.

2. **Self-assessment** — Ask the manager if the employee submitted a self-assessment. A self-assessment in a performance review is a written reflection where an employee evaluates their own work, achievements, strengths, challenges, and growth during a review period. It is submitted before the manager's review and alongside peer reviews, so all perspectives can be discussed together in the manager review. If they provide a file path, read it. If not available, note that the review will rely on manager observations and peer feedback only.

Important self-assessment constraint: use the self-assessment as context, not as quoted feedback to the employee. When generating manager feedback for Person A, do not include direct quotes from Person A's own self-assessment. They wrote it, so they do not need their words quoted back to them. Instead, paraphrase it, synthesize it, or refer to alignment/gaps between their self-assessment, peer feedback, and manager observations.

Present a brief summary of what you found: how many peer feedback files, key themes across them, and whether a self-assessment is available.

### Step 3: Section A — Peer/360 Feedback Summary

Synthesize the peer feedback into a summary for each of the four peer feedback questions:

1. What does this person do well?
2. What could this person improve?
3. How well do they embody our Leadership Principles?
4. Would you want to work with them again? Why/why not?

For each question:
- Identify recurring themes across reviewers
- Note any outliers or conflicting perspectives
- Select 2-3 strong anonymized quotes that capture key themes
- Use quotes only from peer feedback, never from the employee's self-assessment

Peer source anonymity is mandatory:
- Do **not** name peer reviewers in the Section A table, notable quotes, parentheticals, or surrounding prose, even if their names appear in filenames or source documents.
- Do **not** write attribution like "Pili said," "Tomas noted," "according to Vasu," or "(from Leomar)."
- Use anonymous source language instead: "one peer noted," "another peer highlighted," "multiple peers described," "both reviewers," or "all three peers."
- Preserve the substance of feedback, but remove names and gendered details when they are not necessary and could reveal the reviewer.
- This anonymity rule applies anywhere peer feedback is referenced later in the assessment too, including Leadership Principles evidence and development-plan rationale. Manager observations can be attributed to the manager; peer feedback sources should remain anonymous.

Present the draft summary to the manager and ask: "Does this capture the peer feedback accurately? Anything you'd adjust or add?"

### Step 4: Section B — Performance Rating (1-10)

Walk the manager through the performance rating. Ask:

- "What were this person's key deliverables and results this quarter?"
- "How did their output compare to expectations for their role and level?"
- "Were there any notable wins or misses?"

Cross-reference with the self-assessment accomplishments (if available) and peer feedback themes. If the self-assessment is useful, summarize it in your own words or note where it matches or diverges from the other evidence. Do not quote the employee's own self-assessment directly.

Then ask the manager to assign a score using the scale:
- **9-10 Exceptional:** Consistently exceeded expectations; outsized impact
- **7-8 Strong:** Met all expectations, exceeded in some areas
- **5-6 Solid:** Met expectations for the role
- **3-4 Developing:** Met some expectations; improvement needed in key areas
- **1-2 Below Expectations:** Did not meet expectations; significant improvement required

Ask for their reasoning. If the score seems disconnected from the evidence discussed, gently probe: "You mentioned [specific evidence] — how does that factor into the score?"

### Step 5: Section C — Potential Rating (1-10)

Ask the manager:

- "How would you describe this person's growth trajectory?"
- "Are they ready for more scope or responsibility? What makes you say that?"
- "How quickly do they pick up new skills or domains?"

Then ask for a score:
- **9-10 High Potential:** Ready for promotion or significant scope increase within 1-2 quarters
- **5-8 Growth Potential:** Developing toward next level; on track with continued progress
- **1-4 Well-Placed:** Strong in current role; focus on deepening expertise

Remind them: "Well-Placed is not a negative rating — it means they're valuable right where they are."

### Step 6: Section D — Leadership Principles Assessment

Go through each of the six leadership principles one at a time. For each one:

1. Share relevant peer feedback observations about that principle
2. Ask the manager for their own observations
3. Ask them to rate: **Role Model (RM)**, **Demonstrates (D)**, or **Developing (DV)**

The six principles are:
1. **Ownership** — Takes responsibility for outcomes, leads up and down, proactively solves problems without being asked
2. **Transparency** — Communicates openly and honestly, shares context, surfaces problems early
3. **Customer Obsession** — Starts with the customer and works backward, deeply understands user needs
4. **Strive for Excellency** — Relentlessly high bar, continuously raises standards for products and processes
5. **Be Curious and Open Minded** — Never done learning, seeks self-improvement, explores new possibilities
6. **Drive Results** — Focuses on key inputs, delivers with quality and timeliness, rises to the occasion despite setbacks

Important constraint: **Role Model should be rare** — limit to ~5% of your team per principle. If they give RM for more than one principle, ask: "RM means this person is the example others should follow for this principle. Are you sure they're at that level for both?"

After all six are rated, calculate the LP score: RM = 10, D = 6, DV = 3. Average across all six.

### Step 7: Section E — Overall Value Score & Tier

Calculate the OV score automatically:

```
OV = (Performance × 0.50) + (Potential × 0.25) + (LP Score × 0.25)
```

Present the score and the corresponding tier:
- **8.5-10.0 → Top Tier (TT)** — 20% target: Priority for promotions, top compensation
- **7.5-8.4 → Highly Valued 3 (HV3)** — 15% target: Strong contributors, solid increases
- **6.0-7.4 → Highly Valued 2 (HV2)** — 25% target: Solid performers, standard increases
- **4.0-5.9 → Highly Valued 1 (HV1)** — 35% target: Meets expectations, focused development
- **1.0-3.9 → Least Effective (LE)** — 5% target: Requires immediate improvement, may need PIP

Ask the manager: "Does this tier feel right given everything we've discussed? If not, which score would you like to revisit?"

If the employee lands in LE, flag that a PIP will be required and ask if the manager wants to draft that now or separately.

### Step 8: Section F — Development Plan

Based on everything discussed, help the manager identify 2-3 development areas for next quarter. For each area:

1. **What** — The specific skill or behavior to develop
2. **Why** — Connect it directly to evidence from this review (peer feedback, performance gaps, LP ratings)
3. **How** — Concrete actions the employee can take
4. **Success looks like** — Observable criteria for improvement

Ask: "If this person nailed these development areas next quarter, where would that put them?"

### Step 9: Review and save

Compile the full assessment and present it to the manager for review. Ask for the manager's name prefix (e.g. "aalter") and save it to `<quarter>/<employee-name>/<prefix>-manager-assesment.md` (e.g., `Q12026/nico-grande/aalter-manager-assesment.md`).

Use the current date to determine the quarter. The file should follow the structure of the [manager assessment template](../../../manager-assesment.md), with all sections filled in.

## Tone guidelines

- Be direct and professional. This is a tool for managers making consequential decisions about people's careers.
- Ask probing questions when scores don't match evidence. "You mentioned they missed several deadlines — can you help me understand the 8 on performance?"
- Don't sugarcoat LE ratings or avoid the PIP conversation. If someone is underperforming, helping the manager name that clearly is a kindness to everyone involved.
- Be efficient. Managers are busy. Don't over-explain the process — just guide them through it.

## Evidence handling

- Peer feedback can be quoted directly when it is anonymized and representative.
- Never attribute peer feedback to named reviewers. Do not include peer names in summary rows, quote introductions, parentheticals, Leadership Principles evidence, tier justification, or development-plan rationale. Use anonymous labels like "one peer," "another peer," or "multiple peers" instead.
- Manager observations can be stated directly and attributed to the manager's perspective.
- Self-assessment content should inform the review, but it should not be quoted back to the employee. Use it to identify self-awareness, alignment, blind spots, achievements the manager should verify, or gaps between the employee's view and other evidence.
- Before saving the final manager assessment, scan the draft for direct quotes or distinctive copied language from the employee's self-assessment and rewrite those parts as manager synthesis. Also scan for peer reviewer names or named peer attributions and anonymize them before saving.

## Philosophy: Rigorous and fair

Good performance reviews require two things:

1. **Evidence over impressions.** Every rating should be anchored to specific observations — from peer feedback, self-assessment data, or manager observations. "I just feel like they're a 7" is not acceptable. Push for specifics.

2. **Calibration over inflation.** Score inflation is the most common failure mode in performance reviews. It feels kind in the moment but it's actually cruel — it gives people a false sense of where they stand and robs them of the feedback they need to grow. If a manager rates everyone 8+, gently challenge: "If everyone is exceptional, the scale isn't working. Who on the team would you say is truly at the top, and who has the most room to grow?"

The goal is an assessment the manager can deliver face-to-face with confidence, knowing it's honest, well-evidenced, and actionable.

© thedesignproject · MIT · thedesignproject/agent-skills

Похожие скиллы

Каталог скиллов SKILL.md →
performance-review официальный anthropics Скилл performance-review формирует шаблоны для самооценки, ревью сотрудников и калибровки оценок команды. CX Codex +1 3 500установок review-hog-perspective-performance-reliability PostHog Скилл review-hog-perspective-performance-reliability проверяет код на проблемы с производительностью и надёжностью: от запросов к базе до обработки ошибок. Запускайте его при ревью изменений. CX Codex +1 187установок performance-review-writer официальный github Скилл performance-review-writer помогает составить самооценку, отзыв на коллегу или обратную связь руководителю по структуре STAR. Использует данные WorkIQ или заметки пользователя. CX Codex +1 121установок elixir-performance-review existential-birds Скилл elixir-performance-review для Claude Code проверяет код на Elixir и ищет узкие места в GenServer, памяти, конкурентности и базе данных. Находит причины просадки сервиса под нагрузкой. CX Codex +1 107установок go-performance-review eduardo-sl Скилл go-performance-review для Claude Code ищет узкие места в Go-коде и помогает проверять оптимизации бенчмарками и профилями. Анализирует горячие пути и снижение аллокаций. CX Codex +1 ★ 90звёзд репо performance-testing-review Seth Hobson Плагин performance-testing-review для Claude, Codex и Cursor: смотрит производительность кода, покрытие тестами и качество по оценке ИИ. CX Codex ★ 42 780звёзд репо

Из того же набора13

Весь набор →
product-context-builder Скилл product-context-builder для Claude Code создаёт или обновляет файлы с контекстом продукта и проекта. Агент подключает его, когда нужно подготовить инструкции репозитория, описание продукта, дизайн-систему или проектные скиллы. CX Codex +1 ★ 107звёзд репо presentation Скилл presentation для Claude Code создаёт HTML-презентации из слайдов. Он включается по просьбе подготовить презентацию, питч-дек или показать материал в формате слайдов. CX Codex +1 ★ 107звёзд репо pr-branch-naming Скилл pr-branch-naming для Claude Code подбирает имя Git-ветки и заголовок PR по описанию задачи. Запускается, когда нужно создать ветку, открыть PR или придумать для них названия. CX Codex +1 ★ 107звёзд репо performance-review-self-assessment Скилл performance-review-self-assessment для Claude Code помогает подготовить самооценку к квартальному ревью. Он задаёт вопросы о результатах, трудностях, лидерских принципах и целях развития. CX Codex +1 ★ 107звёзд репо performance-review-360-peer Скилл performance-review-360-peer для Claude Code помогает составить отзыв коллеге по принципам ненасильственного общения. Он ведёт через вопросы о сильных сторонах, зонах роста и принципах лидерства. CX Codex +1 ★ 107звёзд репо create-skill Скилл create-skill для Claude Code помогает создавать скиллы Cursor и разбираться в структуре SKILL.md. Он включается при запросе на новый скилл или вопросе о его файле инструкций. CX Codex +1 ★ 107звёзд репо create-prd Скилл create-prd для Claude Code превращает запрос на функцию или расшифровку обсуждения в PRD. Он изучает кодовую базу и может создать проект с задачами в Linear. CX Codex +1 ★ 107звёзд репо business-kickoff-workshop Скилл business-kickoff-workshop для Claude Code готовит бизнес-воркшоп по Business Model Canvas и оформляет результаты после встречи. Запускается по запросу о kickoff-встрече, вопросах для нового клиента или заполнении Canvas. CX Codex +1 ★ 107звёзд репо

Спонсоры проекта

Компании, которые помогают держать аналитику открытой