Okr drafting

Skill shinzoxD/knackbox/skills/productivity/okr-drafting

Draft OKRs and goal cascades that are measurable and non-vanity. Use whenever the user asks for OKRs, quarterly objectives, key results, goal setting, or how to turn a strategy into measurable objectives and key results.From its SKILL.md

Install

npx -y skills add shinzoxD/knackbox --skill okr-drafting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 304 tokens by cl100k_base, as published. Nobody here has run it

OKR Drafting

Objectives are qualitative and motivating. Key results are measurable outcomes, not a task list. Fewer OKRs beat a wall of metrics.

Patterns

Objective: memorable outcome direction (not "be world class"). Key results: 2–4 metrics or binary milestones with starting point → target.

Bad KR: "Launch dashboard" (task). Better KR: "Raise weekly active teams using dashboard from 12% to 30%".

Output format

## OKRs — <team> — <quarter>

### O1: …
- KR1: from X to Y by date (source of metric)
- KR2: …
- KR3: …

### Notes
- scoring: …
- dependencies: …
- non-goals: …

Rules

KRs need baseline and target when numbers exist; else mark metric TBD.
Avoid vanity metrics disconnected from user/business value.
Cascade: company → team without cloning identical KRs everywhere.
Commit vs stretch: label if useful.
Do not invent company strategy; use provided context.
Cap at ~3 objectives per team per cycle unless asked otherwise.

Edge cases

Platform teams: KRs via customer team outcomes + reliability SLOs.
Early startup: shorter cycle; learning KRs ok if measurable.
Individual OKRs: align to team; avoid HR-only busywork.

What ships with it: 1 file

1.2 KB alongside SKILL.md

benchmarks/

prompts.json1.2 KB