CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

okr-design

OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition with quarterly accountability). Triggers on OKR design, OKR setting, key result design, OKR scoring, mid-quarter recalibration, OKR cascading, outcomes vs outputs, quarterly planning, goal setting. Also triggers when a team's OKRs are always hit and producing no learning, when OKRs are demoralizing because they were set as fantasy, or when the team uses OKR vocabulary but the practice has decayed.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction skill: actionable worked examples, explicit scoring thresholds, a clear review cadence, and exemplary one-level-deep progressive disclosure into a real reference bundle. The main weakness is repetition — the sandbagged/aspirational/stretch thesis and the 60-70% target recur across five separate sections, and the intro/closing restate each other.

Suggestions

State the sandbagged/aspirational/stretch framing and the 60-70% target once in the keystone section, and have the scoring, failure-modes, framework, and closing sections reference it (e.g., "per the stretch-zone litmus test above") instead of re-deriving it — this is the largest source of repeated tokens.

Merge the closing section with the intro: both restate "OKR design as actually shipped, not as conference-talk theory" and "the teams that benefit from OKRs are the ones that hold the discipline"; keep one formulation and end the file after the framework and reference list.

Trim lines that restate standard OKR knowledge Claude already has (e.g., "Objectives are outcome statements. They name what the team is trying to achieve in the quarter.", "Key results measure progress toward the objective.") down to the opinionated, non-obvious guidance — the strong/weak examples and thresholds already carry the instruction.

DimensionReasoningScore

Conciseness

Mostly efficient — sections deliver concrete worked examples and thresholds — but noticeably padded in places: the intro and closing restate the thesis nearly verbatim ("The teams that benefit from OKRs are the ones that hold the discipline" appears in both), and the sandbagged/aspirational/stretch framing with the 60-70% target is re-derived in the intro, keystone section, scoring section, failure modes, and closing. Some lines restate standard OKR knowledge Claude already has ("Objectives are outcome statements. They name what the team is trying to achieve in the quarter."). Not 2 because most sections carry non-generic, opinionated content; not 4 because the repetition is recurring rather than isolated.

3 / 5

Actionability

Concrete, usable guidance throughout: worked key results with real numbers ("from 32% to 45%"), the 0.0-1.0 scoring scale, the 60-70% stretch target, the four-quarter litmus test, and a 12-consideration design/audit framework. Not 5 because some directives stay advisory without a procedure ("Investigate which", "Surface these explicitly"); not 3 because the common design and audit cases are covered with copy-ready examples.

4 / 5

Workflow Clarity

The review cadence is clearly sequenced (weekly check-in → mid-quarter review → end-of-quarter scoring → retrospective) with explicit decision points ("Decision point for any recalibration (rare; should not be the default outcome)"), and the litmus test provides a check-and-adjust loop. Not 5 because the 12-consideration design workflow is a flat checklist rather than an ordered procedure with validation checkpoints; not 3 because sequences and checkpoints are mostly explicit and no destructive/batch operations are involved.

4 / 5

Progressive Disclosure

Each major section ends with a "Detail in [references/...](...)" pointer, all 9 cited reference files exist in the bundle, references are exactly one level deep (no reference cites another), and a consolidated, annotated "Reference files" list aids navigation. The body functions as a genuine overview with detail appropriately split out. Not 4 because the split, signaling, and depth are all clean with no organization gaps observed.

5 / 5

Total

16

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capability list, comprehensive keyword and scenario triggers, and an explicit when-to-use clause. The only deductions are editorial framing ("not as conference-talk theory") and a couple of generic trigger terms ("quarterly planning, goal setting") that slightly broaden conflict risk.

DimensionReasoningScore

Specificity

Enumerates several concrete capabilities — "Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration" — plus the sandbagged/aspirational/stretch distinction. Not 5 because phrases like "measure the right thing" and "not as conference-talk theory" are editorial rather than concrete actions; not 3 because multiple specific capabilities are explicitly listed.

4 / 5

Completeness

Explicitly answers what ("Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration...") and when ("Triggers on... Also triggers when a team's OKRs are always hit...") with concrete trigger phrases. Matches the anchor-5 example structure exactly; not 4 because the when-clause is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

"Triggers on OKR design, OKR setting, key result design, OKR scoring, mid-quarter recalibration, OKR cascading, outcomes vs outputs, quarterly planning, goal setting" covers the natural terms and their synonyms, and scenario triggers ("when a team's OKRs are always hit and producing no learning") capture phrasings a user would actually say. Not 4 because both keyword synonyms and behavioral-scenario triggers are comprehensively covered.

5 / 5

Distinctiveness Conflict Risk

The OKR-specific vocabulary (OKR design, key result design, OKR cascading, mid-quarter recalibration) carves a clear niche, but generic trailing terms "quarterly planning, goal setting" carry minor overlap risk with roadmap-planning and general planning skills. Not 5 because of that overlap; not 3 because the dominant triggers are unambiguously OKR-specific.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/okr-design/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.