Menu

Individual skill

okr-builder

0upvotes

Drafts a quarter's OKRs - an inspiring qualitative objective with 3-5 measurable key results, each with a baseline, target, and owner - plus the weekly confidence check-in and end-of-quarter grading cadence. Use when someone asks "help me write OKRs", "are these key results any good", "turn our goals into OKRs for next quarter", or "how do we score our OKRs". Do NOT use for building the full-year company plan that OKRs slot into - use annual-plan instead - or for personal goal-tracking with a check-in partner - use goals-accountability instead.

skills/okr-builder/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# OKR Builder

OKRs align effort around outcomes, and they fail in one predictable way: key results that are really a to-do list in disguise, so the team "completes" everything and moves nothing. The job of this skill is to produce few, measurable, honest OKRs - where a 0.7 at quarter end is a good result on a stretch goal, not a failure to explain away.

## Operating procedure

### Step 1: gather inputs

Collect before drafting; label anything the user estimates as a guess.

- The company or org priority this quarter rolls up to (one sentence). If the user cannot state it, that is the first problem - OKRs written in a vacuum get orphaned. If no annual plan exists, route to annual-plan first.
- The team's candidate goals, in whatever raw form exists.
- Current baselines for any metric that might become a key result. No baseline means no KR yet - default to spending the first two weeks of the quarter instrumenting it, and say so in the OKR.
- Who is available to own each key result.