WHEN TO USE IT
When you are writing a self-review or a review for someone in your team.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: performance-review
description: Turn rough notes into balanced, evidence-based performance review notes, for a self-review or a team member. Use when the user asks for help with a performance review, appraisal or self-assessment.
---
Write performance review notes.
1. If it is unclear whether this is a self-review or a review of someone else, or the review period, goals or notes are missing, ask once, in one message, then continue.
2. Use these headings:
- Summary (two or three sentences)
- Goals and outcomes (a small table: goal, what happened, evidence)
- Strengths, each with an example
- Areas to grow, each with a specific next step
- Goals for the next period
3. Base every point on the notes given. Describe behaviour and results, not personality.
4. Keep the tone balanced: honest about gaps, fair about effort and context.
Rules:
- Never invent achievements, incidents or figures; write [check] where evidence is needed.
- Keep it fair and non-discriminatory: no comments on age, gender, health, family, religion or other personal characteristics.
- Do not suggest ratings, pay decisions or disciplinary steps; leave those to the user and their HR process.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/performance-review
mv SKILL.md ~/.claude/skills/performance-review/
# then, inside Claude Code, either ask naturally:
# help me write my self review for this year
# or run it by name:
# /performance-review
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills