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 matteotitta/genesys-skills --skill call-coachinggit clone --depth 1 https://github.com/matteotitta/genesys-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/matteotitta/genesys-skills/call-coaching)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/call-coaching"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/call-coaching/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/matteotitta/genesys-skills/call-coaching"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/call-coaching.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.00149 | $0.02094 |
| Opus 5.5 | $0.00060 | $0.00838 |
| Sonnet 5.5 | $0.00030 | $0.00419 |
| Haiku 4.5 | $0.00015 | $0.00209 |
Grade A, and why
call-coaching 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 1mo 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Call coaching
Score a sales rep's single call against the qualification framework that fits the call type, and return an evidence-bound coaching report: what they did well, where they fell short, the specific better moves to make next time, and the one thing to focus on. Every verdict is backed by a verbatim quote. Coach the rep; judge the call.
Built for sales-team enablement — e.g. ClientCo's SDR ramp and QA. It reads one call and helps one rep get better.
Claude Code triggers
Invoke when the user says:
- "Coach this call" / "score this rep's call"
- "Rep coaching report" / "how did this call go?"
- "Grade this discovery/demo/closing call"
- "Where did the rep miss on this call?"
Do NOT invoke when:
- User wants patterns across many won/lost deals → use
win-loss(retrospective aggregate, not per-rep coaching) - User wants to author a reusable sales playbook → use
sales-call-playbook - User wants general meeting summary/notes → use
transcripts - User wants competitive intel → use
competitor-research
How this differs from its siblings
| Skill | Job | Input → output |
|---|---|---|
| call-coaching (this) | Make one rep better on one call | One call → forward-looking per-rep coaching |
win-loss |
Find why deals are won/lost | Many calls → backward-looking aggregate patterns |
sales-call-playbook |
Author the client's playbook | No transcript → reusable reference |
Input requirements
| Input | Required? | Notes |
|---|---|---|
| One call transcript | Required | Any recorder format — see intake below |
| Call outcome / context | Optional | Helps calibrate (deal stage, amount, competitor) |
| Chosen framework | Optional | If omitted, inferred from the call type |
| product-messaging | Recommended | What we're selling — sharpens "better move" examples |
| sales-call-playbook | Recommended | The client's own playbook, if one exists |
If no transcript: ask for one. A coaching report needs a real call — never fabricate one to demonstrate the format.
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.
- 1mo ago First seen · 145 lines · 149 tokens per session scan A 9705f6a70347
call-coaching is a skill published in the GitHub repository matteotitta/genesys-skills (46 stars, last pushed 13d ago), licensed MIT. It adds 149 tokens to every session and 2,094 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
deepline-quickstart
Run a quick Deepline demo with a maintained Play.
first-call-rampup
Audits a new rep's early sales call transcript against a six-technique foundational rubric (opening, open-ended questioning, pain uncovered, trigger surfaced, pitch clarity, rapport) and credits only what the buyer's replies show, as a coaching read. Use when the user asks to coach a newly ramped rep, review a rep's…
coaching-plan
Writes a short coaching plan for one rep from two or more of their call transcripts or audit outputs, naming the pattern that repeats, the question to practice, a drill, and how to check progress. Use when a manager asks for a coaching plan, wants to turn call reviews into one thing a rep can work on, or needs a 1:1…
rep-ramp-status-digest
Reads a new rep's calls over several weeks and writes a ramp status by technique (opening, questioning, pain, trigger, pitch, rapport), marking each as improving, flat, regressing, or not enough evidence, with a quote from each call. Use when a manager asks how a new rep is ramping, wants a ramp status for a 1:1, or…
meta-learn
Captures a completed skill session in depth: three extraction questions (what surprised you, what was wrong, what was missing) become falsifiable pattern statements, logged to /context/skill-sessions.md for meta-synthesis. Trigger on: "capture what we learned", "log this session", "save the learnings", "what did we…
scout-mindset-bias-check
Detects and removes cognitive biases from reasoning using Julia Galef's Scout Mindset framework. Provides reversal tests, scope sensitivity checks, status quo bias tests, confidence interval audits, and full bias audits. Use when a prediction feels emotional, stuck at 50/50, or when validating forecasting process. Use…