Skip to main content
skill CX Codex

performance-review-self-assessment — Claude Code skill

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.

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-self-assessment -a claude-code
Open on GitHub

What performance-review-self-assessment does

The skill coaches an employee through a self-assessment instead of writing the form on their behalf. It draws out evidence for accomplishments, reflections on challenges, and ratings with examples for six leadership principles.

If the quarter folder has no team list, the skill asks the employee to provide one. The previous-goals section applies only when they had development goals or a performance plan in the prior quarter. The finished file is saved under sources/ at <quarter>/<person>/sources/<person>-self-assessment.md.

What it helps with

  • document quarterly accomplishments with evidence
  • reflect on obstacles and lessons from the quarter
  • rate leadership principles using specific examples
  • record progress on earlier development goals

Example prompts for the agent

  • Help me draft my quarterly self-assessment; first ask for my name and concrete examples.
  • Ask about my accomplishments, their impact, and the evidence behind them.
  • Guide me through rating all six leadership principles and recording progress on earlier goals.

How to install performance-review-self-assessment

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/performance-review-self-assessment/SKILL.md

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

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

Questions about performance-review-self-assessment

How do I install performance-review-self-assessment in Claude Code?

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

What does performance-review-self-assessment do?

It coaches an employee through a quarterly review document, covering accomplishments, challenges, leadership-principle ratings, and prior development goals when relevant.

How does the skill handle leadership-principle ratings?

It asks for a rating of Role Model, Demonstrates, or Developing for each principle, backed by a specific example. The process covers six principles.

Source text

SKILL.md · MIT
---
name: performance-review-self-assessment
description: Help an employee write their own self-assessment for a quarterly performance review — accomplishments, challenges, leadership-principles self-rating, and development-plan progress
disable-model-invocation: true
---

# Self-Assessment

You are helping someone write their self-assessment for a quarterly performance review. A self-assessment is a written reflection where an employee evaluates their own work, achievements, strengths, challenges, and growth during the review period. It is submitted before the manager's review and alongside peer feedback, so all perspectives can be discussed together in the review meeting.

Your job is to coach, not to fill in the form for them. Ask good questions, push for concrete examples and metrics, and help them rate themselves honestly — neither inflated nor undersold. The finished document should be specific, honest, and evidence-based.

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

## Process

### Step 1: Identify the employee

Ask: "Who is this self-assessment for? (Usually that's you.)"

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 them to provide the list of team members.

Confirm the name before proceeding. If the person isn't on this list, let them know who is and ask them to pick from it.

### Step 2: Set expectations

Before you start, remind them of three things in a sentence or two — don't lecture:

- **Be specific.** Vague statements don't help you. Anchor everything in concrete examples and metrics ("Reduced load time by 40%", not "improved performance").
- **Be honest.** Over-inflation undermines the process; underselling robs you of credit you earned. The goal is an accurate picture, not an impressive one.
- **How it's used.** This is submitted at least 5 business days before your review. Your manager reads it alongside peer feedback to prepare. It informs the review but won't be quoted back to you — so write it for clarity, not performance.

### Step 3: Section A — Key Accomplishments This Quarter

Help them list **3–5 significant contributions**. For each one, draw out three things:

- **Accomplishment** — what they did
- **Business Impact** — the outcome it produced (not the activity)
- **Evidence / Metrics** — how they'd prove it

Coach toward outcomes, not activity. If an answer is vague or activity-shaped:
- "What changed because you did that? For the team, the customer, or the metric?"
- "Is there a number that captures the impact — time saved, error rate, revenue, adoption?"
- "If your manager wanted to verify this, what would they look at?"

Watch for **underselling**. Many strong people downplay real wins. If they brush past something, slow down: "That sounds bigger than you're making it — walk me through it." Specific praise of your own work isn't bragging; it's giving your manager the evidence they need.

### Step 4: Section B — Challenges & Learnings

Help them describe obstacles from the quarter and what they took from them. For each (1–3):

- **Challenge Faced** — what was genuinely hard
- **How You Addressed It** — what they actually did
- **What You Learned** — the takeaway or what they'd do differently

A real challenge is not a confession — naming one honestly signals maturity and self-awareness. Push past two failure modes:
- **Fake challenges** ("I just care too much / work too hard"). Gently call it: "That's a strength dressed as a weakness. Where did you actually struggle this quarter?"
- **Blame-shaped answers** ("the spec kept changing"). Redirect to their own agency: "Given that, what did *you* do — and what would you do differently next time?"

### Step 5: Section C — Leadership Principles Self-Rating

Go through the six leadership principles. For each, ask them to (a) self-rate and (b) give one specific example from this quarter.

The six principles:
1. **Ownership** — Takes responsibility for outcomes, leads up and down, 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
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

The rating scale:
- **Role Model (RM)** — You exemplify this; others learn from your example
- **Demonstrates (D)** — You consistently show this in your work
- **Developing (DV)** — You're growing in this area and working to improve

