Token导航 LogoToken导航

Agent Skill · 研究检索

product-leadership(产品领先地位)

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

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

总安装 240周安装 10GitHub Stars 31下载 80核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:product-leadership(产品领先地位)
来源仓库:https://github.com/ericgandrade/claude-superskills
仓库路径:skills/product-leadership
安装命令:
npx skills add https://github.com/ericgandrade/claude-superskills --skill product-leadership
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/ericgandrade/claude-superskills --skill product-leadership

这个 Skill 是做什么的

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

product-leadership 聚焦产品领导力的高阶实践,适用于管理多产品或多团队场景。它涵盖组合管理、高管协同、董事会沟通与规模化产品组织的运作节奏。通过策略框架和系统思维,帮助构建可持续的产品决策体系与执行机制。安装前请确认权限范围、维护状态及是否涉及联网或文件操作。

建议结合原始 README 核验具体用法与适用边界。

来源仓库内路径:skills/product-leadership

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

product-leadership 怎么安装?

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

product-leadership 支持哪些 AI 工具?

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

product-leadership 需要什么权限?

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

product-leadership 是免费的吗?

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

product-leadership 用的人多吗?

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

product-leadership 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
product-leadership

产品领先地位 · 本页

24031只读未明确通过

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

SKILL.md 原文

Product Leadership

"Your job is no longer to build products. It's to build the teams and systems that build products."

This skill covers Product Leadership — the overlay for operating at Director, VP, or CPO level. It addresses portfolio management, executive alignment, board communication, team structure, and the operating rhythms that scale product organizations.

Related skills: product-strategy, product-discovery, product-architecture, product-delivery, ai-native-product


When to Use This Skill

Use this skill when:

  • Managing multiple products or product teams
  • Aligning product strategy with company strategy
  • Communicating to board or executives
  • Designing product team structure
  • Establishing operating rhythms across teams
  • Coaching and developing product managers
  • Navigating organizational politics

Role scope: Director, VP Product, CPO, Head of Product


The Leadership Shift

IC PM vs. Product Leader

DimensionIC PMProduct Leader
OutputShip features, move metricsBuild teams that ship and move metrics
DiscoveryDo discoveryEnsure discovery happens across teams
DecisionsMake product decisionsCreate systems for good decisions
InfluenceTeam + stakeholdersOrganization + executives + board
SuccessYour product winsYour PMs and products win
Time horizonQuartersYears

The Three Jobs of Product Leadership

  1. Set Direction — Portfolio strategy, resource allocation, what to build/not build
  2. Build Capability — Hire, coach, develop PMs; establish systems and processes
  3. Remove Obstacles — Unblock teams, align executives, navigate politics

Progress Tracking

Display progress during leadership work:

[████░░░░░░░░░░░░░░░░] 25% — Phase 1/4: Portfolio Assessment & Team Structure
[████████░░░░░░░░░░░░] 50% — Phase 2/4: Executive Alignment & Communication
[████████████░░░░░░░░] 75% — Phase 3/4: Operating Rhythm Design
[████████████████████] 100% — Phase 4/4: Board/Stakeholder Readout

Framework Components

1. Portfolio Management

The Portfolio View

As a leader, you manage a portfolio of products/bets, not a single product.

┌─────────────────────────────────────────────────────────────────┐
│                     PRODUCT PORTFOLIO                           │
├─────────────────┬─────────────────┬─────────────────┬──────────┤
│   Product A     │   Product B     │   Product C     │ Product D│
│   [Cash Cow]    │   [Star]        │   [Question]    │ [Dog]    │
│   Maintain      │   Invest        │   Decide        │ Sunset?  │
└─────────────────┴─────────────────┴─────────────────┴──────────┘

Portfolio Categories (BCG-style)

CategoryCharacteristicsStrategy
StarsHigh growth, high shareInvest heavily
Cash CowsLow growth, high shareMaintain, harvest
Question MarksHigh growth, low shareInvest or divest
DogsLow growth, low shareSunset or pivot

Resource Allocation Questions

  • Where are we over/under-invested relative to opportunity?
  • Which products deserve more resources? Fewer?
  • What would we stop doing to fund something new?
  • Are we spreading too thin or concentrating appropriately?

Portfolio Review Cadence: Quarterly


2. Executive Alignment

The Alignment Challenge

Product leaders translate between:

  • Customer needs ↔ Business objectives
  • Team capabilities ↔ Executive expectations
  • Long-term bets ↔ Short-term pressures

Stakeholder Map

StakeholderCares AboutYour Job
CEOCompany strategy, major bets, competitive positionAlign product to company strategy, flag strategic choices
CFORevenue, costs, unit economicsConnect product to financial outcomes
CTOTechnical strategy, platform health, eng efficiencyPartner on build vs. buy, technical investments
SalesPipeline, quota, competitive winsEnable sales, balance custom vs. scalable
MarketingPositioning, launches, demand genCoordinate GTM, provide product narrative
BoardGrowth, market position, key metricsSimplify complexity, show progress

Managing Up Principles

  1. No surprises — Flag risks early, even if uncomfortable
  2. Options, not just problems — Bring recommendations
  3. Translate to their language — Business impact, not feature details
  4. Build trust through delivery — Track record enables autonomy
  5. Pick your battles — Not everything is worth escalating

Executive Review Format

SectionContentTime
ProgressKey wins, metrics moved5 min
RisksWhat could go wrong, mitigation5 min
Decisions neededChoices requiring exec input10 min
Forward lookNext quarter priorities5 min

3. Board Communication

What Boards Care About

TopicBoard QuestionYour Preparation
GrowthAre we growing? Why/why not?Key metrics, trend, drivers
Product-market fitDo customers love it?NPS, retention, expansion
Competitive positionAre we winning?Win rates, market share
Roadmap confidenceWill you deliver?Track record, risks
TeamDo we have the right people?Org health, key hires

Board Metrics (Keep Simple)

MetricWhy It MattersTarget
ARR/RevenueBusiness health[Target]
Growth rateTrajectory[Target]%
RetentionProduct stickiness[Target]%
NPSCustomer love[Target]
ActivationNew user success[Target]%

Board Slide Principles

  • One message per slide
  • Metrics with context (vs. target, vs. last period)
  • Honest about challenges
  • Clear asks if any
  • No jargon, no feature lists

Common Board Questions to Prepare For

  • "What's the biggest risk to hitting plan?"
  • "Why should customers choose us over [competitor]?"
  • "What would you do with more resources?"
  • "What's taking longer than expected and why?"
  • "What's the one thing keeping you up at night?"

4. Team Structure

Product Team Models

ModelStructureBest For
Feature teamsTeam owns feature areaClear boundaries, simple coordination
Mission teamsTeam owns outcome/metricOutcome focus, cross-functional
Platform + ProductPlatform serves product teamsScale, shared infrastructure
Pods/SquadsSmall autonomous unitsSpeed, ownership

Team Sizing Guidelines

Team SizeCharacteristics
4-6Tight, fast, 0→1 mode
6-10Standard product team
10+Consider splitting

The Product Trio at Scale

         Product Leader
              │
    ┌─────────┼─────────┐
    │         │         │
  PM A      PM B      PM C
    │         │         │
 [Trio]    [Trio]    [Trio]

Each PM leads a trio (PM + Designer + Tech Lead). Product Leader coaches PMs, not trios directly.

Hiring Principles

LevelLook For
Junior PMCuriosity, analytical ability, communication, coachability
Senior PMTrack record, strategic thinking, influence, autonomy
PM LeadTeam building, coaching, systems thinking, exec presence

PM Career Ladder Dimensions

  • Scope (feature → product → portfolio)
  • Complexity (clear → ambiguous)
  • Influence (team → org → company)
  • Autonomy (guided → independent → guiding others)

5. Operating Rhythm

The Operating Calendar

CadenceActivityPurpose
DailyStandups (teams)Execution alignment
WeeklyPM syncCross-team coordination
Weekly1:1s with PMsCoaching, unblocking
Bi-weeklyProduct reviewProgress, decisions
MonthlyMetrics reviewPerformance assessment
QuarterlyPlanningPrioritization, resourcing
QuarterlyPortfolio reviewStrategic alignment
AnnuallyStrategy refreshDirection setting

Weekly PM Sync (60 min)

SegmentTimePurpose
Wins & learnings15 minCelebrate, share knowledge
Cross-team dependencies20 minUnblock, coordinate
Escalations15 minDecisions needed from leader
Announcements10 minOrg updates, process changes

Quarterly Planning Process

WeekActivity
Week -4Strategy inputs gathered (market, customers, data)
Week -3Leadership alignment on priorities
Week -2Teams develop proposals
Week -1Review, negotiate, finalize
Week 0Communicate and kick off

