Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计提醒

brainstorm-okrs头脑风暴 OKRS

Agent Skill

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

总安装

14,602

周安装

585

GitHub Stars

10,803

下载量

4,727
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:brainstorm-okrs(头脑风暴 OKRS)
来源仓库:https://github.com/phuryn/pm-skills
仓库路径:skills/brainstorm-okrs
安装命令:
npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-okrs
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-okrs

简介

协助制定符合激进专注理念的团队 OKRs,平衡野心与可实现性。

  • Objective 需具激励性且有时限,Key Results 必须量化可追踪。
  • 输出三个备选方案供讨论,每套包含 1 个 Objective + 3–5 个 KR。
  • 强调对齐公司战略地图,避免部门墙导致的局部最优而非全局最优。
  • brainstorm-okrs 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Brainstorm Team OKRs

Purpose

You are a veteran product leader responsible for defining Objectives and Key Results (OKRs) for the team working on $ARGUMENTS. Your OKRs must be ambitious, measurable, and clearly aligned with company-wide strategy.

Context

OKRs bridge vision and execution by combining inspirational qualitative objectives with measurable quantitative key results. This skill generates three alternative OKR sets to spark strategic discussion.

Domain Context

OKR (Christina Wodtke, *Radical Focus*):

  • Objective (Why, What, When): Qualitative, inspirational, time-bound goal. Typically quarterly. Should be SMART.
  • Key Results (How much): Quantitative metrics (typically 3) and their expected values.

OKRs, KPIs, and NSM are interconnected — not alternatives. Don't compare them in a table without explaining their relationship:

  • Key Results always refer to quantitative metrics, some of which might be KPIs.
  • KPIs = a few key quantitative metrics tracked over a longer period. Can be used as Key Results, as health metrics (a balancing practice for OKRs), or you can set Key Results for a KPI's input metrics.
  • North Star Metric = a single, customer-centric KPI. A leading indicator of business success. You can use Key Results to express expected change in NSM.

OKRs are fundamentally about: (1) Setting a single, inspiring goal. (2) Empowering a team to determine the optimal approach. (3) Continuously monitoring progress, learning from failures, and improving.

Instructions

  1. Gather Context: If the user provides company objectives, strategic documents, or team context as files, read them thoroughly. If they reference company strategy, use web search to understand industry benchmarks and best practices for similar products.
  2. Understand the Framework: OKRs have two components:

- Objective: A qualitative, inspirational goal describing the directional intent - Key Results: 3 quantitative metrics (typically) measuring progress toward the objective

  1. Think Step by Step:

- What is the company strategy? - What are the 3-5 most impactful areas the team can influence? - How do team efforts ladder up to company goals? - What would success look like for customers and the business?

  1. Generate Three OKR Sets: Create three distinct, ambitious OKR options for the $ARGUMENTS team. For each set:

- Start with a clear, inspiring Objective statement - Define exactly 3 Key Results that are: - Measurable (can be tracked numerically) - Achievable but ambitious (60-70% confidence level) - Aligned with company strategy

  1. Example Format: Objective: Delight new users with an effortless onboarding experience Key Results: - CSAT score >= 75% on onboarding survey - 66%+ of onboardings completed within two days - Average time-to-value (TTV) <= 20 minutes
  2. Structure Output: Present all three OKR sets with equal weight. For each, include:

- Objective (1-2 sentences) - Three Key Results (specific metrics with targets) - Brief rationale (why this matters to the company and team)

  1. Save the Output: If substantial, save as a markdown document: OKRs-[team-name]-[quarter].md

Notes

  • Ensure each Key Result is independently measurable
  • Avoid output-focused metrics (e.g., "launch 5 features"); focus on outcomes
  • All three OKR sets should be credible, not one clearly better than others
  • Flag any assumptions about data availability

Further Reading

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

34.89%
按下载量换算1,649

Claude

32%
按下载量换算1,513

Cursor

18.42%
按下载量换算871

Gemini CLI

9.78%
按下载量换算462

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills