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 cnfeat/top-pm-skills --skill coaching-pmsgit clone --depth 1 https://github.com/cnfeat/top-pm-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/cnfeat/top-pm-skills/coaching-pms)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/coaching-pms"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/coaching-pms/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/cnfeat/top-pm-skills/coaching-pms"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/coaching-pms.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.00039 | $0.00647 |
| Opus 5 | $0.00019 | $0.00324 |
| Sonnet 5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
coaching-pms 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 11d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coaching Product Managers
Help the user develop and coach product managers using frameworks from 3 product leaders who have scaled PM organizations at top companies.
How to Help
When the user asks for help with coaching PMs:
- Define "good" in context - Establish what a successful PM looks like for their specific company and stage
- Assess current state - Help diagnose where the PM is today across key competencies
- Create a shared vision - Align on what growth looks like for both the PM and the organization
- Build a development plan - Design specific actions, feedback loops, and timelines
Core Principles
Define good before coaching
Petra Wille: "Step number one is really having a solid definition of what a good product person looks like in your context." Create explicit competency frameworks before attempting to develop anyone.
Use Bloom's Taxonomy for diagnosis
Bangaly Kaba: "Bloom Taxonomy describes what's the different levels or order of critical thinking... knowledge, comprehension, application, analysis, synthesis, and evaluation." Assess where PMs fall on the learning ladder to target development appropriately.
Coaching is the primary leadership job
Marty Cagan: "Sundar at Google has been saying that the number one thing they look for in their leaders is a good coach." Top companies (Google, Apple, Microsoft) prioritize coaching ability over domain expertise in their leaders.
Follow the 5-step framework
Petra Wille outlines a specific development process:
- Definition of Good - What does success look like here?
- Current Assessment - Where is the PM today?
- Shared Vision - Where do they want to be?
- Development Plan - What specific actions will get them there?
- Follow-up - How will you track and support progress?
Questions to Help Users
- "What does a 'great' PM look like at your company specifically?"
- "Which competencies are most critical for your current stage?"
- "Where is this PM on the knowledge-to-evaluation spectrum?"
- "What's the biggest gap between their current state and your needs?"
- "How much of your time as a leader goes to coaching versus doing?"
What ships with it
1 file 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.
- 11d ago First seen · 64 lines · 39 tokens per session scan A 74d12252d9ad
coaching-pms is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 647 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-08-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.