1:1 Structure with PMs

TopicQuestions
ProgressWhat's going well? What's stuck?
SupportWhat do you need from me?
DevelopmentWhat are you learning? Where do you want to grow?
StrategyAny concerns about direction?
PersonalHow are you doing?

6. Culture & Principles

Building Product Culture

PrincipleWhat It Looks Like
Customer obsessionEvery PM talks to customers weekly
Outcome over outputTeams celebrate metrics, not launches
Evidence-basedDecisions cite data or research
Bias to actionShip → learn → iterate beats planning
Psychological safetyPMs can flag risks without fear
Intellectual honestyWe say what's not working

Anti-Patterns to Fix

Anti-PatternSymptomFix
Feature factoryTeams build what's requestedOutcome-based goals
PM as project managerPMs track tasks, not strategyElevate PM role, coach
Stakeholder-drivenLoudest voice winsEvidence-based prioritization
Hero cultureIndividual heroics save the daySystems and processes
Analysis paralysisEndless research, no shippingTimeboxes, thin slices

Defending Product Time

As leader, protect your teams from:

  • Stakeholder pet projects
  • Excessive meetings
  • Scope creep
  • Reactive firefighting
  • Process theater

7. Coaching PMs

Coaching vs. Directing

DirectingCoaching
"Do X""What options are you considering?"
"The answer is Y""What does the data suggest?"
"I would do Z""What's your recommendation?"

Coaching Questions

SituationQuestions
PM is stuck"What have you tried? What's blocking you?"
PM wants validation"What's your conviction level? What would change your mind?"
PM made a mistake"What did you learn? What would you do differently?"
PM is succeeding"What made this work? How can you replicate it?"

Development Conversations

PM LevelFocus Areas
JuniorDiscovery skills, stakeholder management, shipping
SeniorStrategic thinking, influence without authority, ambiguity
LeadTeam building, coaching others, exec communication

Feedback Framework

  1. Situation: What happened (specific)
  2. Behavior: What the PM did
  3. Impact: Effect on outcome
  4. Request/Suggestion: What to do differently

Templates

This skill includes templates in the templates/ directory:

  • portfolio-review.md — Quarterly portfolio assessment
  • board-metrics.md — Board-ready metrics summary
  • operating-rhythm.md — Annual operating calendar
  • pm-development.md — PM coaching and development plan

Using This Skill with Claude

Ask Claude to:

  1. Design portfolio strategy: "Help me assess my product portfolio and resource allocation"
  2. Prepare board deck: "What should I include in my board update for [situation]?"
  3. Structure team: "How should I structure my product team for [X PMs, Y products]?"
  4. Create operating rhythm: "Design an operating rhythm for a [size] product org"
  5. Plan quarterly: "Help me design a quarterly planning process"
  6. Coach PM: "How should I coach a PM who is struggling with [issue]?"
  7. Handle stakeholder: "How do I manage [stakeholder type] who wants [request]?"
  8. Prepare exec review: "Help me structure an executive product review"
  9. Build culture: "What practices build a strong product culture?"
  10. Navigate politics: "How do I handle [organizational challenge]?"

Connection to Other Skills

When you need to...Use skill
Define product strategyproduct-strategy
Ensure discovery practicesproduct-discovery
Review roadmaps and betsproduct-architecture
Assess delivery healthproduct-delivery
Guide AI product teamsai-native-product

Quick Reference: Leadership Checklist

Weekly:

  • 1:1s with all direct reports
  • PM sync completed
  • Cross-team blockers addressed
  • Exec touchpoints maintained

Monthly:

  • Metrics reviewed with team
  • Development conversations held
  • Stakeholder relationships maintained
  • Portfolio health assessed

Quarterly:

  • Planning completed
  • Portfolio review done
  • Board materials prepared
  • Team retro facilitated

Sources & Influences

  • Marty Cagan — EMPOWERED, INSPIRED
  • Melissa Perri — Escaping the Build Trap
  • Julie Zhuo — The Making of a Manager
  • Gibson Biddle — PM leadership frameworks
  • Lenny Rachitsky — PM research and interviews

平台分布

Codex

37.94%
按下载量换算30

Claude

27.55%
按下载量换算22

Cursor

17.97%
按下载量换算14

Gemini CLI

10.16%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills