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

setting-objectives-okrs设定目标 okrs

Agent Skill

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

总安装

235

周安装

10

GitHub Stars

公开资料未说明

下载量

82
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/razzza/skills-management-setting-okr-goals --skill setting-objectives-okrs

简介

setting-objectives-okrs 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 它支持按来源仓库、安装命令和原始 README 核验具体用法,适用于信息整理与定向搜索场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和维护状态后再部署。
  • 安装前建议检查是否会触发联网、命令执行或文件读写,避免误操作影响系统安全。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Setting Objectives & OKRs

Create clear, aligned priorities that translate strategy into execution. Reduce thrash, vague expectations, and "busy but not impactful" work.

Definitions

TermWhat it isCritical Question
Objective (O)A meaningful outcome (qualitative, directional)Where do we want to go?
Key Result (KR)Evidence of achievement (quantitative, time-bound, verifiable)How will we know we got there?
InitiativeProjects/tasks that influence KRs (not part of the OKR itself)What will we do to move the numbers?

Definition of Done

Outputs:

  • 1–3 Objectives per team (per quarter), each with 2–4 Key Results
  • Clear ownership for each KR
  • Baseline + target for each KR
  • Each team OKR maps to a higher-level priority
  • Initiatives listed separately (optional but recommended)
  • Individual goals derived from team KRs, with explicit lineage documented
  • Each individual includes: business goals + people goals (managers) + personal development goal
  • Manager goal reflection documented (alignment confirmed or redirected)

