Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

coaching-pms辅导经前管理系统

Agent Skill

coaching-pms 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

729

周安装

31

GitHub Stars

3

下载量

255
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:coaching-pms(辅导经前管理系统)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/coaching-pms
安装命令:
npx skills add https://github.com/oldwinter/skills --skill coaching-pms
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill coaching-pms

简介

coaching-pms 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。
  • 通过 npx skills add 命令从指定仓库安装并使用。
  • 使用前需确认权限范围、维护状态,避免触发联网或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Coaching Product Managers

Scope

Covers

  • Coaching a PM (direct report or mentee) to improve product craft, leadership, and decision quality
  • Converting “be better at X” into a measurable development plan with weekly reps + follow-ups
  • Defining what “good PM” means in your context and diagnosing skill depth using Bloom’s Taxonomy
  • Building a coaching cadence that scales (coaching as the primary job of product leadership)

When to use

  • “Coach my PM on strategic thinking / product sense / execution.”
  • “Create a PM development plan / growth plan for the next 8–12 weeks.”
  • “Assess a PM’s current level and decide what to coach next.”
  • “Define what ‘good PM’ means here and align on expectations.”

When NOT to use

  • You need a formal performance-management process (PIP, HR documentation, investigation) — use your company/HR process.
  • You only need 1:1 meeting design (use running-effective-1-1s).
  • The situation is primarily a conflict/difficult feedback moment (use having-difficult-conversations).
  • You need org-wide leveling/comp framework design (this pack can seed inputs, but it’s not the full program).

Inputs

Minimum required

  • Your context: role (PM manager/product leader), team/product, stage, constraints
  • The PM: level/title, scope, tenure, strengths, current challenges
  • Coaching goal: what must be more true in 4–12 weeks (outcomes + behaviors)
  • Evidence: 2–5 examples of work (PRDs, launches, decisions, stakeholder feedback) — anonymized
  • Any existing ladder/role expectations/values (if available)

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md (3–5 at a time).
  • If role expectations or evidence are missing, proceed with explicit assumptions and label unknowns.
  • Do not request sensitive personal data; use behavior/evidence summaries.

Outputs (deliverables)

Produce a PM Coaching Pack (Markdown in-chat; or files if requested) in this order:

  1. Definition of “Good PM” (in this context)

- Competency model + observable behaviors + Bloom depth ladder

  1. Current Assessment (evidence-based)

- Strengths, gaps, current level per competency, evidence notes, constraints vs skill gaps

  1. Shared Vision (1–3 growth bets)

- Target level, success signals, why it matters, timeframe

  1. Development Plan (practice loops + stretch work)

- Weekly reps, stretch assignment(s), required artifacts, coaching support, timeline, measurement

  1. Coaching Cadence + Session Toolkit

- 1:1 structure, coaching prompts, feedback moments, artifact review points

  1. Follow-up Tracker + Review Plan

- Checkpoints, how to evaluate progress, how to adjust the plan

  1. Risks / Open questions / Next steps (always included)

Templates: references/TEMPLATES.md Expanded guidance: references/WORKFLOW.md

Workflow (8 steps)

1) Intake + boundaries + coaching goal

  • Inputs: user context; references/INTAKE.md.
  • Actions: Confirm this is a coaching engagement (not HR/PIP). Define timeframe and outcomes. Choose whether to output the full pack or a subset.
  • Outputs: Context snapshot + assumptions/unknowns.
  • Checks: Goal is stated as observable outcomes/behaviors (not personality traits).

2) Define “good PM” for this role (Petra step 1)

  • Inputs: PM role scope; company context; any existing ladder/values.
  • Actions: Draft a context-specific competency model. For each competency, define behaviors and a Bloom ladder for skill depth (know → understand → apply → analyze → synthesize → evaluate).
  • Outputs: Definition of “Good PM” (competencies + behaviors + Bloom levels).
  • Checks: Expectations are observable; avoids vague labels like “be more strategic” without behaviors.

3) Assess current capability using evidence (Petra step 2)

  • Inputs: work examples; feedback; self-assessment (optional).
  • Actions: Map evidence to competencies. Assign a current Bloom level per competency. Separate skill gaps from constraints (scope, unclear mandate, lack of data/authority).
  • Outputs: Current Assessment table.
  • Checks: Each claimed gap has at least 1 concrete evidence bullet; uncertainties are labeled.

4) Choose 1–3 growth bets + shared vision (Petra step 3)

  • Inputs: assessment; business priorities; PM aspirations (if known).
  • Actions: Pick the highest-leverage competencies. Define target Bloom level + success signals. Align on what “good” looks like for this coaching cycle.
  • Outputs: Shared Vision (growth bets + targets).
  • Checks: Bets are achievable in timeframe; limit to 1–3 to avoid thrash.

5) Build a development plan with “reps” (Petra step 4 + Bloom)

  • Inputs: growth bets; upcoming work; available support (mentors, tools, stakeholders).
  • Actions: Turn each bet into practice loops: weekly reps + a stretch assignment + required artifacts. Choose reps that deliberately move up Bloom levels.
  • Outputs: Development Plan.
  • Checks: Every bet has (a) reps, (b) artifacts, (c) a measurement signal, (d) a coach commitment.

6) Design coaching cadence + session toolkit

  • Inputs: time budget; existing 1:1 cadence; tool constraints.
  • Actions: Propose cadence and meeting design (pre-work, agenda, artifact review points). Add coaching prompts that develop independent reasoning. Define “when to be directive” exceptions (risk/time-critical).
  • Outputs: Coaching Cadence + Session Toolkit.
  • Checks: Cadence is sustainable; coaching promotes autonomy (not dependency).

7) Follow-up loop + measurement (Petra step 5)

  • Inputs: development plan + cadence.
  • Actions: Create a tracker and review checkpoints. Decide how progress will be evaluated (rubric + evidence). Define how/when to adjust bets if constraints change.
  • Outputs: Follow-up Tracker + Review Plan.
  • Checks: Progress is measured via artifacts and behaviors, not vibes.

8) Quality gate + finalize pack

  • Inputs: full draft pack.
  • Actions: Run references/CHECKLISTS.md and score with references/RUBRIC.md. Add Risks / Open questions / Next steps.
  • Outputs: Final PM Coaching Pack.
  • Checks: The next coaching session can be run using the toolkit without additional invention.

Quality gate (required)

Examples

Example 1 (strategic thinking): “My PM is strong at execution but weak at strategy. Build an 8-week coaching plan, including an assessment and weekly reps.” Expected: growth bet around problem framing/insight synthesis; Bloom ladder; stretch work (opportunity assessment); cadence + artifact reviews.

Example 2 (stakeholder leadership): “Coach a senior PM to lead cross-functional alignment and improve exec comms.” Expected: bet on stakeholder mapping + decision briefs; practice reps (pre-reads, narratives); coaching prompts; review checkpoints.

Boundary example: “I need to start a PIP and document underperformance.” Response: recommend HR/performance process; optionally provide a coaching-focused development plan template only, clearly labeled as non-HR.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.26%
按下载量换算90

Claude

27.5%
按下载量换算70

Cursor

18.47%
按下载量换算47

Gemini CLI

9.11%
按下载量换算23

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills