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.
npx skills add nthnclrk/enablement-skills --skill call-review-coachgit clone --depth 1 https://github.com/nthnclrk/enablement-skillsWrote 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.
[](https://agentmods.dev/skills/nthnclrk/enablement-skills/call-review-coach)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/call-review-coach"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/call-review-coach/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.
<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/call-review-coach"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/call-review-coach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00085 | $0.00928 |
| Opus 5 | $0.00043 | $0.00464 |
| Sonnet 5 | $0.00017 | $0.00186 |
| Haiku 4.5 | $0.00009 | $0.00093 |
Grade A, and why
call-review-coach 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 13d 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Call review coach
Turn one call into the next call's behavior. If the note could apply to any rep, rewrite it.
A review covers one conversation, a few moments, and one to three things to try next time. A sample of discovery calls is discovery-rubric-auditor. A practice drill is roleplay-scenario-builder.
Next-call behavior. "After the buyer names a pain, ask what it costs before you talk product. Success on the next call: they name a number or the person who owns that number."
Generic note. "Be more consultative and tighten discovery. Work on active listening and next-step control."
If a manager cannot hear the change on the next comparable call, it is not coaching.
Confirm Inputs First
Ask only for the inputs that change the review:
- The source you can actually access: recording, transcript, notes, or summary
- Call type, intended outcome, and who was in the room
- Rep role, tenure, and segment
- What the coach wants to change, if they already know
- Whether names must be anonymized
If the recording is not reachable, work from what you have and say so. Never imply you heard a moment you could not access.
Read The Right Reference
Read references/call-coaching-rubric.md for anchors, call-type applicability, and worked scoring excerpts. Skip it if the user already supplied a rubric and only wants the coaching plan.
Default Workflow
- Name the job of the call. What was this conversation supposed to produce? Done when the intended next step fits in one sentence.
- Set evidence coverage. Recording beats transcript beats notes. Flag missing sections and speaker uncertainty. Done when you can say what you observed versus inferred.
- Log the few moments that decided the call. Timestamp or transcript location, speaker, what happened, why it mattered. Quote the minimum. Done when three to six moments explain the outcome.
- Score only what this call type made observable.
Use the
1,3, and5anchors. Use2or4only between anchors. UseN/Owhen the behavior never appeared. Done when every score has evidence or an explicitN/O. - Pick the next-call behaviors. Keep 1-3. Drop anything a manager cannot hear next time. One call is directional, not a verdict on the rep.
- Write the practice. For each priority: the behavior, an in-call cue, and a success signal. Done when the rep knows what to try and the manager knows what to listen for.
- Set the follow-up. What to inspect on the next 1-2 comparable calls.
What ships with it
2 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.
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.
- 13d ago First seen · 76 lines · 85 tokens per session scan A ee4082b8731d
call-review-coach is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 23d ago), licensed MIT. It adds 85 tokens to every session and 928 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…