TRIGGER THIS when conducting performance reviews, writing manager feedback, creating self-assessments, building peer feedback, developing PIPs, creating development plans, or handling difficult performance conversations. Helps write constructive, specific, actionable feedback that develops performance and documents performance management appropriately.
npx skills add https://github.com/w95/awesome-claude-corporate-skills --skill performance-review-assistant
This skill helps managers and HR professionals conduct effective performance reviews with constructive, specific, and actionable feedback. It provides frameworks for writing compelling performance narratives, gathering 360 feedback, creating development plans, building performance improvement plans (PIPs) when needed, and conducting conversations that strengthen employee performance and engagement.
360-Degree Feedback Approach:
Review Dimensions:
Typical 5-Point Rating System:
1 - Below Expectations / Does Not Meet Standards:
2 - Partially Meets Expectations / Needs Improvement:
3 - Meets Expectations / Fully Proficient:
4 - Exceeds Expectations / High Performer:
5 - Far Exceeds Expectations / Outstanding Performer:
Note: Avoid rating inflation. Approximately 10% of employees should be in top two categories, 70-80% in middle, 10% below.
Structure for Each Competency/Dimension:
What They Did Well: Start with strengths and specific examples
Opportunity for Growth: Honest feedback on development areas
Trajectory & Overall Assessment:
Key Principles:
Help employees reflect on their own performance:
Self-Assessment Prompt Template:
PERFORMANCE SELF-ASSESSMENT
Please reflect on your performance over the review period. Be honest and specific. This is for your own development and to help your manager understand your perspective.
ROLE RESPONSIBILITIES
Describe how well you performed your core responsibilities:
- [Key responsibility 1]: [How well did you perform it?]
- [Key responsibility 2]: [How well did you perform it?]
- [Key responsibility 3]: [How well did you perform it?]
Key achievements and impact:
- What are you most proud of accomplishing this year?
- What measurable impact did you have?
- What contributions surprised you or exceeded your expectations?
COMPETENCY DEVELOPMENT
Which of these competencies did you develop this year?
- [Competency]: What did you learn? How are you using it?
- [Competency]: What did you learn? How are you using it?
- [Competency]: What did you learn? How are you using it?
Where do you see your biggest growth opportunity?
What skills do you want to develop next?
What support do you need from your manager or organization?
VALUES & CULTURE
How have you demonstrated [Company Value 1]?
Describe a specific example:
How have you demonstrated [Company Value 2]?
Describe a specific example:
COLLABORATION & TEAMWORK
Describe your collaboration with your team and cross-functional partners.
Who did you work effectively with and why?
Where did you struggle to collaborate?
How did you contribute to team success?
LOOKING FORWARD
What are your growth goals for next year?
What skills or experiences do you want to develop?
What role or direction interests you?
What support do you need from your manager?
What do you want your manager to know about your perspective on your performance?
Selecting Peer Reviewers (3-5 ideal):
Peer Feedback Prompts:
PEER FEEDBACK FORM
You've been asked to provide feedback on [Name] for their performance review. Your honest, constructive feedback is valuable and will be kept confidential (comments will be synthesized to protect anonymity).
1. WHAT ARE THEIR KEY STRENGTHS?
What does [Name] do really well? Give specific examples of impact.
2. WHERE CAN THEY IMPROVE?
What's one area where [Name] could develop or grow? How would that help the team or organization?
3. COLLABORATION
How is [Name] to work with? Share an example of effective (or challenging) collaboration.
4. RELIABILITY
Can you count on [Name] to follow through? Give an example.
5. OVERALL IMPRESSION
How much would you want [Name] on your team? Why?
Synthesizing Feedback:
Before the Conversation:
Conversation Flow:
Opening (5 minutes):
Their Perspective (10 minutes):
Strengths & Accomplishments (15 minutes):
Growth Areas & Opportunities (20 minutes):
Development Plan (15 minutes):
Overall Assessment & Rating (5 minutes):
Forward & Closing (5 minutes):
Post-Conversation:
Use when performance is significantly below expectations and needs documented improvement.
When to Use a PIP:
PIP Structure:
PERFORMANCE IMPROVEMENT PLAN
Employee: _________________ Position: _________________ Date: _________
Manager: _________________ HR Partner: _________________
PERFORMANCE ISSUE(S)
[Be specific and factual]
- Specific example of what's not meeting expectations
- Impact on team/organization
- How this differs from role expectations
- Previous feedback given (dates, details)
IMPROVEMENT EXPECTATIONS
[Clear, measurable outcomes]
- By [date], employee will [specific outcome]
- Success will be measured by [specific metrics]
- By [date], employee will [specific outcome]
- Success will be measured by [specific metrics]
SUPPORT & RESOURCES PROVIDED
- [Coaching or mentoring]: [Details]
- [Training or skill-building]: [Details]
- [Adjusted responsibilities]: [Details]
- [Manager check-in frequency]: [Details]
- [Other resources]: [Details]
TIMELINE
- PIP Duration: [Typical 30-90 days]
- Check-in frequency: [Weekly or bi-weekly]
- Formal review date: [End of PIP]
SUCCESS CRITERIA
At the end of this PIP, [Employee] will have:
- [Specific outcome achieved]
- [Specific outcome achieved]
- [Specific outcome achieved]
CONSEQUENCES
If improvement is not demonstrated by [date], the outcome may include:
- Continued performance management
- Reassignment to different role
- Termination of employment
Employee Acknowledgment:
I acknowledge that I have discussed this Performance Improvement Plan with my manager and understand the expectations and timeline. I also understand that failure to meet the improvement expectations may result in further employment consequences.
Employee Signature: _________________ Date: _________
Manager Signature: _________________ Date: _________
HR Partner: _________________ Date: _________
PIP Best Practices:
For growth-oriented employees, create development plans:
DEVELOPMENT PLAN
Employee: _________________ Role: _________________ Date: _________
Manager: _________________
GROWTH GOALS (1-2 year horizon)
Goal 1: [Specific competency or skill to develop]
Why this matters: [How it advances career, role, or organization]
Current level: [Where they are now]
Target level: [Where they'll be in 12-24 months]
Success indicators: [How we'll measure progress]
Learning approach:
- [ ] Formal training/course: [Details]
- [ ] Stretch assignment: [Project, timeline]
- [ ] Mentoring: [With whom, frequency]
- [ ] Self-directed learning: [Reading, resources]
- [ ] Community involvement: [Speaking, community role]
Timeline: [Start date] to [completion target]
Checkpoints: [When will we review progress]
Goal 2: [Specific competency or skill to develop]
[Same structure as Goal 1]
LONGER-TERM CAREER VISION
Where do they want to go in 3-5 years? [Role, impact, growth]
What capabilities need to develop? [List]
What experiences would help? [Stretch projects, moves, etc.]
SUPPORT FROM MANAGER
- [How often will we discuss progress]
- [What opportunities will manager create]
- [What coaching or feedback]
- [Resource allocation]
RESOURCES & LEARNING OPPORTUNITIES
- [Course or certification]: [Timeline, investment]
- [Books or reading]: [Titles]
- [Mentoring]: [Who, frequency]
- [Conference or event]: [Dates, investment]
- [Project or stretch role]: [Details]
REVIEW CADENCE
- Quarterly review: [Discuss progress, adjust as needed]
- 6-month review: [Assess progress, celebrate wins]
- Annual review: [Comprehensive evaluation against goals]
---
QUARTERLY PROGRESS REVIEWS
Quarter 1 Review (Date: _____):
Progress on Goal 1: [What's happened]
Progress on Goal 2: [What's happened]
Adjustments needed: [Any changes to plan]
Next quarter focus: [What comes next]
[Repeat for each quarter]
Be Specific:
Use Specific Examples:
Connect to Impact:
Balance Strengths & Growth:
Avoid Common Pitfalls:
10. Follow-up: Don't end with review; continue development
Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors.
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Translate visa application documents (images) to English and create a bilingual PDF with original and translation
Write, review, and edit documentation files with consistent structure, tone, and technical accuracy. Use when creating docs, reviewing markdown files, writing READMEs, updating `/docs` directories, or when user says "write documentation", "review this doc", "improve this README", "create a guide", or "edit markdown". Do NOT use for code comments, inline JSDoc, or API reference generation.
Real-time Constitution compliance checker for devflow documents. Blocks partial implementations and hardcoded secrets during file editing.
Write self-documenting code with minimal, evergreen comments that explain complex logic without describing recent changes or temporary fixes. Use this skill when writing code comments, documentation strings, explaining complex algorithms, clarifying business logic, or deciding whether code needs comments. Apply when working with any source code files where comments or documentation might be added, ensuring comments remain relevant, helpful, and focused on explaining why rather than what the code does, while preferring clear code structure and naming over excessive commenting.
Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.
Draft a structured investment committee memo for PE deal approval. Synthesizes due diligence findings, financial analysis, and deal terms into a professional IC-ready document. Use when preparing for investment committee, writing up a deal, or creating a formal recommendation. Triggers on "write IC memo", "investment committee memo", "deal write-up", "prepare IC materials", or "recommendation memo".
Take w95/performance-review-assistant from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.