run-one-on-one-meeting

run-one-on-one-meeting is a skill for Claude Code from jeffreytse/grimoire-core. It costs 34 tokens per session (1,107 once invoked), scanned A, original, MIT.

A guide for running a regular one-on-one meeting between a manager and a direct report.

In plain words
What is it for?
Use it to prepare recurring meetings, discuss the employee’s priorities, coach them, and follow up on issues.
Why use it?
It helps build trust, uncover problems early, remove blockers, and support the employee’s development.

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 prepare recurring meetings, discuss the employee’s priorities, coach them, and follow up on issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/run-one-on-one-meeting
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-one-on-one-meeting
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-one-on-one-meeting

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-one-on-one-meeting/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/run-one-on-one-meeting)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-one-on-one-meeting"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-one-on-one-meeting/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for run-one-on-one-meeting

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-one-on-one-meeting"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-one-on-one-meeting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,107 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.00034 $0.01107
Opus 5 $0.00017 $0.00553
Sonnet 5 $0.00007 $0.00221
Haiku 4.5 $0.00003 $0.00111

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

Security

Grade A, and why

run-one-on-one-meeting 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 8d 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-one-on-one-meeting/SKILL.md · 63 lines

How it starts

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

Run One-on-One Meeting

Facilitate a regular one-on-one meeting that builds trust, unblocks the employee, and creates a reliable coaching relationship.

Why This Is Best Practice

Adopted by: Google, Amazon, Microsoft, and organizations following Manager Tools methodology Impact: Google re:Work research identified one-on-ones as the #1 behavior of high-scoring managers on their "Project Oxygen" study. Manager Tools research across 90,000+ managers showed managers who consistently run one-on-ones see 3x higher retention and 40% better performance ratings on their teams. Drucker identified time with direct reports as the highest-leverage activity for any manager. Why best: Consistent, employee-agenda-first one-on-ones create psychological safety, surface problems before they escalate, and provide the coaching relationship that drives long-term development.

Sources: Horstman & Auzenne "Manager Tools One-on-One" podcast (2005–2023); Google re:Work "Project Oxygen" research (2008); Drucker "The Effective Executive" (1967)

Steps

  1. Set a fixed recurring time — schedule weekly or biweekly, same day and time, 30–60 minutes. Consistency signals the relationship is a priority. Canceling sends the opposite signal; reschedule rather than cancel.

  2. Make it the employee's meeting, not yours — the first 10–15 minutes belong to the employee. They set the agenda: what's on their mind, what they're working on, what's blocking them. Resist the urge to fill this time with your agenda.

  3. Prepare your talking points — prepare 2–3 topics for the second half: feedback, coaching on a current project, career development, or organizational updates. Keep the ratio roughly 50/50 employee-agenda to manager-agenda.

  4. Start with "What's on your mind?" — this open question invites the employee to surface whatever matters most to them, not just project status. It reveals concerns, ambiguities, and interpersonal dynamics that status reports never surface.

Read the full file on GitHub · 63 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. 8d ago First seen · 63 lines · 34 tokens per session scan A a47588028139

Subscribe to this mod's changes

run-one-on-one-meeting is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 23d ago), licensed MIT. It adds 34 tokens to every session and 1,107 once invoked, about $0.0002 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.