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 manager-coaching-cadencegit 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/manager-coaching-cadence)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/manager-coaching-cadence"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/manager-coaching-cadence/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/manager-coaching-cadence"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/manager-coaching-cadence.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.00073 | $0.01181 |
| Opus 5.5 | $0.00029 | $0.00472 |
| Sonnet 5.5 | $0.00015 | $0.00236 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
manager-coaching-cadence 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 24d 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.
Manager coaching cadence
Design a sustainable coaching rhythm that helps reps practise a specific behaviour and apply it in live work.
A coaching cycle connects observation, feedback, rehearsal, application, and follow-up. Its frequency depends on the opportunities reps have to use the skill and the time managers can protect. A single recorded-call review belongs in call-review-coach; a deal diagnosis belongs in deal-inspection-coach.
Coaching. "The AE ended a discovery call with 'I'll follow up'. In the 1:1, replay the close, ask what they wanted to achieve, and rehearse a mutual next step. On the next eligible call, listen for the buyer agreeing an action, owner, and date."
Status. "Managers will coach more consistently and hold reps accountable to a culture of excellence."
The manager should leave with a behaviour to coach and a realistic way to check its use.
Inputs
Ask only for the inputs that change the rhythm:
- Team type, role mix, and how many reps
- Behaviours worth coaching, the evidence for them, and opportunities to apply them
- Protected coaching time and existing meetings
- Evidence they can actually review: calls, deals, CRM, notes
- Who may see coaching notes, and where formal performance management begins
Use current supplied context first, or relevant sections of .enablement/context.md if available. If the target behaviour or evidence is unknown, propose a small observation sample and a review decision before presenting a full cadence as ready. For a change to an existing rhythm, revise only the affected sessions and follow-up.
Supporting material
Read references/manager-coaching-cadence-template.md when calculating coverage, designing sessions, or defining escalation. For a narrow edit, consult only the relevant section.
Procedure
- Choose the coaching focus. Use observed work to distinguish a skill gap from a process, incentive, capacity, or territory problem. Select a small set of team priorities and one focus per session. Each focus must describe what the rep will do differently and where it matters.
- Calculate capacity before coverage. Include evidence review, individual sessions, group practice, scheduling, and follow-up. Reserve time for outstanding application checks before adding new cycles. If demand exceeds protected time, prioritize by observed need, use group practice for a shared gap, and show who rotates. The complete time budget must reconcile; shortening preparation does not resolve excess demand.
- Choose a rhythm that fits the work. Match follow-up to the next realistic opportunity to apply the behaviour. A high-volume team may generate evidence daily; an enterprise rep may need longer. Label new days and deadlines proposed until confirmed.
- Design a session the manager can run. Review a relevant example together and ask what the rep intended. Identify one effective behaviour to retain and one change supported by the evidence. Rehearse the change, give specific feedback, and check whether the retry demonstrates it. Agree where the rep will apply it and what evidence both will review. Budget time for practice as well as discussion.
- Capture only role-relevant evidence. Use observation and commitment fields a manager will actually fill. Automated scores are leads, not findings. The rep can add context or correct the record.
- Check application and adjust support. Compare the agreed behaviour with the next eligible work sample. If it is absent, check opportunity, understanding, practice, and workflow barriers before concluding that coaching failed. Report trends only when evidence is comparable and sufficient.
- Define the boundary with formal performance management. Use the organisation's established process and authority. If none is supplied, identify the decision owner and evidence needed; do not create promotion or escalation counts. Keep developmental notes separate and exclude unrelated personal information.
- Set up the first cycle. Name the participants, evidence to review, practice task, follow-up opportunity, and time allocation. Leave unsupplied owners or commitments unresolved.
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.
- 24d ago Changed · -1 lines 7ed816a25743
- 2mo ago First seen · 77 lines · 73 tokens per session scan A 1e606eeb9c90
manager-coaching-cadence is a skill published in the GitHub repository nthnclrk/enablement-skills (16 stars, last pushed 25d ago), licensed MIT. It adds 73 tokens to every session and 1,181 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-08-30.
manager-coaching-cadence compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| manager-coaching-cadencenthnclrk/enablement-skills | Skill | 16 | 25d ago | MIT | A | 73 | Codex |
| orbit-notionnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 117 | Claude Code, Codex |
| agentmailpaperclipai/paperclip | Skill | 111k | yesterday | MIT | A | 30 | Claude Code, Codex |
| Cortexdanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 184 | Claude Code |
| rowboat-spacesrowboatlabs/rowboat | Skill | 18k | yesterday | Apache-2.0 | A | 60 | Claude Code, Codex |
| feishuHmbown/CodeWhale | Skill | 41k | 5d ago | MIT | A | 33 | Claude Code, Codex |
| pinchtab-mcppinchtab/pinchtab | Skill | 11k | 10d ago | MIT | A | 52 | Claude Code, Codex |