Guide · Agent skill
How to use the OKR Planner agent skill: setup and examples
Updated · written with AI from the project's own documentation and checked against our catalogue data
The OKR Planner is an agent skill from the genoffice skills collection that turns team goals into a measurable Objectives and Key Results table, delivered as an Excel workbook with a review note. It is written for team leads and managers preparing a quarterly or half-year OKR set, and for people new to OKRs who want a structured draft to edit. By the end of this guide you will know what the skill does, how to install it, how to ask for it, and what to check in its output.
OKR Plannergenspark-ai/genoffice · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Get the okr-planner skill ZIP from this page.
- 2Unzip into a skills folder. Extract it into ~/.claude/skills/ for personal use or the project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. Go to Settings → Capabilities → Skills and upload the ZIP.
- 4Describe your goals. Give the agent your team goals or rough task list, plus the quarter and team level.
- 5Answer the setup questions. Tell the agent about any parent OKR and whether a strategic direction exists.
- 6Supply missing baselines. Fill in the baselines the reply lists as pending, and set your own confidence scores.
- 7Use the review log. Record weekly check-ins in the Review log sheet.
What the OKR Planner skill makes the agent do
Once installed, the agent acts as an OKR coach. You give it team goals or a rough list of things you want to do. It first asks about the cycle (quarter or half-year), the team level (company, department or squad), and whether a parent OKR already exists. If it does, each Objective must map to one of its Key Results.
The agent then drafts 3-5 Objectives, each with 2-4 measurable Key Results. Tasks such as "build feature X" are moved out of the Objectives and recorded as key initiatives under the relevant KR. It builds a workbook with three sheets and comments on weak KRs, such as tasks disguised as results.
- Sheet OKR: objectives, key results, metric definition, baseline, target, current, progress, owner, confidence and key initiatives.
- Sheet Alignment: links this level's Objectives to the parent KRs.
- Sheet Review log: an empty five-column table for weekly check-ins.
Install the OKR Planner skill
Download the skill ZIP from this page. The skill's files are SKILL.md. Unzip it into one of these locations, depending on where you want it available:
- Personal: unzip into ~/.claude/skills/
- Project only: unzip into the project's .claude/skills/ folder
- Claude apps: upload the ZIP under Settings → Capabilities → Skills
Trigger the skill with a natural request
You do not need a special command. Describe your goals in plain language and ask for an OKR table. The skill's description and quick prompts cover requests like the ones below. The source lists two quick prompts you can reuse directly.
- Turn these team goals into this quarter's OKR table
- Check whether this set of OKRs is measurable
- Here is my team's list of things to do for Q3. Draft OKRs for a squad of six engineers and tell me what baselines I need to find.
What to provide and what the skill will not invent
The skill only works from what you type. It does not know your company data. Each Key Result needs a metric, a baseline, a target and a deadline. If you do not know the baseline, the skill marks it "baseline pending" rather than guessing. Confidence scores are your own subjective rating; the first draft leaves them blank or shows an example value.
If your goals cover several departments, split them first and ask for one table per team. The skill will not combine different teams' KRs under one Objective.
Review the workbook and the comments
Check that each KR is a result, not a task. The skill flags output-type KRs (launches, deliveries) when every KR under an Objective is of that type, and suggests swapping at least one for an outcome KR such as a conversion rate. It also warns when a KR is certain to reach 100%, which usually means the target is too low.
The reply contains the review comments and the list of baselines you still need to supply. Use the Review log sheet for your weekly check-ins.
- Progress is a formula, (Current - Baseline) / (Target - Baseline), not a typed value.
- Each KR has exactly one owner.
- Guardrail metrics such as system availability are labelled as guardrail, not growth KRs.
Safety notes: scripts and network
According to the skill's listing, it does not run scripts and does not use the network. It needs spreadsheet tools available to the agent, because it asks the agent to build an Excel workbook. Without those tools, the workbook step will not work.
- Runs scripts: no
- Uses network: no
- Requires: spreadsheet tools available to the agent
What people use it for
- A team lead drafting a quarterly OKR set from a list of planned projects.
- A manager rewriting a task list into measurable results before a planning meeting.
- A new OKR user producing a starting draft to edit with their team.
- Checking an existing set of OKRs for tasks written as results and for missing measures.
Frequently asked questions
How do I install the OKR Planner agent skill?
Download the skill ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.
Do I need anything special to use the okr-planner skill?
It needs spreadsheet tools available to the agent, because it builds an Excel workbook. It does not run scripts and does not use the network, according to its listing.
Is the OKR Planner skill free?
The skill is licensed under Apache-2.0. This page does not state pricing for anything beyond that licence, so check the licence terms and your own tool subscriptions.
Will the skill use my company's real data?
No. It only works from what you type. Missing baselines are marked as pending for you to fill in, and it is designed not to invent numbers or confidence scores.
Can it decide whether OKRs affect performance reviews?
No. The skill says that tying OKRs to performance reviews follows company policy and gives no conclusive recommendation, so check your HR rules.
What should I do if my goals cover several departments?
Split them by team first and ask for one table per team. The skill asks for this separation and may give less useful output for a mixed brief.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
The OKR Planner suits team leads and managers preparing a quarterly or half-year OKR set, and people new to OKRs who want an editable starting draft. It is not suited to final decisions on performance reviews, to briefs that mix several departments without splitting them, or to anyone expecting it to know real company data. Treat its output as a draft and supply the baselines yourself.
Download the skill