okr-generator — Claude Code skill: what it does, how to install
okr-generator builds a structured okr-plan.md file using the Google and Intel framework from your company targets and team baselines.
MIT 250 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill okr-generator -a claude-codeWhat okr-generator does
The skill collects four core inputs before drafting anything: organizational goals, team function, target quarter, and current numerical baselines. Fabricating numbers is explicitly disallowed. When context is missing, the agent stops and prompts for real data instead of guessing.
The resulting okr-plan.md spans at least 400 substantive lines. It sets 3–5 qualitative objectives without numbers and attaches 3–4 measurable key results to each. Targets follow a strict balance: roughly 60–70% committed goals alongside 30–40% aspirational targets. Every key result receives its own single owner role, clear dependencies, and a distinct five-tier grading rubric scored at 0.0, 0.3, 0.5, 0.7, and 1.0.
Any objective failing to ladder directly into an organizational goal gets dropped from the cascade diagram. Initiatives remain strictly separated from key results so implementation steps never get confused with business outcomes.
What it helps with
- generate a quarterly OKR document following Google and Intel standards
- separate execution activities from measurable metric outcomes
- build five-level scoring rubrics for every team key result
- map department objectives directly to broader company goals
Example prompts for the agent
- Generate an OKR plan for our engineering team for Q2 based on our current performance numbers
- Create okr-plan.md for the customer success team aligned with our annual retention target
- Adjust our active quarter OKR document and preserve the previous targets with adjustment rationale
How to install okr-generator
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill okr-generator -a claude-code2Manually: put the files in place
~/.claude/skills/okr-generator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/okr-generator/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill okr-generator -a codex2Manually: put the files in place
.agents/skills/okr-generator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill okr-generator -a cursor2Manually: put the files in place
.cursor/skills/okr-generator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills okr-generator2Manually: put the files in place
.github/skills/okr-generator/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill okr-generator -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path okr-generatorManually: put the files in place
.devin/skills/okr-generator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill okr-generator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about okr-generator
How to install okr-generator in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill okr-generator -a claude-code in your terminal.
What does okr-generator produce?
It outputs an okr-plan.md file containing aligned objectives, measurable key results, grading criteria, tracking cadences, and review templates.
What inputs are mandatory before running the skill?
You must supply company goals, team function, the target quarter, and verified baseline metrics.
Source text
SKILL.md · MIT
---
name: okr-generator
description: Generates structured OKR plans (Objectives and Key Results) for teams and companies following Google/Intel methodology. Takes company goals, team function, quarter, and current metrics to produce a comprehensive okr-plan.md with objectives, key results, scoring criteria, alignment mapping, tracking cadence, and retrospective templates.
tools: Read, Write, Glob, Grep
model: inherit
---
# OKR Generator
Generate a comprehensive, actionable `okr-plan.md` from user inputs, applying the Google/Intel OKR framework.
## Contents
- `references/methodology.md` -- Core OKR principles (non-negotiable rules to apply).
- `references/inputs.md` -- The four required inputs plus optional context.
- `references/output-template.md` -- Exact structure of the generated `okr-plan.md`.
- `references/best-practices.md` -- Appendix content (common mistakes, OKR cycle, grading by KR type, reading list).
## Workflow
1. Read `references/inputs.md`. Collect the four required inputs: company goals, team function, quarter/period, current metrics/baseline. If any are missing, ask for them. Never fabricate baselines.
2. Read `references/methodology.md` and apply every core principle. Objectives are qualitative and inspirational (no numbers); key results are quantitative and measurable (always a number).
3. Design 3-5 objectives. Attach 3-4 key results to each. Mark each as Committed or Aspirational, targeting roughly 60-70% committed and 30-40% aspirational across the plan.
4. Map every objective to at least one company goal. Build both the alignment table and the cascade diagram. Drop any objective that does not ladder up.
5. Write a 5-level scoring rubric (0.0, 0.3, 0.5, 0.7, 1.0) for every key result, with KR-specific descriptions.
6. List initiatives separately from key results. Initiatives are the activities ("how"); key results are the measured outcomes ("what"). Never conflate them.
7. Document dependencies and risks. Assign a single owner role to every objective and key result.
8. Define the tracking cadence (weekly check-in, monthly scoring, quarterly retrospective) and include all three templates plus the appendix from `references/best-practices.md`.
9. Generate the full document per `references/output-template.md` as `okr-plan.md` in the working directory (or a user-specified path). Produce at least 400 substantive lines, no filler.
10. Summarize the plan: objective count and committed/aspirational split, the most ambitious key result, key dependencies/risks, and the recommended first action.
## Generation Rules
- Validate inputs before generating; base all targets on the provided baselines (committed: ~10-30% improvement; aspirational: ~50-100%+ or breakthrough).
- Objectives qualitative, key results quantitative. Rewrite any KR lacking a number.
- Every objective maps to a company goal; every KR has a single owner and a scoring rubric.
- Never connect OKR scores to compensation, promotion, or performance reviews. Include the decoupling reminder in the scoring guide.
- Include all templates in full (weekly, monthly, quarterly). Do not abbreviate.
## Edge Cases
- **Multiple teams**: Generate one plan per team in its own file (e.g., `okr-plan-engineering.md`, `okr-plan-marketing.md`).
- **Company-level OKRs**: Remove team-to-company alignment; show department-level cascade instead.
- **Mid-quarter adjustment**: Preserve original OKRs, mark adjusted ones with `[ADJUSTED]`, and include rationale per change.
- **Previous-quarter scores provided**: Calibrate ambition -- if the team scored 1.0 on everything, push harder; if below 0.4, investigate whether the cause was execution or target-setting.
© OneWave-AI · MIT · OneWave-AI/claude-skills