Agent skill

Managing High Performers

by manager-dot-dev in manager-dot-dev/manager-skills

Guides engineering managers through the specific challenges of managing top engineers — produces a four-quadrant ability/confidence diagnostic, the Rock Star vs.

MITAuto-check passedBusiness, Finance & HR

Install Managing High Performers

skills CLI
$ npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install manager-dot-dev/manager-skills managing-high-performers --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/manager-dot-dev/manager-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/managing-high-performers .claude/skills/managing-high-performers && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
managing-high-performers
GitHub stars
114
Token cost
~2.7k tokens
SKILL.md length
1,526 words
Files
2 (incl. references)
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Guides engineering managers through the specific challenges of managing top engineers — produces a four-quadrant ability/confidence diagnostic, the Rock Star vs.

  • Works in 5 steps: Type of high performer: rock star,… → Core tension: autonomy vs. oversight,… → Manager move: goals, visibility,… → …
  • The user says rockstar engineer
  • SKILL.md covers Before Starting, Response Style, How to Use This Skill and Default Response Shape, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Managing High Performers is an agent skill from manager-dot-dev/manager-skills. Guides engineering managers through the specific challenges of managing top engineers — produces a four-quadrant ability/confidence diagnostic, the Rock Star vs. Superstar distinction, common mistakes to avoid, a stagnation diagnostic (Diminishing XP), and a Pusher vs. Puller framework for managing burnout and team friction. Use when the user says "rockstar engineer," "superstar," "high performer," "brilliant jerk," "wants promotion," "hardest to manage," "overconfident," "my best developer is burning out,"…

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Business, Finance & HR, covering Performance reviews. The repository describes itself as: Skills for engineering managers. The licence is MIT.

When your agent uses it

  • The user says rockstar engineer
  • Wants promotion
  • Hardest to manage
  • My best developer is burning out

Example prompts

  • “rockstar engineer,”
  • “superstar,”
  • “high performer,”
  • “/managing-high-performers”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Type of high performer: rock star, superstar, pusher, puller, brilliant jerk, bored expert, or burnout risk.
  2. Core tension: autonomy vs. oversight, growth vs. stability, impact vs. team cost.
  3. Manager move: goals, visibility, feedback, constraints, scope, or recovery.
  4. Conversation script: direct wording that respects their competence.
  5. Team impact: how to protect the rest of the team while keeping the person engaged.

What it can do on your machine

Read from SKILL.md and the folder at commit c47ebc7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Managing High Performers loads about 2.7k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 182 tokens; SKILL.md has 1,526 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~182
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from manager-dot-dev/manager-skills at commit c47ebc7, republished under its MIT licence (© manager-dot-dev). 1,526 words, ~2,737 tokens.

Download SKILL.mdSave it as .claude/skills/managing-high-performers/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
managing-high-performers
description
Guides engineering managers through the specific challenges of managing top engineers — produces a four-quadrant ability/confidence diagnostic, the Rock Star vs. Superstar distinction, common mistakes to avoid, a stagnation diagnostic (Diminishing XP), and a Pusher vs. Puller framework for managing burnout and team friction. Use when the user says "rockstar engineer," "superstar," "high performer," "brilliant jerk," "wants promotion," "hardest to manage," "overconfident," "my best developer is burning out," "engineer is frustrated," or "my best developer is pushing me." Do NOT use for standard underperformance (use performance-reviews) or general motivation questions (use engineer-motivation).
metadata.version
2.1.2

Managing High Performers

Before Starting

Check for EM context first. If .agents/em-context.md exists, read it. If the person is named, check .agents/reports/[name].md.

If .agents/em-context.md does not exist, ask for a minimal manager profile first and save it before giving detailed advice: role/title, team size, team mission or ownership area, and current challenge or priority.

If a specific person is central to the conversation and .agents/reports/[name].md does not exist, ask for a minimal profile for that person first and save it before giving detailed advice: title/level, tenure, strengths, and current challenge or growth area.

If the conversation reveals durable new context later, update .agents/em-context.md or .agents/reports/[name].md automatically. Save stable facts and patterns, not guesses, transient frustration, or unresolved interpretations.

Response Style

Keep the first answer concise and useful. Do not dump the whole framework unless the user asks for depth.

Default to:

  • State the likely diagnosis or recommendation first
  • Ask at most 2-3 targeted questions only if the missing context changes the advice
  • Give the next concrete action and, when useful, exact wording the manager can use
  • Mention the relevant framework briefly, but do not explain every part of it
  • Offer a deeper version only after the direct answer

