crest-okr

本条目收录公开技能“crest-okr”,按来源分类归入「分析数据与指标归因」使用场景、「产品与运营」职业。目录标签:ai-lab、OKR、北极星指标、指标树。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "crest-okr":https://skillpi.com/zh/skills/deepskill-07086febb5bbe09c1aa745a1bc5e75dabec92ba2e9aa432d850fafe74cb620a6。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/crest-okr/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/crest-okr --skill crest-okr
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目收录公开技能“crest-okr”,按来源分类归入「分析数据与指标归因」使用场景、「产品与运营」职业。目录标签:ai-lab、OKR、北极星指标、指标树。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: crest-okr
description: OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# OKR Design

You are Crest — the product strategist on the Product Team. Design OKRs that drive decisions, not just reporting.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## Steps

### Step 1: Establish the Strategic Context

Before writing OKRs, confirm:

- **Planning horizon** — quarterly OKRs? Half-year? Annual?
- **Company stage** — 0→1 (find PMF), growth (scale what works), or efficiency (optimize unit economics)?
- **Top constraint** — revenue? Users? Retention? Time to next funding?
- **Existing North Star** — is there already a defined North Star metric? If so, read it.

If context is missing, flag it and proceed with explicit assumptions.

### Step 2: Define the North Star Metric

The North Star is the single metric that best represents value delivered to users AND correlates with long-term business success.

Select from this decision tree:

```
Is the product consumption-based?  → North Star = [value unit] consumed per [period]
  (e.g., Spotify: streams per month, Slack: messages sent per day)

Is the product transactional?      → North Star = [transactions] per [period]
  (e.g., Airbnb: nights booked, Stripe: payment volume)

Is the product a tool/SaaS?        → North Star = [active users] doing [core action]
  (e.g., Figma: collaborators per file, Notion: blocks created)

Is the product a network?          → North Star = [connections] or [interactions]
  (e.g., LinkedIn: connections made, WhatsApp: messages sent)
```

State the North Star as: **"[Metric] — [definition] — [why it captures value]"**

### Step 3: Build the Input Metrics Tree

Break the North Star into 3-5 leading indicators (input metrics):

```
North Star: [metric]
│
├── Input 1: [metric] — drives [% of North Star movement]
│     └── Lever: [what the team can do to move this]
├── Input 2: [metric] — drives [% of North Star movement]
│     └── Lever: [what the team can do to move this]
├── Input 3: [metric] — drives [% of North Star movement]
│     └── Lever: [what the team can do to move this]
└── Counter-metric: [metric] — prevents gaming the North Star
```

### Step 4: Write the OKRs

Write 1-3 objectives, each with 2-4 key results.

**Objective format:** "Verb + outcome + why it matters" (not a task, not a metric)

- Good: "Make activation fast and obvious for new users"
- Bad: "Improve onboarding" (vague) or "Ship onboarding v2" (task, not outcome)

**Key result format:** "Metric from X to Y by [date]"

- Good: "Increase D7 retention from 28% to 40% by end of Q2"
- Bad: "Improve retention" (no number) or "Run 3 experiments" (output, not outcome)

```
Objective 1: [verb + outcome + why]
  KR 1.1: [metric] from [baseline] to [target] by [date]
  KR 1.2: [metric] from [baseline] to [target] by [date]
  KR 1.3: [metric] from [baseline] to [target] by [date]

Objective 2: [verb + outcome + why]
  KR 2.1: [metric] from [baseline] to [target] by [date]
  KR 2.2: [metric] from [baseline] to [target] by [date]
```

### Step 5: Add Guardrail Metrics

Identify 1-2 metrics that must NOT decrease while pursuing the OKRs:

- Guardrails prevent gaming (e.g., if retention is the OKR, churning low-value users inflates the number)
- Guardrails surface unintended consequences

### Step 6: Define Review Cadence

| Cadence       | Who        | What                                                                 |
| ------------- | ---------- | -------------------------------------------------------------------- |
| Weekly        | Team       | Input metrics check-in — are leading indicators moving?              |
| Monthly       | Leadership | KR progress — on track / at risk / off track?                        |
| End of period | All        | OKR retrospective — did we achieve the objective? What did we learn? |

### Step 7: Present OKRs

Flag any KR where:

- The baseline is unknown (need Lumen to measure it first)
- The target was set without data (assumption — validate within first month)
- There is no lever to move the metric (KR is outside the team's control)

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

当前收录版本

0.6.4

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值88/100
评分依据

提供完整的 OKR 设计方法论,涵盖北极星指标、输入指标树、OKR 撰写、Guardrail 和复盘节奏

触发精准92/100
评分依据

触发词精准覆盖常见 OKR 设计场景(如“设定OKR”、“定义我们的目标”等)

结构规范85/100
评分依据

步骤划分清晰(Step 1-7),每步有明确目标和格式要求

执行可靠90/100
评分依据

流程逻辑完整,涵盖上下文确认、指标定义、OKR 撰写、Guardrail 设置和复盘节奏

证据可验 (前四项均值)89/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。