measure-okr-grader

Scores completed OKR sets at cycle close with type-specific conventions and evidence quality assessment.

640|81|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill measure-okr-grader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: measure-okr-grader
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/measure-okr-grader
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill measure-okr-grader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams closing an OKR cycle often misread results: averaging away failed guardrails, treating 0.7 as success on committed KRs, equating shipped effort with impact, or forcing numeric scores on KRs whose measurement windows have not closed. This Skill produces an honest, evidence-grounded OKR cycle review that protects the integrity of the OKR operating system.

Core Features & Use Cases

  • Type-aware KR scoring: Applies the correct scoring convention per OKR type (committed, aspirational, learning, operational_health, compliance_or_safety), with special states for not-yet-observable and not-yet-fully-observable KRs.
  • Evidence quality and initiative review: Rates evidence confidence per KR, separates ship-status from KR-impact, and reviews each initiative as a bet with continue, retire, or rework recommendations.
  • Learning synthesis and hand-offs: Captures validated and invalidated assumptions, then routes learnings to downstream skills like iterate-retrospective, define-hypothesis, and foundation-okr-writer.
  • Use Case: At quarter close, feed the original OKR set, final KR values, baselines, targets, and initiative status into the Skill to produce a complete cycle review with scorecard, objective interpretation, risks in interpretation, and next-cycle recommendations for the Q4 planning workshop.

Quick Start

Score our completed Q3 OKR set using these final KR values, baselines, and targets, and produce a full cycle review with learning synthesis and next-cycle recommendations.

Frequently Asked Questions about measure-okr-grader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I score OKRs at the end of a quarter?

Provide the original OKR set, cycle dates, final KR values, baselines, and targets. The grader scores each KR using the convention for its OKR type, rates evidence confidence, and produces a full cycle review with learning and next-cycle recommendations.

What is the difference between committed and aspirational OKR scoring?

Aspirational KRs use a 0 to 1 numeric scale where 0.6 to 0.7 is the designed sweet spot. Committed KRs are pass or fail against the target, and anything below 1.0 is a miss requiring postmortem, never softened with aspirational interpretation.

Can OKR scores be used for individual performance reviews?

No. The skill refuses to use OKR scores as individual performance ratings or compensation inputs, because doing so creates sandbagging incentives and suppresses honest learning. Scores evaluate the OKR set, not people.

What happens when a KR measurement window extends past cycle close?

The KR is marked not-yet-observable and its score is deferred rather than forced. The review records an interim signal, a projected score with explicit confidence, and the date the final score becomes available.

When should I not use an OKR grader?

Do not use it while still drafting OKRs, for generic team retrospectives, for single experiment results, or for stakeholder progress updates without scoring. It requires an authored, tracked OKR set at cycle close.

How are guardrail metrics handled in OKR scoring?

Guardrail KRs are scored per their OKR type but reported as a separate signal, never averaged into the primary objective score. A failed guardrail is surfaced independently so it cannot be diluted by a high primary KR score.