The review you'd stand behind if they asked you to explain any line of it.
The tool that pushes every claim in a performance review back to a specific behavior and a specific instance, so the review actually helps the person improve instead of protecting your afternoon.
Most performance reviews fail the same way: three genuine positives, one vague concern buried in paragraph four, and a closing line about continuing to grow. The employee reads it, feels fine, and nothing changes, because nothing specific enough to act on was ever said.
This tool pushes past the trait to the behavior, past the vibe to the dated instance, and forces one clear message instead of ten diluted ones. It won't write a review from nothing; it needs your actual observations to work with.
Same review, run two ways.
One version protects the conversation. The other one is actually useful to the person reading it.
A manager is writing an annual review for a marketing manager who's strong on execution but has had two visible conflicts with other departments this year.
You ask Claude to draft a performance review from your notes. You get something professional, balanced, and diplomatically worded, three strengths, one softened concern about collaboration.
It reads well and changes nothing, because "has room to grow in stakeholder management" doesn't tell the person what they actually did or what to do differently.
It pushes every claim back to a specific instance before it goes in the draft:
- →"Needs to work on collaboration" becomes two dated incidents with specific impact
- →The strongest quarter on the team gets cited with the actual number, not just praised generically
- →The one message that matters most is identified before the rest of the review is drafted around it
The finished draft states what happened plainly, in the room, in front of six people, rather than in HR euphemism that empties the sentence of information, and closes with one checkable, forward-looking goal instead of a vague call to improve.
The cold version was diplomatic. This one is actually going to change something.
- ✦Managers writing reviews for people with genuinely mixed performance
- ✦Anyone avoiding a review because the honest version feels uncomfortable to write
- ✦Teams standardizing what a specific, defensible review actually looks like
- →performance-review-writer.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to
~/.claude/skills/ - →performance-review-writer-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
- →A README inside the zip with install steps for Claude, ChatGPT, Gemini, and the API
What it does with a real question.
I need to write the annual review for a senior designer on my team. She consistently delivers high-quality work and mentors juniors well, but misses internal deadlines, resists written documentation, and twice left a project handover unclear. I want the review to be honest without damaging someone I want to keep.
Lead with the pattern, not the praise. The one message that matters most here is that her work is excellent and her reliability around it is not, because the deadline misses, the resistance to documentation and the two unclear handovers are one habit: she treats the work as the deliverable and the coordination around it as optional. If the review presents these as three separate nitpicks after a warm opening, she'll hear "great job" and nothing will change. Name the pattern as the central point, then let the strengths prove you mean it when you say you want to keep her.
Keep the strengths as specific as the concerns. Cite the project where her quality made a difference, and the junior designer whose growth you can trace to her mentoring. Retention is served by being believable, and generic praise reads as padding.
State the concerns without euphemism. Say which deadlines slipped, whether she flagged the risk beforehand, and what the two handovers cost the people who inherited them. Then frame the stakes honestly: at her level, others rely on her reliability as much as her craft.
Your concrete next move: write the handover and deadline-flagging goals first, in checkable form, such as "a written handover note before any project transitions" and "flag a deadline risk 48 hours ahead." Build the review around those goals. If you have never said this to her directly, schedule that conversation before the review lands.
The full Tool runs the whole procedure and writes the complete deliverable, not this excerpt.
Written by claude-sonnet-5-5 with this Tool loaded, 2026-10-11. Checked automatically for length and for copied framework text.
No subscription · free updates within v1.x
Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable
Before you buy.
How is this different from just asking Claude directly?
Asked cold, Claude drafts a diplomatic, balanced review from whatever notes you give it, softening language until real concerns barely register. This pushes every claim back to a specific behavior and dated instance, forces you to name the one message that matters most, and drafts development areas directly enough that the person actually knows what to change.
Will this work with ChatGPT, Gemini, and other LLMs?
Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.
Can I share this with my team?
It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Tool itself in the hands of a whole team, email hello@authority.md about team licensing.
What if it doesn't work for me?
If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.
Performance Review Writer is a drafting tool. Not HR or employment-law advice; consult your HR function or counsel on documentation and legal requirements specific to your jurisdiction.