Skip to content
Back to skills

Performance Review Writer

ASecurity

Write compelling self-assessments and peer reviews with evidence-backed impact narratives.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsgoperformance

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aicodedecode/awesome-muse-skills --skill performance-review-writer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Performance Review Writer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Performance Review Writer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-performance-review-writer/badge)](https://www.skillsdirectory.com/skills/aicodedecode-performance-review-writer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: performance-review-writer
description: Write compelling self-assessments and peer reviews with evidence-backed impact narratives.
category: career
---

## Overview

Performance reviews determine compensation, promotion, and reputation — yet most
people write them
in an hour the night before, listing tasks instead of impact. This skill helps
you write
self-reviews that make your case undeniable: structured around outcomes, backed
by evidence, honest
about growth areas, and calibrated to your company's rating scale.

## When to use

- Writing an annual or mid-year self-assessment

- Drafting peer or upward feedback for colleagues

- Preparing a performance improvement plan (PIP) response

- Calibrating self-ratings against company competencies

- Collecting feedback quotes to support a promotion case

## Core concepts

- - - **Impact, not activity.** "Shipped the new billing flow" is activity.
  "Shipped billing flow 3
  weeks early; reduced failed payments 31%, recovering ~$400K ARR" is impact.
Every bullet needs a
  so-what.
- - - **The brag document habit.** Keep a running doc year-round: wins, metrics,
  praise quotes, hard
  problems solved. Reviews written from memory in December lose half the
evidence.
- - - **Map to the rubric.** Companies rate against competencies or values.
  Explicitly tag each
  achievement to a competency ("Ownership: ...", "Customer focus: ...") so
calibrators don't have to
  guess.
- - - **Own the growth areas.** Naming 1-2 real development areas with a plan
  signals maturity and
  disarms critics. Pick genuine-but-safe ones, never your actual derailers — fix
those separately,
  quietly.
- - - **Peer reviews are currency.** Specific, generous peer feedback builds
  allies who return the
  favor. Vague praise ("great to work with") is forgettable; cite the exact
moment they helped.
- - - **Ratings need a narrative.** If you rate yourself "exceeds," every
  paragraph must justify it.
  Inconsistency between rating and evidence is the fastest way to lose
credibility in calibration.

## Practical workflow

1. 1. 1. **Gather raw material.** Pull from the brag document: projects,
   metrics, feedback quotes,
   launches, incidents handled. If no brag doc exists, reconstruct from
calendars, commit history,
   and messages.
2. 2. 2. **Study the rubric.** Read the company's competencies and rating
   definitions. Note what
   "exceeds" actually requires — it's usually scope, influence, or sustained
excellence, not just
   doing your job well.
3. 3. 3. **Draft the self-review.** Structure: 3-5 headline accomplishments
   (each with metric +
   business impact), 1-2 growth areas with concrete development actions, and
goals for next cycle.
   Lead with the strongest win.
4. 4. 4. **Add the evidence layer.** For each claim: numbers, links to
   docs/launches, and 1-2 verbatim
   quotes from stakeholders. Evidence turns assertions into facts.
5. 5. 5. **Write peer reviews.** For each peer: 2-3 specific strengths with
   examples, 1 constructive
   suggestion framed as growth. Submit on time — late peer reviews signal
disengagement.
6. 6. 6. **Pressure-test.** Read it as your skip-level manager would: Is the
   impact obvious? Are
   ratings justified? Would this survive calibration against peers? Trim
anything that weakens the
   case.
7. 7. 7. **Prepare for the conversation.** The review meeting matters as much as
   the doc. Prepare 2-3
   talking points, anticipate pushback on ratings, and have your next-cycle
goals ready.

## Common pitfalls

- - - **Writing it the night before.** Rushed reviews read rushed. Start 2-3
  weeks early and iterate —
  or better, maintain the brag doc all year.
- - - **Underselling ("just doing my job").** If you don't advocate for your
  impact, nobody will.
  Calibration committees only see what's written.
- - - **Overselling with no proof.** Grand claims without metrics invite
  skepticism and invite harder
  questions. Every superlative needs a receipt.
- - - **Ignoring the growth section.** Leaving it blank or writing "none" looks
  arrogant or oblivious.
  Everyone has growth areas; naming them is strength.
- - - **Generic peer feedback.** "X is awesome" helps no one. Specificity is the
  gift: describe what
  they did, why it mattered, and the effect on you or the team.
- - - **Surprises in the meeting.** If your manager's view differs wildly from
  your self-review,
  that's a communication failure from the past 6 months, not a writing problem.
Fix with regular
  1:1s next cycle.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…