How to Use This Skill

  • Not sure what kind of challenge you're dealing with → The 4 Quadrants (start here)
  • High performer who wants to keep climbing vs. one who's settled → Rock Stars and Superstars
  • Promotion conversation or setting goals for a high performer → What to Do
  • High performer is damaging team dynamics or being a jerk → The Brilliant Jerk Problem
  • Senior engineer seems productive but quietly stagnating → The Diminishing XP Diagnostic
  • High performer is burning people out or burning themselves out → Pushers and Pullers

Default Response Shape

When helping with a high performer, avoid treating excellence as a generic good:

  1. Type of high performer: rock star, superstar, pusher, puller, brilliant jerk, bored expert, or burnout risk.
  2. Core tension: autonomy vs. oversight, growth vs. stability, impact vs. team cost.
  3. Manager move: goals, visibility, feedback, constraints, scope, or recovery.
  4. Conversation script: direct wording that respects their competence.
  5. Team impact: how to protect the rest of the team while keeping the person engaged.

If the issue is harmful behavior, do not excuse it because the person is talented.


The 4 Quadrants

Not every "difficult" engineer is a rockstar problem. Diagnose first:

Low ConfidenceHigh Confidence
High AbilityNeeds a mentor to grow — this is where you come inYour (positive) headache
Low AbilityOften the wrong role/fit — be honest with expectationsAlmost impossible to work with — give honest feedback; if no improvement, cut it

The true rockstar challenge is High Ability + High Confidence:

  • They expect you to always challenge them with bigger and bigger projects
  • They have tons of ideas they want implemented
  • The question of promotion always hangs in the air — if the org doesn't grow, they'll leave

Rock Stars and Superstars

From Radical Candor (Kim Scott): not every high performer wants the same thing. The mistake is assuming they do.

Superstars are on a steep growth trajectory — they want challenge, advancement, and new scope constantly. They're building toward something bigger. Managing them well means clearing the path, delegating high-visibility work, and being honest about what promotion requires.

Rock Stars are excellent performers in stable mode — the "rock" of the team. They're not stagnating; they're doing great work at a level they've chosen. They may have interests outside work, have reached a career equilibrium they're satisfied with, or simply not want the cost of constant upward movement. They are not under-performing. They are essential.

The management mistake: treating Rock Stars as Superstars who failed to advance. Asking them repeatedly "where do you see yourself in two years?" signals that their current contribution isn't enough. It creates pressure they didn't ask for and resentment they shouldn't have to manage.

What Rock Stars need: recognition for the stability and expertise they provide. Meaningful work. Not being pushed toward a path they haven't chosen.

What Superstars need: visible, difficult assignments. Regular feedback on what's between them and the next level. An honest answer to "what do I need to do to get there?"

A team that has both — and treats each well — is more resilient than one that only prizes the Superstar trajectory.


How NOT to Manage a Rockstar

Overpromise. The worst thing you can do. Painting a picture of a promotion that doesn't happen — even if your manager overrules you at the last moment — destroys trust permanently. If it's not 100% up to you, don't promise.

Ignore advice. You'll get good ideas constantly. If you say you'll do something, do it. If you decide not to — explain why. Don't just endlessly implement everything to please them, either — you'll lose credibility with the rest of the team.

Micromanage. They want freedom. Trust them to come to you when they need you.


What to Do

Set clear goals. Ambitious people love goals. If they're aiming for promotion: sit together and define exactly what they need to do to make it happen. Verify with your superiors that achieving those targets will almost guarantee it (and still — don't promise).

Delegate the hardest and most visible tasks. This is the best way to lay groundwork for their promotion. When everyone in the organization gets a chance to work with them — including your peers and your manager — they'll support the promotion when you suggest it.

Give unfiltered feedback. Giving tough feedback to someone who gives everything can feel like picking on them. Don't. Superstars are always looking for good feedback. Even if they disagree, they'll appreciate it.

Help them focus. High performers can be in many places at once, wanting to make things better everywhere. Listen to why they're focusing on what they are. Find alternative solutions. Align on what's truly important.


Show full SKILL.md (561 more words)Show less

Protecting Them from Burnout

A rockstar may get frustrated when working on a very ambiguous problem that requires cross-team alignment. The complexity and stakeholder involvement slows them down, and they may overwork to compensate.

Options:

  • Provide a secondary project for a sense of accomplishment
  • Pair them with an engineer who is comfortable with ambiguity
  • If frustration is high and they want to move on, find a different project

