The-AI-Directory-Company/agents-and-skills / skills/okr-writing
okr-writing
VerifiedWrite OKRs (Objectives and Key Results) with measurable outcomes, scoring rubrics, and alignment checks across team and company levels.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.9 KB |
| assets/okr-template.md | markdown | 2.3 KB |
| assets/scoring-rubric.md | markdown | 3.7 KB |
| examples/engineering-team-q2.md | markdown | 6.2 KB |
assets/scoring-rubric.md
View on GitHub# OKR Scoring Rubric
Use this rubric to score each Key Result at the end of the OKR cycle. Score the Key Result, then average KR scores to get the Objective score.
---
## Scoring Scale
| Score | Label | Meaning | Example (KR: Increase activation rate from 30% to 50%) |
|-------|-------|---------|--------------------------------------------------------|
| **0.0** | No progress | No measurable movement from baseline. Work may not have started, or efforts produced no outcome. | Activation rate remained at 30%. |
| **0.1** | Minimal progress | Early-stage work began but did not translate into measurable results. | Activation rate moved to 31-32%. |
| **0.2** | Slight progress | Some movement, but well below a meaningful trajectory. | Activation rate reached 33-34%. |
| **0.3** | Partial progress | Meaningful effort applied, but results fell significantly short. | Activation rate reached 35-36%. |
| **0.4** | Below expectations | Roughly a third of the way to target. Progress is real but insufficient. | Activation rate reached 37%. |
| **0.5** | Halfway | Reached the midpoint between baseline and target. Solid effort, incomplete result. | Activation rate reached 40%. |
| **0.6** | Meaningful achievement | Substantial progress. Fell short of target but delivered clear value. | Activation rate reached 42%. |
| **0.7** | Delivered | Hit the target. This is the expected "success" score for a well-calibrated OKR. | Activation rate reached 44-45%. |
| **0.8** | Exceeded expectations | Surpassed the target. Either the execution was exceptional or conditions were favorable. | Activation rate reached 47%. |
| **0.9** | Significantly exceeded | Well beyond what was planned. Investigate whether the target was too conservative. | Activation rate reached 49%. |
| **1.0** | Fully achieved or exceeded | Hit or exceeded the most optimistic interpretation of the KR. May indicate the target was sandbagged. | Activation rate reached 50%+. |
---
## Interpreting Scores
### Healthy ranges
| Level | Healthy Average Score | Signal |
|-------|----------------------|--------|
| Individual KR | 0.4 - 0.8 | Normal distribution around the target |
| Objective average | 0.5 - 0.7 | Properly ambitious objectives |
| Team-wide average | 0.6 - 0.7 | Team is setting stretch goals and mostly delivering |
### Warning signs
| Pattern | What It Means | Action |
|---------|---------------|--------|
| Team average consistently > 0.9 | OKRs are not ambitious enough. The team is sandbagging targets to look good. | Set more aggressive targets next quarter. Normalize 0.7 as success. |
| Team average consistently < 0.4 | OKRs are unrealistic, or the team lacks the resources/focus to deliver. | Reduce scope. Investigate blockers. Ensure OKRs are within the team's control. |
| One KR at 1.0 while others are at 0.2 | Resources were concentrated on one KR at the expense of others. | Rebalance effort. Discuss whether the objective needs restructuring. |
| All KRs at exactly 0.7 | Possible gaming -- real-world outcomes rarely land uniformly. | Ask for supporting evidence. Look at the raw data, not just the score. |
---
## Scoring Process
1. **Score individually first.** Each KR owner scores their own KR with supporting data before the team review.
2. **Calibrate as a team.** Review scores together. Challenge scores that seem too high or too low. Align on what the evidence shows.
3. **Separate scoring from performance evaluation.** OKR scores measure ambition and progress, not individual performance. If scores affect compensation, people will sandbag targets. Keep these systems separate.
4. **Document the reasoning.** For each score, write one sentence explaining the evidence behind it. "Scored 0.6 because activation reached 42% (target was 50%), driven by onboarding redesign in weeks 6-10."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |