plugins/hr-people-ops/skills/performance/performance-review-assistant/SKILL.md
Write constructive, specific performance reviews that drive growth and development. Use this skill when writing performance reviews, giving feedback, or preparing for review conversations. Activate when: performance review, employee review, feedback, annual review, quarterly review, evaluation.
npx skillsauth add latestaiagents/agent-skills performance-review-assistantInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Write effective performance reviews that drive growth and development.
# Performance Review: [Employee Name]
**Review Period:** [Start Date] - [End Date]
**Reviewer:** [Manager Name]
**Date:** [Review Date]
## Overall Performance Summary
[2-3 sentences summarizing overall performance and impact]
## Key Accomplishments
1. [Specific achievement with measurable impact]
2. [Another achievement with context]
3. [Third achievement]
## Areas of Strength
- [Strength 1 with specific example]
- [Strength 2 with specific example]
## Areas for Development
- [Development area 1 with specific example and suggestion]
- [Development area 2 with specific example and suggestion]
## Goals for Next Period
1. [SMART goal 1]
2. [SMART goal 2]
3. [SMART goal 3]
## Overall Rating
[Rating according to company scale]
**Situation:** During the Q3 product launch...
**Behavior:** You proactively identified a critical dependency issue and coordinated with three teams to resolve it before it impacted the timeline.
**Impact:** This saved an estimated two weeks of delay and demonstrated strong cross-functional leadership.
Vague (Poor):
"Sarah is a great team player and always positive."
Specific (Good):
"Sarah consistently supports her teammates. When the backend team was behind on the API integration, she volunteered to help debug issues despite her own full workload. This collaboration helped the team deliver on time."
Vague (Poor):
"John needs to improve his communication."
Specific (Good):
"John would benefit from providing more context in written updates. In the Q2 project update, stakeholders had questions that could have been preemptively addressed. I recommend using a structured format that includes status, blockers, and next steps."
| Rating | Label | Description | Distribution | |--------|-------|-------------|--------------| | 5 | Exceptional | Consistently exceeds all expectations, role model | ~5-10% | | 4 | Exceeds | Regularly exceeds expectations in key areas | ~20-25% | | 3 | Meets | Fully meets expectations, solid performer | ~50-60% | | 2 | Developing | Partially meets expectations, improvement needed | ~10-15% | | 1 | Does Not Meet | Significantly below expectations | ~5% |
When assigning ratings, ask:
**Exceeds Expectations:**
"[Name] has become the team's go-to expert on [technology/skill]. They not only deliver high-quality work but also mentor others. Example: They created comprehensive documentation for our deployment process that reduced onboarding time by 50%."
**Meets Expectations:**
"[Name] demonstrates solid [skill] abilities and consistently delivers quality work. They successfully completed [specific project] on time and within scope."
**Needs Development:**
"While [Name] shows foundational knowledge of [skill], there's opportunity for growth in [specific area]. I recommend [specific development action] to build proficiency."
**Exceeds:**
"[Name] excels at tailoring communication to the audience. Their executive summary of the Q3 results was praised by leadership for its clarity. They also effectively facilitated difficult cross-team discussions."
**Meets:**
"[Name] communicates clearly in meetings and written updates. Stakeholders receive timely information about project status."
**Needs Development:**
"[Name] would benefit from more proactive communication, especially when priorities shift. I recommend sending weekly status updates and flagging blockers earlier."
**Exceeds:**
"[Name] leads by example and inspires others. When the team faced a challenging deadline, they rallied the group and maintained morale. Two team members have cited [Name] as instrumental in their growth."
**Meets:**
"[Name] effectively leads their projects and provides guidance to junior team members when asked."
**Needs Development:**
"[Name] has opportunities to increase their influence beyond their immediate work. I encourage them to share their expertise more broadly through lunch & learns or documentation."
**Framework:**
1. State the observation factually
2. Explain the impact
3. Listen to their perspective
4. Collaboratively problem-solve
5. Agree on specific next steps
**Example:**
"I want to discuss the timeline slippage on Project X. The milestone was missed by two weeks, which impacted the marketing launch. I'd like to understand what happened from your perspective, and then let's figure out how to prevent this going forward."
# Performance Improvement Plan
**Employee:** [Name]
**Manager:** [Name]
**Start Date:** [Date]
**End Date:** [Date - typically 30/60/90 days]
## Current Performance Gap
[Specific, documented issues with examples]
## Expected Performance Standards
[Clear, measurable expectations]
## Support Provided
- [Resource 1: training, mentorship, etc.]
- [Resource 2]
## Milestones & Check-ins
| Date | Milestone | Status |
|------|-----------|--------|
| Week 2 | [Specific milestone] | |
| Week 4 | [Specific milestone] | |
| Week 8 | [Specific milestone] | |
## Consequences
[Clear statement of what happens if improvement is not achieved]
**Signatures:**
Employee: _______________ Date: ___
Manager: _______________ Date: ___
HR: _______________ Date: ___
Provide these to employees before reviews:
1. What are you most proud of accomplishing this period?
2. What challenges did you face, and how did you handle them?
3. What skills have you developed or improved?
4. Where do you want to grow in the next period?
5. What support do you need from your manager?
6. What feedback do you have for your manager or team?
development
Test skills for correct activation, content quality, and regression — both automated checks (frontmatter validity, lint) and manual verification (query-suite activation testing). Covers CI integration and how to catch skill regressions before users do. Use this skill when adding skills to a repo, setting up CI for a skill library, or debugging "the skill exists but doesn't work". Activate when: test skills, validate skills, skill CI, skill linting, skill activation test, skill regression.
documentation
Write the YAML frontmatter for a SKILL.md file so it activates reliably — name, description, and activation keywords that the model matches against. Covers length, tone, and the most common frontmatter mistakes. Use this skill when authoring a new skill, fixing a skill that isn't auto-activating, or reviewing skills for publication. Activate when: SKILL.md frontmatter, skill description, skill activation, skill YAML, write a skill, author a skill.
development
Design skills that fire at the right moment — neither over-eager (noise) nor under-eager (silent). Covers activation specificity, trigger phrases, disambiguation between overlapping skills, and debugging activation. Use this skill when multiple skills could fire on the same query, a skill never fires, or a skill fires too often. Activate when: skill won't activate, skill over-activates, overlapping skills, skill triggers, skill selection, skill disambiguation.
development
Structure SKILL.md content so the model reads just enough — concise summary up front, progressively deeper detail, examples on demand. Covers section ordering, length budgets, when to split into multiple skills. Use this skill when writing or refactoring a skill body, one skill has grown too long, or a skill is wordy but not useful. Activate when: SKILL.md structure, skill content, skill too long, split skill, progressive disclosure, skill body.