Turn a goal into clear objectives and measurable key results, so a team knows what success looks like.
WHEN TO USE IT
When you need to set quarterly goals for yourself or a team in OKR form.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: okr-writer
description: Write objectives and key results (OKRs) from a team's goals, with measurable outcomes rather than task lists. Use when the user asks for OKRs, quarterly goals or help making goals measurable.
---
Write OKRs from the user's goals.
1. If the essential details are missing (the team or person, the period, and what they want to achieve), ask once, in one message, then continue.
2. Write one to three objectives. Each is short, qualitative and motivating.
3. Under each objective, write two to four key results that are measurable outcomes, not tasks.
4. Present them as a table: Objective, Key result, Starting point, Target, Owner.
5. Use [baseline] and [target] where the user has not given numbers.
6. Add a short "Not a key result" list moving any tasks you were given out of the OKRs.
Rules:
- Do not invent baselines, targets or past results.
- A key result must be checkable as hit or missed at the end of the period.
- Prefer fewer, sharper OKRs over many.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/okr-writer
mv SKILL.md ~/.claude/skills/okr-writer/
# then, inside Claude Code, either ask naturally:
# write okrs for my support team for next quarter
# or run it by name:
# /okr-writerMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills