Wp Performance Review
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
Guides engineering managers through the specific challenges of managing top engineers — produces a four-quadrant ability/confidence diagnostic, the Rock Star vs.
$ npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install manager-dot-dev/manager-skills managing-high-performers --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "managing-high-performers" agent skill from https://github.com/manager-dot-dev/manager-skills/tree/main/skills/managing-high-performers into .claude/skills/managing-high-performers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-high-performers", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/manager-dot-dev/manager-skills/tree/main/skills/managing-high-performersType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install manager-dot-dev/manager-skills managing-high-performers --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manager-dot-dev/manager-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/managing-high-performers .agents/skills/managing-high-performers && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "managing-high-performers" agent skill from https://github.com/manager-dot-dev/manager-skills/tree/main/skills/managing-high-performers into .agents/skills/managing-high-performers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-high-performers", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install manager-dot-dev/manager-skills managing-high-performers --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manager-dot-dev/manager-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/managing-high-performers .cursor/skills/managing-high-performers && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "managing-high-performers" agent skill from https://github.com/manager-dot-dev/manager-skills/tree/main/skills/managing-high-performers into .cursor/skills/managing-high-performers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-high-performers", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/manager-dot-dev/manager-skills.git --path skills/managing-high-performers--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install manager-dot-dev/manager-skills managing-high-performers --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manager-dot-dev/manager-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/managing-high-performers .gemini/skills/managing-high-performers && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "managing-high-performers" agent skill from https://github.com/manager-dot-dev/manager-skills/tree/main/skills/managing-high-performers into .gemini/skills/managing-high-performers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-high-performers", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install manager-dot-dev/manager-skills managing-high-performersInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/manager-dot-dev/manager-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/managing-high-performers .github/skills/managing-high-performers && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "managing-high-performers" agent skill from https://github.com/manager-dot-dev/manager-skills/tree/main/skills/managing-high-performers into .github/skills/managing-high-performers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-high-performers", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add manager-dot-dev/manager-skills --skill managing-high-performers -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install manager-dot-dev/manager-skills managing-high-performers --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manager-dot-dev/manager-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/managing-high-performers .opencode/skills/managing-high-performers && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "managing-high-performers" agent skill from https://github.com/manager-dot-dev/manager-skills/tree/main/skills/managing-high-performers into .opencode/skills/managing-high-performers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-high-performers", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
managing-high-performersGuides 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. 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.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit c47ebc7. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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.
.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.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.
.agents/em-context.md or .agents/reports/[name].md automatically. Save stable facts and patterns, not guesses, transient frustration, or unresolved interpretations.Keep the first answer concise and useful. Do not dump the whole framework unless the user asks for depth.
Default to:
When helping with a high performer, avoid treating excellence as a generic good:
If the issue is harmful behavior, do not excuse it because the person is talented.
Not every "difficult" engineer is a rockstar problem. Diagnose first:
| Low Confidence | High Confidence | |
|---|---|---|
| High Ability | Needs a mentor to grow — this is where you come in | Your (positive) headache |
| Low Ability | Often the wrong role/fit — be honest with expectations | Almost impossible to work with — give honest feedback; if no improvement, cut it |
The true rockstar challenge is High Ability + High Confidence:
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.
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.
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.
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:
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.
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.
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.
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" statesengineer-motivation — Use the 3 Drivers to find what kind of high-visibility work actually motivates themdelegation — Delegating high-visibility work is both retention and developmentperformance-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
SKILL.md and 1 other file (references) in skills/managing-high-performers of manager-dot-dev/manager-skills.
Open the folder on GitHubat commit c47ebc7
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Managing High Performers this skillmanager-dot-dev/manager-skills | 114 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Wp Performance Reviewelvismdev/claude-wordpress-skills | 235 | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Align Humanagentscope-ai/OpenJudge | 868 | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Performance ReportAffitor/affiliate-skills | 699 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Run Mv Hoi Reconstructionnvidia-isaac/video_to_data | 850 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Company Analysiszhu1090093659/dsh-trading | 231 | — | ~4.2k | Automated safety check: Pass | Custom licence |
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
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…
Affitor/affiliate-skills
Generate affiliate performance reports with KPIs and recommendations.
nvidia-isaac/video_to_data
Run and validate the repository-local multi-view camera calibration and human-object reconstruction pipelines.
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…
microsoft/win-dev-skills
Use with every WinDbg plugin investigation to apply evidence-first reasoning, confidence calibration, contrarian review, structured reporting, and deterministic validation.
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.
manager-dot-dev/manager-skills
Foundation skill for engineering managers. An agent skill from manager-dot-dev/manager-skills.
manager-dot-dev/manager-skills
Prepares agendas, diagnoses struggling 1:1 relationships, and gives frameworks for running effective 1:1 meetings with direct reports.
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…
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)…
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.
Categories
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.
Managing High Performers fits situations like: the user says rockstar engineer; wants promotion; hardest to manage; my best developer is burning out.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Managing High Performers is instructions for the agent only.
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.
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.
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.
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.
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.
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.