The Brilliant Jerk Problem

Rockstars can become brilliant jerks if not managed. They may grow impatient with "slower" team members, dismiss questions they consider trivial.

In most cases, they have good intentions and are simply oblivious. Bringing it up directly usually fixes it. If the problem is genuinely unfixable, you may have to let them go — a brilliant jerk who damages team trust and morale is not worth it.


The Diminishing XP Diagnostic

Engineers who stay in the same role for years can quietly stagnate even when they appear productive — doing familiar work returns negligible growth while the requirements for promotion keep increasing.

The RPG analogy is useful: the same task that was a stretch challenge at mid-level becomes rote at senior level. Rote work produces disengagement that precedes departure by months or years, often before either the engineer or manager notices.

How to use this: Periodically map each senior engineer's primary skills against what they have actually worked on in the last two quarters. If every assignment falls within their existing comfort zone, they are grinding low-XP monsters.

The fix isn't a job switch — most organizations have internal opportunities, but those require active EM intervention to surface and assign. Ask directly: "What skills do you want to level up in the next six months that you haven't had the chance to?" Then design at least one assignment per cycle that sits in their zone of proximal development — hard enough to generate real growth, not so far beyond current capability that it produces failure.


Pushers and Pullers

High performers fall into two distinct patterns — and each needs a different response:

Pushers always want more: more responsibility, more recognition, more impact. They drive themselves hard and can handle almost anything. The problem: they burn the people around them. They create friction by moving faster than the team can follow, and can make colleagues feel inadequate or pressured.

What to do: tell them directly that their success depends on the people around them succeeding too. Help them see that not everyone operates at their pace — and that bringing people along is a leadership skill, not a compromise.

Pullers don't ask — but they'll take everything you give them. They do great work, are reliable, and exercise good judgment. Then one day they explode: burned out, resentful, or quietly checked out.

What to do: set expectations proactively. Actively offload things from their plate before they ask. Check in on their energy, not just their output.

Identifying which type you're dealing with changes what kind of support to provide.


Dive Deeper

If the user asks where a framework came from, wants to read the original article, or wants more context — read references/sources.md.


  • retaining-developers — Rockstars are primarily in the "Bored" and "Stuck" states
  • engineer-motivation — Use the 3 Drivers to find what kind of high-visibility work actually motivates them
  • delegation — Delegating high-visibility work is both retention and development
  • performance-reviews — Setting clear promotion criteria is how you manage expectations

© manager-dot-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/managing-high-performers of manager-dot-dev/manager-skills.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit c47ebc7

Compare with similar skills

Managing High Performers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Managing High Performers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Managing High Performers this skillmanager-dot-dev/manager-skills114—~2.7kAutomated safety check: PassMIT
Wp Performance Reviewelvismdev/claude-wordpress-skills2351 repos~4.5kAutomated safety check: PassMIT
Align Humanagentscope-ai/OpenJudge868—~3.1kAutomated safety check: PassApache-2.0
Performance ReportAffitor/affiliate-skills6991 repos~2.5kAutomated safety check: PassMIT
Run Mv Hoi Reconstructionnvidia-isaac/video_to_data850—~1.5kAutomated safety check: PassCustom licence
Company Analysiszhu1090093659/dsh-trading231—~4.2kAutomated safety check: PassCustom licence

Similar skills

  • Wp Performance Review

    elvismdev/claude-wordpress-skills

    WordPress performance code review and optimization analysis.

    235 GitHub starsUsed in 1 repo~4.5k tokens
    Business, Finance & HRAuto-check passed
  • Align Human

    agentscope-ai/OpenJudge

    A skill your agent uses when the user has a judge/grader and human-labeled data, and wants to measure how well the judge agrees with humans, detect systematic biases, determine whether automatic…

    868 GitHub stars~3.1k tokensUpdated 26 days ago
    Business, Finance & HRAuto-check passed
  • Performance Report

    Affitor/affiliate-skills

    Generate affiliate performance reports with KPIs and recommendations.

    699 GitHub starsUsed in 1 repo~2.5k tokens
    Business, Finance & HRAuto-check passed
  • Run Mv Hoi Reconstruction

    nvidia-isaac/video_to_data

    Run and validate the repository-local multi-view camera calibration and human-object reconstruction pipelines.

    850 GitHub stars~1.5k tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Company Analysis

    zhu1090093659/dsh-trading

    A skill your agent uses when the user wants to analyze a listed company, stock, business, or investment target; challenge or revise an existing company report; compare A/H or primary-listing/ADR…

    231 GitHub stars~4.2k tokensUpdated 4 days ago
    Business, Finance & HRAuto-check passed
  • Windbg Diagnostic Method

    microsoft/win-dev-skills

    Official

    Use with every WinDbg plugin investigation to apply evidence-first reasoning, confidence calibration, contrarian review, structured reporting, and deterministic validation.

    462 GitHub stars~1.9k tokensUpdated today
    Business, Finance & HRAuto-check passed