Success signals:

  • People can explain "why this matters" in one sentence
  • Progress can be tracked weekly without debate
  • Tradeoffs are easier (what we won't do becomes clearer)
  • Every individual goal traces to a team KR — no orphan goals

Failure signals:

  • KRs are tasks ("launch X", "build Y") rather than outcomes
  • KRs are unmeasurable ("improve quality" with no metric)
  • Too many KRs (looks like a backlog, not a strategy)
  • Everyone agrees until week 6, then discovers they meant different things
  • Individual goals exist that don't connect to any team KR

Inputs / Prerequisites

Required:

  • Planning horizon (quarter/half-year)
  • Company/team strategy or priorities for that horizon
  • Current baselines (where are we now?)
  • Known constraints: budget, headcount, dependencies, compliance

Nice-to-have:

  • Customer insights (NPS/CSAT, churn reasons, win/loss, support themes)
  • Historical metrics (last quarter's performance)
  • Stakeholder expectations (sales/ops/product/etc.)

Workflow

Phase 1: Drafting (Outcomes first)

Step 1 — Start with outcomes, not activity (30–60 min)

  • What must be different by end of period?
  • Who benefits (customer/internal/business)?
  • What tradeoff are we making (what won't we prioritize)?

Objective template: *"Improve for by."*

Step 2 — Choose 1–3 Objectives max (15–30 min)

  • If you have 5+, you don't have objectives — you have a wishlist.
  • "If we only achieved ONE, which matters most?"

Step 3 — Draft KRs per Objective (60–90 min)

  • 2–4 KRs each; measurable, time-bound, verifiable, owned.
  • Prefer a mix of Leading + Lagging indicators (see references/examples.md for KR formats).

Step 4 — Add baselines + targets + data sources (30–60 min)

  • Baseline: current value
  • Target: end-of-period value
  • Data source: dashboard/report
  • Owner: who updates/owns movement

Phase 2: Stress-Testing

Step 5 — Run Validation Tests (20–30 min)

TestQuestion
Strategic alignmentDoes each Objective map to a top priority?
CausalityWould these KRs indicate the Objective is achieved?
ControllabilityCan the team materially influence these metrics?
FocusIs scope realistic for the time period?
ClarityWould two strangers score progress the same way?
Counter-metricFor each KR, name at least one metric you must not degrade.

Counter-metric example: reduce cycle time (KR) → counter-metric = defect rate or customer complaints.

Step 6 — Identify initiatives (optional, 30–60 min)

  • List initiatives that influence KRs, kept separate from OKRs.
  • Each initiative maps to a KR and has an owner + rough effort.

Phase 3: Socializing

Step 7 — Review with stakeholders + dependency owners (30–60 min)

  • Confirm dependencies, commitments, timelines.
  • Resolve conflicts: what gets deprioritized?
  • Lock version for the cycle.

Step 8 — Set cadence & scoring (10 min)

  • Weekly: update KR values + confidence score
  • Mid-cycle: re-baseline if reality changed (document why)
  • End: score KRs + capture learnings

Phase 4: Cascading to Individual Goals

Team OKRs are set. Now each person derives their individual goals from the team's KRs.

Step 9 — Map individual goals to team KRs (30–60 min per person)

  • For each team KR, identify who contributes and how
  • Each individual goal must trace to a specific team KR (the lineage)
  • Use FROM-TO metrics to make the individual's contribution measurable
  • Include all three goal categories (see below): Business, People, Personal Development
  • Identify barriers to remove and support needed per goal

Step 10 — Validate the cascade (15–30 min)

  • Every team KR has at least one individual goal feeding it
  • No individual goal is orphaned (disconnected from a team KR)
  • The sum of individual contributions plausibly covers the team KR target
  • No critical gaps: if a KR has no one's goal pointing to it, it won't move

Phase 5: Manager Goal Reflection

After individuals submit their goals, the manager reviews and responds.

Step 11 — Manager reflects on submitted goals (15–30 min per person)

  • Confirm alignment with team/org priorities
  • Redirect or sharpen goals where there's misalignment
  • Add context the individual may be missing (cross-team dependencies, strategic shifts)
  • Reinforce what's strong; coach on what needs adjustment
  • Document the agreed version — this becomes the contract for the cycle

See references/examples.md for manager goal reflection examples.

Three Categories of Individual Goals

Individual goals should span Business Outcomes, People Outcomes, and Personal Development.

Business Outcomes (what moves the business):

  • User Growth & Adoption (e.g., active weekly users FROM 18% → TO 30%)
  • Revenue Contribution (e.g., ARR FROM $2.1M → TO $3.0M)
  • Quality (e.g., critical defects per KLOC FROM 0.45 → TO 0.20)
  • Customer Retention (e.g., logo retention FROM 91% → TO 94%)
  • Operational Efficiency (e.g., support cost per case FROM $19 → TO $14)

People Outcomes (how you lead and grow others — required for managers/leaders):

Use the Strategy / Execution / Leadership expectations to shape people outcomes.

ExpectationManagerSenior leader
StrategyTranslating direction into clear goalsLooking around corners and setting direction
ExecutionDelivering business results (team goals)Delivering business results (org goals)
LeadershipInspiring and developing others (within and across team)Inspiring and developing others (within and across org)

Examples of measurable people outcomes:

  • Strategy: team has clarity on direction with documented measurable goals; stakeholders aligned early; fewer priority conflicts
  • Execution: predictable delivery (hit rate on committed outcomes); reduced cycle time / incidents; improved cross-team predictability
  • Leadership: scaled through others; built successors; retained critical talent; addressed underperformance with clear feedback

Common people-outcome areas:

  • Performance Management: provided clear feedback and addressed underperformance
  • Hiring & Scaling: attracted and onboarded top talent
  • Engagement: improved engagement scores and created a positive team culture

Personal Development (how you grow yourself):

  • Skill to develop (e.g., negotiation, coaching, technical depth, public speaking)
  • Company Value to embody (which company value you'll focus on demonstrating)
  • How you'll develop it (workshops, mentorship, practice, feedback loops)
  • How you'll know it worked (observable behavior change, feedback from others, measurable outcome)

Barriers to Remove

For each goal, identify blockers that stand in the way and your plan to address them:

  • What is the barrier? (tech debt, skill gaps, resource constraints, market conditions)
  • What will you do about it? (specific actions with timeline)
  • What support do you need? (budget, headcount, tools, executive sponsorship)

Cross-functional Collaboration

Call out key partnerships that enable your goals:

  • Which teams/stakeholders are you partnering with?
  • What have you committed to together? (SLAs, shared rituals, joint reviews)

Good Individual Goals Are

CriteriaWhat it means
Derived from team KRsExplicit lineage to a team-level Key Result
Outcome-focusedMeasured by impact, not effort
SMARTSpecific, Measurable, Attainable, Relevant, Time-Bound
RevisitableCan be updated as priorities shift
Three-dimensionalCovers business + people + personal development

Quality Checks for Individual Goals

  • Each goal explicitly names which team KR it supports
  • Each goal has a FROM → TO metric (not just "improve X")
  • Impact statement explains why it matters to the business or people
  • At least one goal addresses people outcomes (for managers)
  • For managers/leaders: people outcomes cover Strategy, Execution, and Leadership (across the set of goals)
  • At least one personal development goal with a Company Value focus
  • Barriers and support needed are identified (not left vague)
  • Goals are attainable within the fiscal year

Templates

Team OKR Template

Objective:
  Statement:
  Why it matters:
  Owner:

Key Results:
  KR1: <metric> from <baseline> → <target>
    Data source:
    Owner:
    Confidence (0.1–1.0):
    Counter-metric(s):
  KR2: ...
  KR3: ...

Initiatives (not KRs):
  Initiative A → supports KR1 (owner: ___)
  Initiative B → supports KR2 (owner: ___)

Dependencies/Risks:
  Dependency:
  Risk:
  Mitigation:

Individual Goal Template (cascaded from Team OKR)

BUSINESS / PEOPLE GOALS (top 3, cascaded from team OKRs):

Goal 1:
  Team Objective: [which team objective this supports]
  Team KR: [which specific KR this goal feeds into]
  Goal: [What I will achieve — outcome, not activity]
  Success Measure: FROM [baseline] → TO [target] by [date]
  Impact: [business and/or people outcome]
  People expectation (if people outcome): [Strategy | Execution | Leadership]
  My role: [what specifically I will do to move this]

Goal 2: ...
Goal 3: ...

BARRIERS TO REMOVE:
  Barrier 1: [what's in the way]
    Action: [what I will do, by when]
    Support needed: [budget, headcount, tools, sponsorship]
  Barrier 2: ...

PERSONAL DEVELOPMENT:
  Skill to develop: [specific capability]
  Company Value: [which company value I will focus on demonstrating]
  How I will develop it: [workshops, mentorship, practice, etc.]
  How I will know it worked: [observable change, feedback, measurable outcome]

CROSS-FUNCTIONAL COLLABORATION:
  Partnership: [team/stakeholder]
  Commitment: [what we agreed to — SLAs, shared rituals, joint reviews]

What I won't do this cycle:

Strategic Alignment (How work rolls up)

Company Strategy / North Star
        ↓
Org Priorities (this cycle)
        ↓
Team Objectives (why)
        ↓
Team Key Results (how we measure)
        ↓
Individual Goals (my contribution to a team KR, with FROM→TO metrics)
        ↓
Initiatives / Tasks (what we do)

Sanity checks:

  • If an individual goal doesn't feed a team KR → it's orphaned work.
  • If a team KR has no individual goals pointing to it → nobody owns moving it.
  • If an initiative doesn't move an individual goal or team KR → probably a distraction.
  • If a team KR doesn't support an Objective → probably a random metric.
  • If an Objective doesn't map to a priority → probably local optimization.

Additional Resources

  • For KR formats (leading vs lagging indicators), quality rubric, discovery OKRs, common pitfalls, goal-setting examples, and success metrics, see references/examples.md.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

35.83%
按下载量换算29

Claude

33.06%
按下载量换算27

Cursor

18.71%
按下载量换算15

Gemini CLI

10.38%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills