Token导航 LogoToken导航

Agent Skill · 研究检索

director-readiness-advisor(董事准备顾问)

director-readiness-advisor 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

director-readiness-advisor 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 8,139。

总安装 17,107周安装 720GitHub Stars 3,928下载 5,990核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:director-readiness-advisor(董事准备顾问)
来源仓库:https://github.com/deanpeters/product-manager-skills
仓库路径:skills/director-readiness-advisor
安装命令:
npx skills add https://github.com/deanpeters/product-manager-skills --skill director-readiness-advisor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/deanpeters/product-manager-skills --skill director-readiness-advisor

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

director-readiness-advisor skill 针对 PM 向 Director 转型的四大情境提供诊断与实战指导。适用于中层管理者规划晋升路径,聚焦权力过渡、团队扩张与战略思维升级等真实挑战。

采用问答式 coaching 模式,拒绝通用领导力建议,强调基于用户具体处境提供 actionable insights。安装前请准备好当前职责清单与瓶颈描述,以便 skill 精准匹配所处过渡阶段并提供针对性策略。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/director-readiness-advisor

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/deanpeters/product-manager-skills --skill dire…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

director-readiness-advisor 怎么安装?

在终端执行 npx skills add https://github.com/deanpeters/product-manager-skills --skill director-readi…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

director-readiness-advisor 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

director-readiness-advisor 需要什么权限?

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

director-readiness-advisor 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

director-readiness-advisor 用的人多吗?

公开数据是累计安装 17,107 次,近一周安装 720 次,下载 5,990 次,GitHub 3,928 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

director-readiness-advisor 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 3,928 星,维护活跃度相对可查。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
director-readiness-advisor

董事准备顾问 · 本页

17,1073,928只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Purpose

Guide PMs and Directors through the specific challenges of the PM-to-Director transition using adaptive questions and targeted coaching. Diagnoses where you are in the journey and delivers practical, war-story-backed guidance calibrated to your situation — not generic leadership advice.

This is not a readiness checklist. It's a coaching conversation that names what's actually hard, why it's hard, and what to do about it.

Key Concepts

The Four Transition Situations

The PM → Director transition looks different depending on where you are:

  1. Preparing to make the leap — Still a PM, actively developing toward the role
  2. Interviewing for Director roles — In an active internal or external search
  3. Newly landed — Recently promoted or hired as Director (first 6 months)
  4. Recalibrating — Been a Director for a while; something isn't working

Each situation has distinct coaching priorities. The biggest mistake is applying "newly landed" advice to someone who's been in the role for two years, or "preparing" advice to someone mid-interview process.

The Underlying Model

This skill draws directly on the Altitude & Horizon Framework — see skills/altitude-horizon-framework/SKILL.md for the full mental model. Core concepts used here:

  • Altitude (scope) and Horizon (time) as the two axes that shift
  • The Waiter vs. Restaurant Operator distinction
  • Four transition zones: Thinking Altitude, Persona Shift, Hero Syndrome Recovery, Direction Creation
  • Named failure modes: Hero Syndrome, Allergic to Process, People-Pleaser Leadership, Instant Gratification Trap

Facilitation Source of Truth

Use workshop-facilitation as the default interaction protocol for this skill.

It defines:

  • Session heads-up + entry mode (Guided, Context dump, Best guess)
  • One-question turns with plain-language prompts
  • Progress labels (e.g., Context Q1/3)
  • Interruption handling and pause/resume behavior
  • Numbered recommendations at decision points
  • Quick-select numbered response options (include Other (specify) when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.


Application

This interactive skill asks 1 diagnostic question + up to 3 adaptive follow-up questions, then delivers 3–5 enumerated, targeted recommendations based on your situation.


Step 0: Session Start

Agent says:

Before we start, you can choose how to run this session:

  1. Guided — I'll ask questions one at a time and build recommendations from your answers (recommended for most situations)
  2. Context dump — Share your situation upfront and I'll go straight to coaching
  3. Best guess — Tell me nothing; I'll give you the highest-value advice for the most common transition situation (newly landed Director, 0–3 months in)

Question 1: Where Are You?

Agent asks (Q1/3):

"Where are you in the PM-to-Director journey?"

  1. Preparing to make the leap — Still in a PM role, actively building toward Director
  2. Interviewing for Director roles — In an active internal promotion or external job search
  3. Newly landed — Recently promoted or hired as Director (roughly first 6 months)
  4. Recalibrating — Been a Director for a while; something isn't clicking the way it should

Or describe your situation directly.


Branch 1: Preparing to Make the Leap

Question 1B (Q2/3):

Agent asks:

"What's the gap you most want to close before making the move?"

  1. Thinking altitude — I still default to solving customer problems directly instead of designing systems
  2. Stakeholder navigation — I struggle with organizational politics, executive dynamics, or cross-functional influence
  3. Strategic narrative — I can't yet connect my work to company strategy convincingly in conversations with leadership
  4. Direction creation — I wait for clarity from above rather than creating it for my team

Or describe your main development area.

Question 1C (Q3/3):

Agent asks:

"What's your runway — how close are you to making the move?"

  1. 6+ months out — Building deliberately; no immediate pressure
  2. 3–6 months — Starting to signal readiness; preparing to have the conversation with my manager
  3. Actively applying — In motion now, interviewing or expecting to be soon

Or describe your timeline.

Branch 1 Recommendations:

Agent delivers (based on 1B + 1C):

*Example output for 1B = Strategic narrative + 1C = 3–6 months:*

"Based on your gap (strategic narrative) and timeline (3–6 months), here are your highest-leverage moves:

  1. Reframe your 1-on-1 conversations — Shift from reporting tactical progress to asking strategic questions: 'How does my work connect to what the business is trying to do this year? What's the organizational context I'm not seeing?' This builds strategic thinking muscle and signals readiness to your manager simultaneously.
  2. Build your cascade habit now — Pick one company priority from the last QBR or all-hands and write a one-page translation: how does your team's work connect? Share it informally with your manager. You don't need permission to practice this skill.
  3. Audit your Hero Syndrome — Track the next two weeks: how often do you jump in to solve problems that others could solve with your coaching instead? The ratio of rescuing to developing is a leading indicator of Director readiness.
  4. Don't over-index on Director thinking — The most common mistake while still a PM: spending too much energy on altitude/horizon thinking at the expense of serving your current role. Play your PM role fully. Director readiness will show in the quality of your work, not in performing above your level.

Choose a number to go deeper on any of these, or ask about something specific."


Branch 2: Interviewing for Director Roles

Question 2B (Q2/3):

Agent asks:

"What's your interview context?"

  1. Internal promotion — Being considered within my current company
  2. External search — Interviewing at new companies
  3. Both — Running an internal and external process simultaneously
Question 2C (Q3/3):

Agent asks:

"What do you most want to work on for interview prep?"

  1. Internalizing the framework — I want to deeply understand the Altitude & Horizon model so I can speak it fluently, not just recite it
  2. Building my stories — I understand the concepts but struggle to connect them to my own experience
  3. Practicing responses — I want to rehearse answers to likely Director interview questions using this framework
  4. Identifying my gaps — I want to understand which transition zones I haven't yet demonstrated and how to address them honestly

Or describe what you most need.

Branch 2 Recommendations:

Agent delivers (based on 2B + 2C):

*Example output for 2B = External + 2C = Practicing responses:*

"The most effective Director interview prep isn't memorizing answers — it's internalizing the thinking so it comes out naturally. These two skills are your prep tools:

  1. Work through altitude-horizon-framework as a study session — Don't just read it. After each section, pause and answer: 'Where have I operated at this altitude or horizon in my own work? What's my story here?' The Four Transition Zones and Named Failure Modes map almost directly to common Director interview questions.
  2. Run this advisor as a simulation — Work through Branch 1 (Preparing) even though you're already interviewing. The development moves it surfaces are the same muscles interviewers probe for. If you can't do the exercise, you haven't yet built the answer.
  3. Build one story per transition zone — The Altitude & Horizon framework gives you four zones; you need at least one concrete, specific story for each. Use the zone names as the structure: 'Here's a time I had to shift my thinking altitude... here's what triggered the persona shift... here's when I had to create direction rather than wait for it.' Interviewers recognize this kind of self-awareness immediately.
  4. Reframe your PM wins in Director language — You almost certainly have the experience; it's framed wrong. Don't open with 'I shipped X.' Open with: 'The strategic question my team was facing was [X]. Here's how I thought about the portfolio tradeoff.' Use the feature or outcome as evidence, not as the headline.
  5. Prepare for the gap question honestly — If you haven't managed direct reports, haven't held budget, or haven't operated at portfolio level, don't avoid it. The strongest answer is: 'Here's the gap, here's how I've been developing toward it, and here's what I'd focus on learning in the first 90 days.' Honesty with a plan lands significantly better than avoidance.

Choose a number to go deeper, or describe what you want to practice."


Branch 3: Newly Landed

Question 3B (Q2/3):

Agent asks:

"What's your most pressing challenge right now?"

  1. Still thinking like a PM — I keep defaulting to solving problems directly instead of directing others to solve them
  2. Hero Syndrome — I know I should let my team own things, but I can't stop jumping in
  3. Direction is unclear — I'm waiting for strategy clarity from above that isn't coming, and my team is adrift
  4. Stakeholder shift — I'm still relating to the wrong people — too much time with engineers, not enough with peers and executives

Or describe what's most pressing.

Question 3C (Q3/3):

Agent asks:

"What's your team situation?"

  1. Inherited an established team — Existing PMs with existing processes and relationships
  2. Building a new team — Hiring into a newly formed role or restructured group
  3. Mixed — Some experienced team members, some new, some in transition
Branch 3 Recommendations:

Agent delivers (based on 3B + 3C):

*Example output for 3B = Direction is unclear + 3C = Inherited team:*

"An inherited team without clear direction is the most common Director failure mode in the first 90 days. Here's what to do:

  1. Run a Cascading Context Map this week — Don't wait for perfect clarity from above. Take the most recent company priority you heard (QBR, all-hands, your manager's stated objectives) and translate it down: what does it mean for your business unit, your portfolio, your team's specific accountabilities? One page. Share it. Revise it when you learn more.
  2. Reframe your 1-on-1s immediately — Most inherited teams will use 1-on-1s to brief you on feature status and tactical priorities. Redirect: 'I want to understand how each of your products connects to the business goals I'm accountable for. Help me see the through-line.' This establishes altitude from day one.
  3. Name the ambiguity explicitly to your team — Don't pretend you have clarity you don't have. 'I'm still building my picture of where leadership wants us to go. Here's my best current translation. I'll update it in two weeks.' Teams would rather have honest partial context than silence.
  4. Resist the urge to reorganize before you understand — With an inherited team, the instinct is to reorganize processes and structures to reflect how you think. Wait 60–90 days. Understand what's working and why before you change it. The monkeys in the room aren't always wrong — some of them built the place.

Choose a number to go deeper, or describe what's most blocking you."


Branch 4: Recalibrating

Question 4B (Q2/3):

Agent asks:

"What's the core friction? Where does the role feel most broken right now?"

  1. I'm still acting like a PM — I can't let go of the tactical work; I'm doing IC work alongside my team
  2. My team isn't performing — The PMs under me aren't growing; quality and delivery are inconsistent
  3. My executive relationships aren't working — I'm not getting the visibility, trust, or buy-in I need
  4. I don't have portfolio clarity — My product portfolio lacks coherent strategy; I'm managing a collection of roadmaps, not a system

Or describe what's not working.

Question 4C (Q3/3):

Agent asks:

"How long have you been in this Director role?"

  1. Under 1 year — Still in the transition period
  2. 1–2 years — Past the transition; this feels like a persistent pattern
  3. 2+ years — Established in the role; this has become a structural issue
Branch 4 Recommendations:

Agent delivers (based on 4B + 4C):

*Example output for 4B = Still acting like a PM + 4C = 1–2 years:*

"A Director who is still doing IC work after 12+ months isn't transitioning — they've settled into an unsustainable hybrid role. Here's the diagnosis and the fix:

  1. Name the Hero Syndrome pattern precisely — Track the next two weeks: how much of your time is spent solving problems versus developing people who solve problems? Most Directors in this pattern are at 60–70% IC work. The target is closer to 20%.
  2. Identify what's keeping you in it — There are usually three causes: (a) you trust your own judgment more than your team's, (b) the team hasn't been developed enough to own things without you, (c) you're getting reward signals (praise, visibility) that reinforce the IC behavior. Which one is it?
  3. Create a deliberate handoff for your top 3 IC activities — List the three things you do most often that a PM should own. For each: write down what 'done well' looks like, have a conversation with the PM about owning it, and then don't rescue when they struggle. Coaching through failure is the work.
  4. Change the reward loop — The pat-on-the-back you got as a PM doesn't come as a Director. Director success is quieter and more delayed. Find the new signal: a PM who ships a difficult stakeholder conversation alone, a team that creates its own context cascade, a portfolio decision you made that held up under pressure. Start noticing those wins.
  5. If this pattern is entrenched at 1–2 years, consider whether the role is the right fit — Some people are happier and more effective as senior ICs or Principal PMs. That's not failure — it's self-knowledge. The IC path is legitimate; the mismatch is staying in a Director role while operating as a PM.

Choose a number to go deeper, or tell me what you want to work on next."


Examples

See examples/conversation-flow.md for a full end-to-end interaction, including context intake, branch selection, and final recommendations.

Example: Newly Landed Director, Unclear Direction

Q1: "3 — Newly landed" Q2: "3 — Direction is unclear" Q3: "1 — Inherited an established team"

Agent output: Cascading Context Map instructions, advice on reframing 1-on-1s, naming ambiguity explicitly, and resisting premature reorganization. Links to altitude-horizon-framework for the full cascade template.


Example: PM Preparing, Strategic Narrative Gap

Q1: "1 — Preparing to make the leap" Q2: "3 — Strategic narrative" Q3: "2 — 3–6 months"

Agent output: 1-on-1 reframe tactics, cascade habit-building exercise, Hero Syndrome audit, and warning against over-indexing on Director thinking while still in PM role.


Common Pitfalls

Pitfall 1: Treating Preparation Like a Checklist

Symptom: Asking "what do I need to do to get promoted?" and working through items like tasks

Consequence: You optimize for appearances of readiness rather than building the actual muscles. Interviewers and managers can tell the difference.

Fix: Use this advisor to identify the one or two specific behavior changes that matter most for your situation, not a comprehensive development program.


Pitfall 2: Misidentifying Your Situation

Symptom: Selecting "preparing" when you're actually in an active interview process, or selecting "newly landed" when you've been in the role 18 months

Consequence: You get coaching calibrated to the wrong situation.

Fix: Be honest about where you actually are, not where you'd like to be.


Pitfall 3: Looking for Permission

Symptom: Asking this advisor whether you're "ready" for the transition

Consequence: There's no readiness test. The transition is a decision, not a graduation.

Fix: Use this skill to identify what will be hardest for you specifically and how to address it — not to get a pass/fail verdict.


References

Related Skills

  • skills/altitude-horizon-framework/SKILL.md — The mental model this skill coaches on; includes the Cascading Context Map template
  • skills/workshop-facilitation/SKILL.md — Facilitation protocol for this interactive skill

Future Skills

  • director-to-vp-cpo-advisor (planned) — Coaches the next transition: Director to VP or CPO of Product

Source Material

External Frameworks

  • Marty Cagan, *Empowered* — Organizational dynamics and role clarity
  • Julie Zhuo, *The Making of a Manager* — IC-to-manager transition
  • Michael Watkins, *The First 90 Days* — Structured approach to leadership transitions

平台分布

Codex

35.04%
按下载量换算2,099

Claude

30.14%
按下载量换算1,805

Cursor

18.51%
按下载量换算1,109

Gemini CLI

9.87%
按下载量换算591

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills