
Performance Review Manager
- 48 installs
- 68 repo stars
- Updated July 13, 2026
- thedesignproject/agent-skills
Use when working on perf tasks.
About
Performance Review Manager skill provides code review and analysis. Complexity: intermediate.
- Manager
- Performance
- Review
Performance Review Manager by the numbers
- 48 all-time installs (skills.sh)
- +10 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #594 of 1,378 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/thedesignproject/agent-skills --skill performance-review-managerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 48 |
|---|---|
| repo stars | ★ 68 |
| Last updated | July 13, 2026 |
| Repository | thedesignproject/agent-skills ↗ |
What it does
Use when working on perf tasks.
Files
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.
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
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, 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.
- 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.
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.
Scoring & Calibration Guide
Reference guide for managers completing performance reviews. Use this to ensure consistent, evidence-based ratings.
OV Score Formula
OV = (Performance × 0.50) + (Potential × 0.25) + (LP Score × 0.25)Performance Rating (1-10) — Weight: 50%
Evaluate results delivered against expectations for the employee's role and level.
| Rating | Score | Definition | Evidence examples |
|---|---|---|---|
| Exceptional | 9-10 | Consistently exceeded expectations; outsized impact | Delivered ahead of schedule, solved problems beyond their scope, measurable impact on business metrics |
| Strong | 7-8 | Met all expectations, exceeded in some areas | Reliable delivery, some standout contributions, positive peer feedback on output |
| Solid | 5-6 | Met expectations for the role | Completed assigned work at expected quality, no major gaps or standout moments |
| Developing | 3-4 | Met some expectations; improvement needed | Missed deadlines, quality issues, needed more support than expected for level |
| Below Expectations | 1-2 | Did not meet expectations | Significant missed deliverables, quality problems, peer feedback reflects concern |
Calibration check: If you're giving a 9-10 to more than 20% of your team, you're likely inflating. Exceptional means exceptional.
Potential Rating (1-10) — Weight: 25%
Evaluate growth trajectory and readiness for increased scope.
| Rating | Score | Definition | Signals |
|---|---|---|---|
| High Potential | 9-10 | Ready for promotion within 1-2 quarters | Actively operating above their level, sought out by others for leadership, learning velocity is high |
| Growth Potential | 5-8 | Developing toward next level | Shows curiosity, takes on stretch assignments, improving quarter over quarter |
| Well-Placed | 1-4 | Strong in current role | Deep expertise in their domain, valuable where they are, may not aspire to or be ready for more scope |
Important: Well-Placed is not negative. A team of all "High Potential" people would be chaotic. You need depth and stability too.
Leadership Principles Rating — Weight: 25%
Rate each of the five principles, then convert to a numerical score.
| Rating | Points | What it means | Frequency target |
|---|---|---|---|
| Role Model (RM) | 10 | Exemplary; others should learn from them | ~5% of team per principle |
| Demonstrates (D) | 6 | Consistently shows this in their work | Most of the team |
| Developing (DV) | 3 | Inconsistent or needs growth | A few per team |
LP Score = average points across all 6 principles
Example: RM, D, D, D, D, DV → (10 + 6 + 6 + 6 + 6 + 3) / 6 = 6.17
The six principles
1. Ownership — Takes responsibility for outcomes, leads up and down, proactively solves problems without being asked. Never says "not my job."
2. Transparency — Communicates openly and honestly, shares context, surfaces problems early. Builds trust through candor.
3. Customer Obsession — Starts with the customer and works backward. Deeply understands user needs and earns their trust.
4. Strive for Excellency — Relentlessly high bar. Continuously raises standards for products, services, and processes.
5. Be Curious and Open Minded — Never done learning, seeks self-improvement. Explores new possibilities and acts on them.
6. Drive Results — Focuses on key inputs, delivers with the right quality and timeliness. Rises to the occasion despite setbacks.
Stack Rank Tiers
| Tier | OV Range | Target % | Implications |
|---|---|---|---|
| Top Tier (TT) | 8.5-10.0 | 20% | Priority for promotions, top compensation increases, stretch assignments |
| Highly Valued 3 (HV3) | 7.5-8.4 | 15% | Strong compensation increases, development opportunities |
| Highly Valued 2 (HV2) | 6.0-7.4 | 25% | Standard compensation increases, continued growth support |
| Highly Valued 1 (HV1) | 4.0-5.9 | 35% | Focused development plan to help reach next level |
| Least Effective (LE) | 1.0-3.9 | 5% | Requires immediate improvement; PIP required |
Common calibration mistakes
1. Central tendency — Rating everyone 5-7. If no one is exceptional and no one is struggling, the ratings aren't honest. 2. Recency bias — Weighting the last 2-3 weeks over the full quarter. Look at the whole body of work. 3. Halo effect — One strong trait inflating all scores. Someone can be an exceptional coder (high performance) but poor at collaboration (low LP on that principle). 4. Inflation — Giving high scores because you like the person or want to avoid a hard conversation. This is the most harmful mistake — it robs people of honest feedback. 5. Comparison anchoring — Rating someone based on who came before them in the review cycle rather than against role expectations.