mcpbeat Sign in

Performance Management Agent Skill

Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.

840 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
220
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/cbrock84/headcount --skill performance-management

The instruction itself

6 sections, as written by the author

Performance management

Most review systems are an expensive annual ritual that surprises nobody and improves nothing. The

work happens in the ordinary week; the cycle should record it, not discover it.

**Performance documentation carries legal weight, particularly around termination, discrimination and

accommodation. Employment law varies by jurisdiction — involve qualified counsel before acting on

sustained underperformance.**

Expectations before assessment

Nobody can be fairly assessed against a standard they were not given. Expectations need to be

specific to the level, written down, and shared before the period rather than produced during review

as justification.

Separate two axes deliberately, because conflating them is the most common structural flaw:

  • Outcomes — what was delivered, which is partly situational.
  • Behaviors — how it was done, which is more within the person's control.

Someone who delivered through a collapsing market and someone who delivered by scorching the earth

around them are different cases. A single blended rating hides both.

Feedback in the week, not the quarter

Feedback is useful proportional to its proximity to the event. Specific, immediate, and about the

work: what happened, what the effect was, what to do differently.

The annual cycle should contain nothing new. A review that surprises someone is a reporting failure

by their manager, and the surprise is the finding.

Calibration

Managers rate differently — some systematically generously, some harshly — and the differences are

invisible until ratings sit side by side. Calibration exists to make comparison possible, not to fit

a distribution.

Forced distributions are the failure mode here. On small teams they are statistically meaningless,

and they reliably destroy exactly the collaboration the values section claims to reward.

Calibrate on evidence: what was delivered, at what level, against what expectation. A rating that

cannot be defended with an example is a preference.

Sustained underperformance

Address it early and directly. Late intervention is worse for everyone, most of all the person, who

has been allowed to believe they were fine.

Establish which it is first, because the remedies do not overlap: unclear expectations, missing

capability, a role mismatch, or something outside work. Treating a role mismatch as a capability

problem produces a performance plan that fails for reasons nobody named.

Where a formal plan is warranted it needs specific outcomes, a real timeframe, defined support, and a

stated consequence. A plan that is only a paper trail for a decision already taken is recognized as

such and does damage well beyond the individual.

Never

  • Assess against expectations that were not set in advance.
  • Deliver news in a review that should have been given weeks earlier.
  • Force a distribution on a small team.
  • Start a performance plan without deciding whether the problem is capability or fit.

How to use it

Copy the folder

Take cbrock84/performance-management from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.