coaching-plan

coaching-plan is a skill for Claude Code from zime-ai/zime-gtm-skills. It costs 81 tokens per session (1,010 once invoked), scanned A, original, MIT.

A coaching-plan writer that compares a sales representative's call transcripts or review results and turns repeated weaknesses into one or two practice goals. It includes a question to practise, a drill, and a way to check progress.

In plain words
What is it for?
Use it to prepare a one-to-one meeting, turn call reviews into focused practice, or help a representative prepare for the next call. It identifies a small behaviour to work on rather than producing a long list of criticism.
Why use it?
It helps a manager avoid giving broad feedback based on a single conversation. Repeated patterns are supported by quotes from more than one call, while one call is reported only as an observation.

Skill for Claude Code

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

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is claude "run coaching-plan on ./calls/rep-drew/".

Part of the gtm-skills plugin — 71 skills shipped together

Good fit Use it to prepare a one-to-one meeting, turn call reviews into focused practice, or help a representative prepare for the next call. It identifies a small behaviour to work on rather than producing a long list of criticism.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/zime-ai/zime-gtm-skills
agentmods
npx agentmods add skills/zime-ai/zime-gtm-skills/coaching-plan

Made for: Claude Code.

Or install gtm-skills, the plugin that ships this one along with the rest of its 71 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 coaching-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/coaching-plan/github.svg)](https://agentmods.dev/skills/zime-ai/zime-gtm-skills/coaching-plan)
Your own site
<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/coaching-plan"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/coaching-plan/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 coaching-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/coaching-plan"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/coaching-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,010 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.00081 $0.01010
Opus 5.5 $0.00032 $0.00404
Sonnet 5.5 $0.00016 $0.00202
Haiku 4.5 $0.00008 $0.00101

Measured 8d ago against content hash 9af20f0e5f00, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coaching-plan 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/coaching-plan/SKILL.md · 91 lines

How it starts

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

Coaching-Plan

You are a sales-intelligence writer. Your goal is to turn a rep's calls into one or two things to practice, each backed by quotes from more than one call.

Writes the plan from the rep's own calls. One call shows an observation. A pattern needs the same gap in at least two calls. The plan names a pattern only when the evidence supports it, and it keeps the list short.

When to use this

  • A manager is preparing a 1:1 and wants a plan grounded in real calls.
  • A manager has several call audits and wants one thing for the rep to work on.
  • A rep wants to know what to practice before the next call.

Before you start

  • If .agents/gtm-context.md (or .claude/gtm-context.md) exists, read it first and don't ask for anything it already answers.
  • Run this end to end in one pass. Don't stop to ask which file to use. Decide from what is there, note the assumption once, and move on.
  • If only one call is given, write the plan as observations and say that one call is not a pattern.
  • If the input is cut off or unclear, say so and write "not stated" for what is missing. Do not guess.

Input

Two or more call transcripts, or audit outputs from the other skills in this repo, for one rep. Mark which lines the rep spoke.

How to run it

claude "run coaching-plan on ./calls/rep-drew/"
  1. Read the whole input before you write anything.
  2. Write the sections below, in order, from references/rubric.md.
  3. Read the rubric's "What does not count" list before you write each section.
  4. Run the rubric's reads-well-too test before you finalize.

Output format

  1. Strengths to keep. Name one or two things the rep did well, with a quote from the rep and the buyer's reply that shows it worked.
  2. The pattern. Name the one or two gaps that appear in at least two calls.
  3. One-call observations. List gaps that appear once, with a quote.
  4. The question to practice. Write one question for each pattern that the rep can ask next time.
  5. A drill. Write one short drill for the pattern, such as replaying a moment and rewording it aloud.
  6. How to check progress. State what the manager looks for in the next call, as a line that can be quoted.

Read the full file on GitHub · 91 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 91 lines · 81 tokens per session scan A 9af20f0e5f00

Subscribe to this mod's changes

coaching-plan is a skill published in the GitHub repository zime-ai/zime-gtm-skills (17 stars, last pushed 6d ago), licensed MIT. It adds 81 tokens to every session and 1,010 once invoked, about $0.0003 per session on Opus 5.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-10-20.

Related

Other skills, from other repositories