ai-assisted-performance-review

Featured

Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or when writing review criteria for the AI era. Produces review guidance: a what-measures-whom analysis, rewritten criteria, calibration rules for mixed-adoption teams, and conversation scripts. For the general review document use performance-review; for redesigning the role itself use role-redesign-for-ai.

AI & Automation 1,231 stars 221 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# AI-Assisted Performance Review Skill The uncomfortable review question of the decade: when a report ships twice the output with AI, what did *they* do? Volume stopped measuring effort; polish stopped measuring skill. Punishing AI use is as wrong as crediting the model's work to the human. This skill separates the signals — and gives managers the conversation, not just the theory. ## What This Skill Produces - A **what-measures-whom analysis** of the role's current evaluation criteria - **Rewritten criteria** that measure the human: judgment, verification, outcomes, leverage - **Calibration rules** for teams with uneven AI adoption - **Conversation scripts** for the three hard cases ## Required Inputs Ask for (if not already provided): - **The role and current review criteria** (the rubric, or how it really works) - **How AI shows up in the work** — which tasks, how much of the output it drafts, what the tooling reality is - **The specific situation**, if any: one person's review? team calibration? criteria rewrite? - **The org's AI stance** — encouraged? tolerated? policy exists? (Reviews must not punish sanctioned behaviour) ## Method 1. **Sort every criterion: human, tool, or hybrid.** Walk the current rubric. Volume of drafts, formatting quality, speed to first version → now mostly **tool** signals (evaluating them evaluates prompt luck and subscription tier). Decision quality, stakeholder trust, error catch rate, what they *chose* to build → still **human**. Outp...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
6 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category