More from manager-dot-dev/manager-skills

All 27 skills in this repo
  • Em Grid Scorer

    manager-dot-dev/manager-skills

    Score an Engineering Manager's coverage across all 12 cells of the EM Grid based on their calendar and Slack.

    114 GitHub stars~5.8k tokensUpdated 5 mo ago
    Auto-check passed
  • Em Context

    manager-dot-dev/manager-skills

    Foundation skill for engineering managers. An agent skill from manager-dot-dev/manager-skills.

    114 GitHub stars~1.6k tokensUpdated 5 mo ago
    Auto-check passed
  • 1on1s

    manager-dot-dev/manager-skills

    Prepares agendas, diagnoses struggling 1:1 relationships, and gives frameworks for running effective 1:1 meetings with direct reports.

    114 GitHub stars~3k tokensUpdated 5 mo ago
    Auto-check passed
  • Business Literacy

    manager-dot-dev/manager-skills

    Explains business financial terms and frameworks for engineering managers — produces term definitions (ARR, COGS, CAC, LTV, gross margin, burn rate, EBITDA, AARRR), translation formulas for making…

    114 GitHub stars~2.4k tokensUpdated 5 mo ago
    Auto-check passed
  • Career Development

    manager-dot-dev/manager-skills

    Helps engineering managers support direct report growth — produces a stage-by-stage model of engineering impact (Circles of Influence), a framework for non-linear career planning (Tarzan Method)…

    114 GitHub stars~2.3k tokensUpdated 5 mo ago
    Auto-check passed
  • Delegation

    manager-dot-dev/manager-skills

    Guides managers out of the bottleneck role — provides the Team Rep pattern, Epic Ownership model, Task-Relevant Maturity framework, kingdom ownership, and three-layer assignment strategy.

    114 GitHub stars~3.3k tokensUpdated 5 mo ago
    Auto-check passed

Questions about Managing High Performers

What does Managing High Performers do?

Guides engineering managers through the specific challenges of managing top engineers — produces a four-quadrant ability/confidence diagnostic, the Rock Star vs. Managing High Performers is an agent skill from manager-dot-dev/manager-skills. Guides engineering managers through the specific challenges of managing top engineers — produces a four-quadrant ability/confidence diagnostic, the Rock Star vs.

When should I use Managing High Performers?

Managing High Performers fits situations like: the user says rockstar engineer; wants promotion; hardest to manage; my best developer is burning out.

How do I install Managing High Performers in Claude Code?

Run `npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a claude-code`. Or copy the skill folder (skills/managing-high-performers in manager-dot-dev/manager-skills) into .claude/skills/managing-high-performers in your project. Claude Code loads it when a task matches its description.

How do I install Managing High Performers in Codex?

Run `npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a codex`. Or copy the skill folder (skills/managing-high-performers in manager-dot-dev/manager-skills) into .agents/skills/managing-high-performers in your project. Codex loads it when a task matches its description.

Can I use Managing High Performers in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-high-performers, .gemini/skills/managing-high-performers, .github/skills/managing-high-performers and .opencode/skills/managing-high-performers in your project.

What does Managing High Performers need to run?

SKILL.md names no scripts, command-line tools or credentials: Managing High Performers is instructions for the agent only.

Does Managing High Performers access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Managing High Performers safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Managing High Performers use?

Managing High Performers is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Managing High Performers use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 195 tokens, read only when the agent opens those files.

What are the alternatives to Managing High Performers?

Skills that share tags, products or a category with Managing High Performers: Wp Performance Review (elvismdev/claude-wordpress-skills, 235 stars), Align Human (agentscope-ai/OpenJudge, 868 stars), Performance Report (Affitor/affiliate-skills, 699 stars) and Run Mv Hoi Reconstruction (nvidia-isaac/video_to_data, 850 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Managing High Performers?

manager-dot-dev (a GitHub organization) maintains it in manager-dot-dev/manager-skills, which has 114 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on May 9, 2026.

Source: manager-dot-dev/manager-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.