okr-frameworks
Writes effective OKRs using Christina Wodtke's best practices and Google's OKR methodology. Use when setting goals, aligning teams, creating measurement frameworks, or tracking quarterly progress.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent completeness and trigger term coverage. The explicit 'Use when...' clause with multiple trigger scenarios is well-crafted. The main weakness is the lack of specific concrete actions beyond 'writes' - adding actions like 'draft objectives', 'define measurable key results', or 'score and grade OKRs' would strengthen specificity.
Suggestions
Expand the capabilities with more specific actions: 'Writes effective OKRs, scores progress, cascades goals across teams, and reviews quarterly results'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (OKRs) and references methodologies (Christina Wodtke, Google), but doesn't list specific concrete actions beyond 'writes'. Missing details like 'draft objectives', 'define key results', 'score OKRs', or 'cascade goals'. | 2 / 3 |
Completeness | Clearly answers both what ('Writes effective OKRs using Christina Wodtke's best practices and Google's OKR methodology') and when ('Use when setting goals, aligning teams, creating measurement frameworks, or tracking quarterly progress') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'OKRs', 'setting goals', 'aligning teams', 'measurement frameworks', 'quarterly progress'. These are terms users naturally use when needing OKR help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on OKRs with named methodologies. Unlikely to conflict with general goal-setting or project management skills due to the specific OKR focus and methodology references. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently delivers actionable OKR guidance through concrete templates and examples. The content respects Claude's intelligence by avoiding explanatory fluff and providing copy-paste ready formats. The main weakness is the lack of explicit feedback loops for OKR execution—what to do when targets are missed or need adjustment mid-cycle.
Suggestions
Add a brief troubleshooting section with guidance on mid-quarter OKR adjustments (e.g., 'If at week 6 you're below 30% progress: [specific steps]')
Include validation criteria for the weekly check-in format—what signals indicate an OKR needs revision vs. just more effort
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using structured formats (checklists, templates, formulas) without explaining what OKRs are or why goal-setting matters—it assumes Claude knows the basics and jumps straight to actionable patterns. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready templates with specific examples (time to first value < 5 minutes, activation rate > 70%), clear formulas, and filled-in examples that demonstrate exactly what good OKRs look like. | 3 / 3 |
Workflow Clarity | The execution checklist mentions weekly check-ins and end-of-quarter reviews, but lacks explicit validation steps or feedback loops for when OKRs aren't working—no guidance on what to do if progress stalls or how to course-correct mid-quarter. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines), the content is well-organized with clear sections (Core Frameworks, Action Templates, Quick Reference) and doesn't require external file references; the structure enables easy navigation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- menkesu/awesome-pm-skills
- Commit
53530ef
- 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.