performance-review · git:20260320.869847a · 2026-03-20 · sha256 293d91af038e90c7
performance-review git:20260320.869847aA
Immutable. This exact content never changes and is served at /api/v1/blob/293d91af038e90c7.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_napkqtb4buwdpjkg/293d91af038e90c7886c0b3ccaa5780be8929e57887fa128584dbb1cf5e43f86.json
Then /plugin install performance-review@markdownregistry-napkqtb4buwdpjkg in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: performance-review
description: Use this skill when writing performance achievement documents, self-assessments, peer feedback, PA documentation, or any career review writing. Trigger on keywords: performance review, PA, self-assessment, peer feedback, performance achievement, review cycle, annual review, accomplishments, sprint contribution.
---
# Performance Review Writing
## Core Principles
- Write only what you actually did — no inflation, no filler phrases
- Use "Assisted in..." when not the primary contributor
- Quantify where possible: coverage %, stories completed, time reduced
- Never use: "demonstrating strong commitment to...", "showcasing my passion for..."
- For peer feedback with limited collaboration: keep general, honest, safe
---
## Self-Assessment Format
### Accomplishment Writing Pattern
```
WEAK: "Worked on the BTT module"
STRONG: "Built Query Clarity Assessment Agent (US-2111704),
achieving 95%+ unit and integration test coverage"
WEAK: "Helped with UI work"
STRONG: "Assisted in BTT UI/UX enhancements (US-2068094),
contributing to LaunchDarkly feature flag implementation"
```
### Personal Reflection (One Flowing Paragraph)
- Write in first person, conversational, honest
- Cover: what you learned, what challenged you, what you want next
- Avoid: bullet points, headers, passive voice, corporate filler
---
## Peer Feedback Templates
**Strength:**
```
[Name] consistently [specific behavior] which [impact].
For example, [concrete but general example].
```
**Growth Area (constructive):**
```
One area where [Name] could develop is [skill/behavior].
I believe strengthening this would [positive outcome].
```
### Limited Collaboration Rule
- Keep it general: work ethic, communication style, team presence
- Do NOT mention specific story IDs
- Only state what you can directly verify
---
## Asking for Feedback
```
Hi [Name], completing my performance review and would value your input.
Two questions if you have a moment:
1. One thing I did well you'd want me to keep doing
2. One area where I could improve
Even a few sentences helps. Thanks!
```
---
## Pre-Submission Checklist
- [ ] Achievements are quantified where possible
- [ ] "Assisted in" used for non-primary contributions
- [ ] No filler phrases remain
- [ ] Personal reflection is prose, not bullets
- [ ] Required fields (EID, dates) are filled in
- [ ] Nothing is overstated