Guide · Agent skill
How to use the Brainstorm Team OKRs agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The brainstorm-okrs skill is a set of instructions that teaches an AI agent to draft team-level OKRs (Objectives and Key Results) aligned with company goals. It is written for product and team leads preparing quarterly goals, and for people learning how to write measurable goals. After this guide you will know how to install the skill, trigger it with a plain request, and judge whether its output is useful for your team.
Quick start
- 1Download the ZIP. Get the brainstorm-okrs skill ZIP from this page.
- 2Unzip the skill. Extract the folder so that SKILL.md sits inside it.
- 3Place it in the skills folder. Move the folder to ~/.claude/skills/ for personal use, or to .claude/skills/ inside a project.
- 4Or upload it in the apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 5Make a natural request. Describe your team, the quarter and any strategy documents in plain language.
- 6Review the three sets. Compare the objectives, key results and rationales, and check each metric against your real data.
What is an agent skill and what does this one do?
An agent skill is a folder containing a SKILL.md file with instructions that an AI agent can load when a task matches the skill's description. This one is named brainstorm-okrs and comes from the phuryn/pm-skills collection, licensed MIT.
OKRs pair one qualitative objective with a few measurable key results that show whether you reached it. When you ask for help setting quarterly goals, the skill tells the agent to act like an experienced product leader and produce three alternative OKR sets. Each set has an objective, three key results with numeric targets, and a short rationale. The skill also asks the agent to read any company strategy documents you provide and to flag assumptions about whether the data needed to measure results exists.
Install the brainstorm-okrs skill
Download the ZIP for this skill from this page and unzip it. Then choose one of two locations. For a personal install available across your projects, place the skill folder in ~/.claude/skills/. To limit it to a single project, place it in that project's .claude/skills/ folder.
If you use the Claude apps instead of a local setup, you can upload the skill under Settings → Capabilities → Skills.
- Personal (all projects): ~/.claude/skills/
- Single project: .claude/skills/ inside the project folder
- Claude apps: Settings → Capabilities → Skills, then upload
Trigger the skill with a natural request
You do not need a special command. The skill's description tells the agent when to use it: setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs. Describe your team and the period in plain language, and mention any strategy documents you want the agent to read.
The skill's instructions use a team name placeholder, so name the team clearly in your request. Ask for a quarter so the file name can be built from it if you want a saved document.
- Set Q3 OKRs for the payments product team. Our company goal this year is to grow enterprise revenue.
- Here is our strategy doc. Draft team OKRs for the onboarding squad for next quarter.
- Teach me how to write good OKRs by showing three options for our mobile app team.
Read the output critically
Expect three OKR sets of equal weight, each with a 1-2 sentence objective, exactly three key results with targets, and a rationale. The skill asks for key results that are measurable, ambitious but achievable (around 60-70% confidence), and tied to company strategy. It also warns against output metrics such as shipping a set number of features, and favours outcomes instead.
The outputs are brainstorm material. Check every target against data your team actually collects, because the skill itself tells the agent to flag data availability assumptions. If the agent produces a substantial document, the skill asks it to save the result as a markdown file named OKRs-[team-name]-[quarter].md.
- Confirm each key result can be measured with data you have today.
- Pick one set, or combine elements from several, before sharing with leadership.
- Keep the rationale so you can explain the choice later.
Safety notes: scripts and network access
According to the listing, this skill requires nothing beyond the agent, does not run scripts, and does not use the network. The only file listed is SKILL.md.
The skill's instructions do mention using web search for industry benchmarks when you reference company strategy. Whether that happens depends on the agent environment you use, so review what your agent is allowed to access before you ask for it.
Tips for better OKRs
Give the agent real inputs. Company objectives, a strategy document, and the team's current metrics produce more grounded key results than a one-line request.
Use the skill to learn as well as to draft. The three sets are useful for comparing how a single objective can be measured in different ways.
Remember how the parts relate. The skill notes that key results often refer to KPIs, and that a North Star Metric can be expressed through key results. OKRs, KPIs and North Star Metrics work together rather than replacing each other.
What people use it for
- Drafting three candidate OKR sets for a product team before a quarterly planning meeting.
- Turning a company strategy document into team-level objectives with measurable key results.
- Learning how to write measurable goals by reading worked examples of objectives and key results.
- Spotting assumptions about whether the data needed to track a key result is available.
Frequently asked questions
Is the brainstorm-okrs skill free to use?
The skill is published under the MIT licence, as stated on this page. Check the licence file in the source repository for the full terms before reuse.
What do I need to run the brainstorm-okrs skill?
The listing states that nothing extra is required, it does not run scripts, and it does not use the network. You do need an AI agent that supports agent skills so it can load SKILL.md.
Where do I install an agent skill like this one?
Place the unzipped folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder. In the Claude apps, upload it under Settings → Capabilities → Skills.
Can the skill write final, data-verified targets?
No. The outputs are brainstormed suggestions, and the skill tells the agent to flag data availability assumptions. Verify each target against your own data before committing to it.
Does this skill work for non-product teams?
It is written from a product-leadership perspective. Teams in other functions may need to adapt the framing of the objectives and key results to fit their work.
How is this different from writing OKRs by hand?
It gives you three alternative sets at once with rationales, which is useful for discussion. Writing by hand gives you more control over context you have not shared with the agent, so the two work well together.
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
Use this skill if you are a product or team lead preparing quarterly OKRs, or you are learning to write measurable goals and want several worked options to discuss. Pick a different approach if you need final, data-verified targets or OKRs for a non-product function without adapting the framing.
Download the skill