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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-structured, highly actionable advisory skill with clean progressive disclosure and a clear design/audit framework. Its main weakness is redundancy: the keystone framing and outcomes-vs-outputs point are repeated across several sections and the closing.

Suggestions

Tighten redundancy: the sandbagged/aspirational/stretch framing appears in the intro, its dedicated section, the failure modes, and the closing — consolidate so each point is made once and referenced.

Trim or remove the Closing section, which restates the intro and failure modes without adding new guidance.

Consider moving the 'OKRs vs roadmap items vs metrics' conceptual distinctions into a reference file since the body already scopes the skill against adjacent skills in 'What this skill is for'.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and opinionated, but the sandbagged/aspirational/stretch framing and the outcomes-vs-outputs point recur across the intro, dedicated section, failure modes, and closing, and the closing largely restates earlier material.	2 / 3
Actionability	Concrete, specific guidance throughout: numeric targets (32%→45%, 0.0–1.0 scale, 60–70% stretch, 2–4 objectives, 3–5 KRs), worked examples, and a four-quarter litmus test for diagnosing practice decay.	3 / 3
Workflow Clarity	The 12-consideration framework sequences the design/audit process, and the review cadence (weekly → mid-quarter → end-of-quarter → retro) is laid out as a clear ordered rhythm with time budgets.	3 / 3
Progressive Disclosure	SKILL.md is an overview with each section signaling 'Detail in references/…' one level deep, a consolidated Reference files list with descriptions, and all nine referenced files exist in ./references/.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 capabilities, explicit trigger guidance in third-person voice, and a distinctive niche. It is slightly long but the verbosity is information-dense rather than fluffy.

Dimension	Reasoning	Score
Specificity	Lists multiple 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.	3 / 3
Completeness	Explicitly answers what (OKR design disciplines and the sandbag/aspirational/stretch distinction) and when via a dedicated 'Triggers on...'/'Also triggers when...' clause.	3 / 3
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' gives broad coverage of natural terms users would say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear OKR-design niche with distinctive triggers; unlikely to fire for adjacent skills, and the body explicitly scopes it against roadmap-planning and related skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Commit: f1bc195

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.