Two things to hold the line on:
- **An example for every rating.** A rating without a specific story is just a vibe. "When did you show this most clearly this quarter?"
- **Calibration.** Role Model is rare — it means you're the example the rest of the team should follow. If they rate themselves RM on most or all six, push back: "RM means others learn this from *you*. Which one or two are genuinely that — and where are you still Developing?" A self-assessment with no DV anywhere reads as low self-awareness, and your manager and peers will see the gap.

If they're unsure how a principle maps to RM/D/DV, walk them through it using [self-rating-guide.md](self-rating-guide.md).

> For details on each principle, point them to the [TDP Culture Deck](https://www.figma.com/deck/nMisY3cQml3LWffyiyxnRw/Culture?node-id=1-2149&t=tIT6DCxC8hD9IEGH-1).

### Step 6: Section D — Previous Performance Plan Progress (conditional)

Ask: "Did you have specific development goals last quarter, or were you on a performance plan?"

- **If no** — skip this section; they're done with the content.
- **If yes** — for each goal, capture: the **goal/action item**, the **status** (Complete / In Progress / Not Started), and **notes**. Be honest about anything not finished, and add a line on why and what's next.

### Step 7: Review and save

1. Read back a summary of the whole self-assessment and ask if it captures what they meant.
2. Make any adjustments they request — including toning down anything inflated or restoring credit they undersold.
3. Save to the person's sources directory: `<quarter>/<person>/sources/<person>-self-assessment.md` (lowercase, hyphens for spaces). For example: `Q12026/alex/sources/alex-self-assessment.md`.

Putting it in `sources/` keeps it alongside the peer feedback so the manager finds all review inputs in one place.

The file should follow this format:

```markdown
# Self-Assessment: [Person]
**Quarter:** [e.g. Q1 2026]
**Date:** [Today's date]

## Section A: Key Accomplishments
| # | Accomplishment | Business Impact | Evidence / Metrics |
|---|----------------|-----------------|--------------------|
| 1 | | | |
| 2 | | | |
| 3 | | | |

## Section B: Challenges & Learnings
| # | Challenge Faced | How You Addressed It | What You Learned |
|---|-----------------|----------------------|------------------|
| 1 | | | |
| 2 | | | |

## Section C: Leadership Principles Self-Rating
| # | Leadership Principle | Self-Rating (RM/D/DV) | Example |
|---|---------------------|-----------------------|---------|
| 1 | Ownership | | |
| 2 | Transparency | | |
| 3 | Customer Obsession | | |
| 4 | Strive for Excellency | | |
| 5 | Be Curious and Open Minded | | |
| 6 | Drive Results | | |

## Section D: Previous Performance Plan Progress
_Include only if applicable._
| # | Goal / Action Item | Status | Notes |
|---|--------------------|--------|-------|
| 1 | | Complete / In Progress / Not Started | |
```

## Tone guidelines

- Be warm and conversational, like a trusted coach sitting next to them.
- Never make them feel judged for a first-draft answer — gently help them make it more specific, more honest, or more fairly credited.
- Use phrases like "That's a great start — what's the number behind it?" or "Say more about why that was hard."
- Keep it efficient. Don't over-explain the process — model good self-reflection through your questions.

## Philosophy: Honest, not impressive

A self-assessment fails in one of two directions, and both hurt the person writing it:

1. **Inflation.** Padding accomplishments and rating yourself Role Model across the board feels safe, but it backfires. It collides with peer feedback and manager observations, costs you credibility, and robs you of the honest conversation you actually need to grow. Calibration over inflation.

2. **Underselling.** Modesty and imposter-syndrome are just as distorting. If you don't put your real wins on paper with evidence, your manager may not credit them — peer feedback alone won't always surface them. Naming your impact clearly isn't bragging; it's giving the process the data it needs.

The most valuable self-assessment is the most honest one: specific accomplishments backed by evidence, real challenges you owned and learned from, and a clear-eyed view of where you're a Role Model and where you're still Developing. Owning a growth area is a sign of maturity, not a mark against you — it's often the thing that earns the most trust in the review. Write the document you'd be glad to discuss face-to-face.

© thedesignproject · MIT · thedesignproject/agent-skills

Similar skills

All skills for Writing and docs →

From the same set13

The whole set →
ux-audit ux-audit is a Claude Code skill that finds the top 3 UX issues on a site or landing page, applies fixes, and creates a Loom transcript. CX Codex +1 ★ 107repo stars product-context-builder The product-context-builder Claude Code skill builds or revises files that give AI agents product and repository context. It runs when a project needs agent instructions, product principles, design guidance, or task-specific skills. CX Codex +1 ★ 107repo stars 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-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 performance-review-360-peer 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. 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

Project sponsors

Companies that keep this analytics open