run-underperformance-conversation

run-underperformance-conversation is a skill for Claude Code from jeffreytse/grimoire-core. It costs 54 tokens per session (2,428 once invoked), scanned A, original, MIT.

A manager's early, direct conversation with an employee whose work has fallen below expectations.

In plain words
What is it for?
Use it to describe the specific problem, understand possible causes, agree on corrective steps, and set clear expectations.
Why use it?
It addresses the gap while it is still recent, gives the employee a chance to explain what is happening, and creates a path to improve before formal action is needed.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 145 skills shipped together

Good fit Use it to describe the specific problem, understand possible causes, agree on corrective steps, and set clear expectations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/run-underperformance-conversation
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jeffreytse/grimoire-core --skill run-underperformance-conversation
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 145 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for run-underperformance-conversation

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-underperformance-conversation.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/run-underperformance-conversation)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-underperformance-conversation"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-underperformance-conversation.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,428 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.02428
Opus 5 $0.00027 $0.01214
Sonnet 5 $0.00011 $0.00486
Haiku 4.5 $0.00005 $0.00243

Measured 5d ago against content hash b9e44f07b634, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

run-underperformance-conversation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/business/leadership/skills/run-underperformance-conversation/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run Underperformance Conversation

Have an early, direct conversation the first time a performance gap appears — naming the specific gap, exploring causes without assuming, and agreeing on a clear path to correction — before the pattern hardens and requires formal process.

Why This Is Best Practice

Adopted by: Kim Scott's "Radical Candor" framework — used at Google, Dropbox, Apple, and most major tech companies as a management training standard — defines "challenging directly" as the non-negotiable second half of caring management; Linda Hill's research (100 new managers over one year, "Becoming a Manager") found that failure to address underperformance early was the single most common management failure among new managers, and that delay consistently made the situation worse; SHRM's early performance intervention framework is the HR industry standard for preventing PIPs through proactive management Impact: SHRM research found that managers who addressed underperformance within the first 30 days of observing it resolved the issue (returned the employee to expected performance) 70% of the time; managers who waited more than 90 days resolved it only 25% of the time; Gallup's 2022 research found that only 29% of employees "strongly agree" that their manager discusses their performance clearly — meaning 71% of employees are not getting early performance signal they need to course-correct; Kim Scott's framework identifies manager silence as "ruinous empathy" — the most common management failure, where concern for the employee's feelings causes the manager to withhold feedback that would actually help them Why best: Early underperformance conversations feel uncomfortable to managers — they require naming a gap to someone who may not see it, react defensively, or feel demoralized; managers avoid them through rationalization ("it's just a phase," "they're going through something personal," "it'll get better on its own"); this avoidance is the primary cause of formal PIP processes — by the time a PIP is needed, the gap has been growing for months while the manager said nothing; a single direct conversation at the first sign of decline is almost always easier for both parties than a formal documented process six months later

Read the full file on GitHub · 160 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 160 lines · 54 tokens per session scan A b9e44f07b634

Subscribe to this mod's changes

run-underperformance-conversation is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 20d ago), licensed MIT. It adds 54 tokens to every session and 2,428 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.