
Performance Review Self Assessment
- 49 installs
- 68 repo stars
- Updated July 13, 2026
- thedesignproject/agent-skills
Use this skill when working on review activities during the ship phase.
About
Performance Review Self skill provides code review and analysis. Complexity: intermediate.
- Self
- Assessment
- Review
Performance Review Self Assessment by the numbers
- 49 all-time installs (skills.sh)
- +10 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #588 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-self-assessmentAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 49 |
|---|---|
| repo stars | ★ 68 |
| Last updated | July 13, 2026 |
| Repository | thedesignproject/agent-skills ↗ |
What it does
Use this skill when working on review activities during the ship phase.
Files
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.
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.
For details on each principle, point them to the TDP Culture Deck.
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:
# 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.
Self-Rating Guide
Reference for writing an honest, specific self-assessment. Use this when helping someone draft accomplishments, name challenges, and self-rate on the leadership principles.
Core principle: Honest, not impressive
A self-assessment is not a sales pitch and not a confession. It's an accurate, evidence-based picture of your quarter that your manager reads alongside peer feedback before your review.
It fails in two directions, and both hurt you:
- Inflation protects your ego in the moment. It collides with peer feedback and manager observations, costs you credibility, and denies you the honest conversation you need to grow.
- Underselling feels humble but it's just as distorting. Wins you don't write down — with evidence — may not get credited. Modesty is not a gift to anyone.
The goal is calibration: claim what you earned, own what you're still building, and back both with specifics.
Writing strong accomplishments (Section A)
Describe outcomes, not activity. Activity is what you did; outcome is what changed because you did it.
| Instead of (activity) | Try (outcome + evidence) |
|---|---|
| "Worked on the onboarding flow" | "Redesigned onboarding; activation rate rose from 48% → 61% over the quarter" |
| "Helped the team a lot" | "Unblocked 3 engineers on the auth migration, cutting an estimated week off the timeline" |
| "Improved performance" | "Cut p95 page load from 3.2s to 1.9s (–40%)" |
| "Did a lot of design reviews" | "Ran weekly design crits; shipped 4 features with zero post-launch design rework" |
For each accomplishment, be able to answer:
- Impact — who benefited and how (team, customer, business metric)?
- Evidence — what would your manager look at to verify it?
If a number genuinely doesn't exist, use a concrete observable instead ("zero rollbacks", "shipped on the committed date", "adopted by both pods").
Naming challenges honestly (Section B)
A challenge is not an admission of failure — it's evidence of self-awareness and growth. The structure that works:
1. What was genuinely hard — a real obstacle, not a humblebrag. 2. What you did — your actual response, even if imperfect. 3. What you learned — the takeaway, or what you'd do differently.
Avoid the two traps:
- Fake weakness ("I care too much", "I work too hard"). These read as evasive. Name something real.
- Blame ("requirements kept changing", "QA was slow"). Even when true, the assessment is about your response. What did you do within the constraints, and what would you change next time?
Self-rating the leadership principles (Section C)
Rate yourself on each of the six principles and give one specific example per rating.
The scale
| Rating | What it means | Honest signal |
|---|---|---|
| Role Model (RM) | You exemplify this; others learn from your example | Rare. Reserve for the one or two principles where you're genuinely the example others follow. |
| Demonstrates (D) | You consistently show this in your work | The strong, normal rating. Most principles for most people land here. |
| Developing (DV) | You're growing in this area and working to improve | A sign of maturity, not a mark against you. Naming a real DV builds trust. |
Calibration
- Role Model is rare. If you rate yourself RM on most or all six, the scale isn't doing its job — and the gap with peer/manager views will stand out. Ask yourself: "Would my teammates point to me as the example for this?"
- A self-assessment with no DV reads as low self-awareness. Almost everyone is genuinely developing somewhere. Finding it is a strength.
- Every rating needs a story. A rating with no example is just a vibe. Tie each to a specific moment this quarter.
The six principles
1. Ownership — Takes responsibility for outcomes, leads up and down, proactively solves problems without being asked. Never says "not my job."
- RM: others copy how you take end-to-end ownership. D: you reliably own your work and outcomes. DV: you sometimes wait to be told, or hand off problems you could carry.
2. Transparency — Communicates openly and honestly, shares context, surfaces problems early. Builds trust through candor.
- RM: you set the standard for honest, early communication. D: you share context and flag issues. DV: you tend to sit on problems or under-communicate.
3. Customer Obsession — Starts with the customer and works backward. Deeply understands user needs and earns their trust.
- RM: you pull the whole team back to the customer. D: you keep the user in mind in your work. DV: you default to internal or technical convenience over user need.
4. Strive for Excellency — Relentlessly high bar. Continuously raises standards for products, services, and processes.
- RM: you raise the bar for everyone around you. D: you hold a high bar for your own work. DV: you're still calibrating what "great" looks like here.
5. Be Curious and Open Minded — Never done learning, seeks self-improvement. Explores new possibilities and acts on them.
- RM: your learning visibly pulls the team forward. D: you seek out growth and new ideas. DV: you're building the habit of stepping outside what you know.
6. Drive Results — Focuses on key inputs, delivers with the right quality and timeliness. Rises to the occasion despite setbacks.
- RM: you deliver under pressure in a way others learn from. D: you consistently land your commitments. DV: you're working on follow-through or prioritization.
Common self-assessment mistakes
1. Vagueness — "Improved the product." Without specifics, it's invisible. Add the what, the impact, the evidence. 2. Inflation — Padding wins or rating yourself RM everywhere. It collides with peer feedback and costs you credibility. 3. Underselling — Leaving real wins off the page out of modesty. If you don't write it down, it may not count. 4. Recency bias — Only remembering the last few weeks. Review the whole quarter — calendar, shipped work, notes — before you write. 5. Activity over impact — Listing what you were busy with instead of what changed because of it. 6. No growth areas — Claiming you're a Role Model at everything. It reads as a lack of self-awareness, not strength.