SkillAgentSearch skills...

brainstorm-okrs

Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results

Install / Use

npx skills add phuryn/pm-skills --skill brainstorm-okrs

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Tags

Our assessment of brainstorm-okrs

brainstorm-okrs scores 82/100 on our quality scale, 351st of 421 Education & Research skills we index.

Its SKILL.md is 4.2 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 26,568 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
12/15
Adoption
19/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so brainstorm-okrs is actively maintained.
  • Our last check on 2026-10-16 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

brainstorm-okrs compared with similar skills

All 4 of these similar skills score higher than brainstorm-okrs; compare them before choosing.

SkillScoreStarsUpdatedFormat
brainstorm-okrs (this skill)by phuryn8226.6k2mo agoSKILL.md
last30days-skillby mvanhorn10068.0ktodayCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install brainstorm-okrs?
Run npx skills add phuryn/pm-skills --skill brainstorm-okrs. The install tabs above show the steps for each supported agent.
Which AI agents does brainstorm-okrs work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is brainstorm-okrs safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is brainstorm-okrs still maintained?
The repository was last updated about 2 months ago, so brainstorm-okrs is actively maintained.

name: brainstorm-okrs description: "Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs."

Brainstorm Team OKRs

Purpose

You are a veteran product leader responsible for defining Objectives and Key Results (OKRs) for the team working on $ARGUMENTS. Your OKRs must be ambitious, measurable, and clearly aligned with company-wide strategy.

Context

OKRs bridge vision and execution by combining inspirational qualitative objectives with measurable quantitative key results. This skill generates three alternative OKR sets to spark strategic discussion.

Domain Context

OKR (Christina Wodtke, Radical Focus):

  • Objective (Why, What, When): Qualitative, inspirational, time-bound goal. Typically quarterly. Should be SMART.
  • Key Results (How much): Quantitative metrics (typically 3) and their expected values.

OKRs, KPIs, and NSM are interconnected — not alternatives. Don't compare them in a table without explaining their relationship:

  • Key Results always refer to quantitative metrics, some of which might be KPIs.
  • KPIs = a few key quantitative metrics tracked over a longer period. Can be used as Key Results, as health metrics (a balancing practice for OKRs), or you can set Key Results for a KPI's input metrics.
  • North Star Metric = a single, customer-centric KPI. A leading indicator of business success. You can use Key Results to express expected change in NSM.

OKRs are fundamentally about: (1) Setting a single, inspiring goal. (2) Empowering a team to determine the optimal approach. (3) Continuously monitoring progress, learning from failures, and improving.

Instructions

  1. Gather Context: If the user provides company objectives, strategic documents, or team context as files, read them thoroughly. If they reference company strategy, use web search to understand industry benchmarks and best practices for similar products.

  2. Understand the Framework: OKRs have two components:

    • Objective: A qualitative, inspirational goal describing the directional intent
    • Key Results: 3 quantitative metrics (typically) measuring progress toward the objective
  3. Think Step by Step:

    • What is the company strategy?
    • What are the 3-5 most impactful areas the team can influence?
    • How do team efforts ladder up to company goals?
    • What would success look like for customers and the business?
  4. Generate Three OKR Sets: Create three distinct, ambitious OKR options for the $ARGUMENTS team. For each set:

    • Start with a clear, inspiring Objective statement
    • Define exactly 3 Key Results that are:
      • Measurable (can be tracked numerically)
      • Achievable but ambitious (60-70% confidence level)
      • Aligned with company strategy
  5. Example Format:

    Objective: Delight new users with an effortless onboarding experience
    Key Results:
    - CSAT score >= 75% on onboarding survey
    - 66%+ of onboardings completed within two days
    - Average time-to-value (TTV) <= 20 minutes
    
  6. Structure Output: Present all three OKR sets with equal weight. For each, include:

    • Objective (1-2 sentences)
    • Three Key Results (specific metrics with targets)
    • Brief rationale (why this matters to the company and team)
  7. Save the Output: If substantial, save as a markdown document: OKRs-[team-name]-[quarter].md

Notes

  • Ensure each Key Result is independently measurable
  • Avoid output-focused metrics (e.g., "launch 5 features"); focus on outcomes
  • All three OKR sets should be credible, not one clearly better than others
  • Flag any assumptions about data availability

Further Reading

Related Skills

View on GitHub
GitHub Stars26.6k
CategoryEducation
Updated2mo ago
Forks2.8k

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions