跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

performance-review-self-assessment

Help an employee write their own self-assessment for a quarterly performance review — accomplishments, challenges, leadership-principles self-rating, and development-plan progress

thedesignproject · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

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

技能说明


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.

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
阅读完整来源 ↗