agentleFS
njpattennjpatten/claude-skills/okr-coach-claude-skill/SKILL.md

okr-manager

Skill0 starsChanged 2 months agoMITView on GitHub

Creates, evaluates, and grades OKRs (Objectives and Key Results) for businesses and individuals using Google-style methodology. Supports annual, half-year, and quarterly cycles for solopreneurs, small teams, and larger organizations. Triggers on 'create OKRs', 'set goals', 'review my OKRs', 'weekly check-in', 'monthly review', 'grade my OKRs', or 'plan my quarter'.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create, evaluate, and grade OKRs using Google-style methodology.

    line 8
  2. Distinctive:

    Committed: Must achieve. Target score: 1.0.

    line 21
  3. Distinctive:

    Use the tiered framework. Every question is skippable — user can say "skip" or "not sure."

    line 59
  4. Distinctive:

    If user mentions multiple businesses:

    line 82
  5. Distinctive:

    If everything goes perfectly, what's different in 1 year?

    line 108
  6. Distinctive:

    Ask: "Did you set goals last period?

    line 121
  7. Distinctive:

    Write 2–4 Objectives that are:

    line 137
  8. Distinctive:

    When user shares existing OKRs for feedback:

    line 236
  9. Distinctive:

    Not measurable: "Improve brand awareness"

    line 246
  10. Distinctive:

    All lagging indicators (no early warning)

    line 248
  11. Distinctive:

    Ask for status on each Objective: "On track 🟢, At risk 🟡, or Off track 🔴?"

    line 272
  12. Distinctive:

    Do weekly team check-ins (15 min)

    line 387
  13. Distinctive:

    No revenue pressure — focus on what matters to you

    line 402

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OKR Manager

Create, evaluate, and grade OKRs using Google-style methodology. Works for solopreneurs, small teams, larger companies, and personal goals.

Core Concepts

Formula: "I will [Objective] as measured by [Key Results]"

Scoring (0.0–1.0 scale):

  • 0.0–0.3: Failed / minimal progress
  • 0.4–0.6: Made progress, didn't hit target
  • 0.6–0.7: Sweet spot for aspirational OKRs (this IS success)
  • 0.8–1.0: Exceeded expectations (if hitting 1.0 consistently, goals aren't ambitious enough)

OKR Types:

  • Committed: Must achieve. Target score: 1.0. Failure requires explanation.
  • Aspirational: Stretch/"moonshot". Target score: 0.7. 70% = success.

Modes of Operation

Mode 1: Create OKRs

Triggers: "create OKRs", "set goals", "help me write OKRs", "plan my quarter"

→ Run Discovery → Draft → Validate → Finalize

Mode 2: Evaluate OKRs

Triggers: "review my OKRs", "is this a good OKR", "evaluate these goals", "give me feedback"

→ Apply quality checks → Score dimensions → Provide specific fixes

Mode 3: Weekly Check-In

Triggers: "weekly check-in", "OKR update", "how am I doing"

→ Quick status on each objective → Identify blockers → Set weekly focus

Mode 4: Monthly Review

Triggers: "monthly review", "score my OKRs", "monthly OKR check"

→ Score each KR numerically → Identify what's working/struggling → Adjust tactics

Mode 5: Grade OKRs (End of Period)

Triggers: "grade my OKRs", "end of quarter review", "final OKR score"

→ Final scores with evidence → Reflection questions → Learnings → Prompt for next period


Mode 1: Create OKRs

Step 1: Discovery

Use the tiered framework. Every question is skippable — user can say "skip" or "not sure."

Opening:

"I'll ask a few questions to write better OKRs for you. All questions are optional — skip any that don't apply. Ready?"

Tier 1: Quick Start (Always Ask)

#QuestionWhy It Matters
1What type of OKRs are we creating?Determines approach
• Solopreneur / Freelancer
• Small team (2-10 people)
• Larger company / Department
• Personal (non-work)
2What's your business/role in one sentence?Sets context
3What time period? (Year / Half / Quarter)Scopes the OKRs
4What domain? (Work / Personal / Both)Keeps focus clear
5What would make this period a success?Surfaces real priorities
6What's your biggest constraint? (time, money, skills, clarity)Keeps goals realistic
7What's the ONE thing that would change everything?Identifies the lever

Important: One Business Per OKR Set

If user mentions multiple businesses:

"OKRs work best when focused on ONE business at a time — it's about concentration, not spreading thin. Which business should we focus on? (We can do a separate session for others.)"

Approach by Type:

TypeMax ObjectivesKey Differences
Solopreneur2-3Weekly self-check-ins, include revenue KR, brutal self-honesty required
Small team3-4Light cascading, shared accountability, assign KR owners
Larger company3-5Formal cascading, department alignment, mix committed/aspirational
Personal2-4Life areas (health, finance, relationships, growth), no revenue pressure

After Quick Start:

"That's enough to start drafting. Want to go deeper for sharper OKRs? I can ask about [your vision / past results / resources] — or we can jump to drafting."

Tier 2: Strategic Deep Dive (Optional)

Offer sections à la carte:

Section A: Current State

  • What's your current revenue or MRR? (Ballpark fine)
  • How many clients/customers do you serve?
  • What's taking up most of your time?
  • What's your biggest bottleneck or frustration?

Section B: Vision & Direction

  • If everything goes perfectly, what's different in 1 year? 5 years?
  • Is your business model, offer, or ideal customer likely to change?
  • What would you do with unlimited resources?
  • What are you deliberately saying "no" to?

Section C: Resources & Constraints

  • How many hours/week can you realistically dedicate?
  • What resources do you have? (budget, team, tools, network)
  • What external factors could derail you?
  • Who are you depending on? Who's depending on you?

Tier 3: Reflection Round (If Previous Period Exists)

Ask: "Did you set goals last period? Want to reflect before planning ahead?"

If yes:

  • What was your biggest win?
  • What was your biggest failure or disappointment?
  • What goal did you set but never touched? Why?
  • What surprised you?
  • What will you do differently?
  • What assumptions proved wrong?
  • What unfinished work should carry forward?

After discovery, summarize:

"Here's what I'm hearing: [summary]. Does that capture it? Anything to add before we draft?"

Step 2: Draft Objectives

Write 2–4 Objectives that are:

  • Ambitious — Pushes beyond current state
  • Qualitative — Future state, not a metric
  • Memorable — One line, inspires action
  • Action-oriented — Strong verbs (Build, Launch, Establish, Transform, Dominate)

Avoid:

  • Vague verbs: "help," "support," "continue," "maintain"
  • Metrics in objectives (those go in Key Results)
  • Business-as-usual (OKRs are for change, not status quo)

Template: [Verb] [outcome] [context/scope]

Examples:

  • "Build a predictable client acquisition engine"
  • "Launch a productized service offering"
  • "Establish authority as the go-to expert in [domain]"
  • "Transform operations to support 2x growth"

Step 3: Write Key Results

For each Objective, write 2–5 Key Results using SMART criteria:

  • Specific: One metric, one target
  • Measurable: Quantifiable (number, %, $, date)
  • Attainable: Stretch but possible (not fantasy)
  • Relevant: Directly proves the Objective
  • Time-bound: Deadline within the period

Also ensure MECE:

  • Mutually Exclusive: Each KR tracks something different
  • Collectively Exhaustive: Together, KRs = Objective achieved

Template: [Verb] [metric] from [baseline] to [target] by [date]

Examples:

  • "Increase MRR from $2K to $8K by March 31"
  • "Close 5 new clients by end of Q1"
  • "Reduce response time from 24 hours to under 2 hours"
  • "Achieve NPS of 50+ (baseline: 32)"

KR Types:

TypeDescriptionExample
MetricQuantitative change"Increase NPS from 40 to 60"
MilestoneBinary completion"Launch v1.0 by Feb 15"
ThresholdMaintain a standard"Keep response time under 2 hours"

Step 4: Validate Quality

Objective Checks:

  • Would I be proud to achieve this?
  • Can I explain it in one sentence?
  • Does it require real effort/change?
  • Is it outcome-focused (not activity-focused)?

Key Result Checks:

  • Is there a specific number or date?
  • Can a stranger verify completion? (No gray area)
  • Does it measure outcome, not output?
  • Is 70% achievement still meaningful? (The "70% test")

Overall Checks:

  • If all KRs hit 100%, is the Objective achieved?
  • Are there 2–5 KRs (not too few, not too many)?
  • Is at least one KR a "leading indicator" (actionable early)?

Step 5: Classify and Finalize

Mark each OKR as:

  • Committed (target: 1.0) — failure requires explanation
  • Aspirational (target: 0.7) — stretch goal, 70% is success

Output format:

## [Period] OKRs

### O1: [Objective] [Committed/Aspirational]

| KR | Target | Baseline |
|----|--------|----------|
| KR1: [Description] | [Target] | [Baseline] |
| KR2: [Description] | [Target] | [Baseline] |
| KR3: [Description] | [Target] | [Baseline] |

### O2: [Objective] [Committed/Aspirational]
...

Include:

  • Baselines (where they're starting)
  • Review cadence recommendation
  • Key dates/milestones

Mode 2: Evaluate OKRs

When user shares existing OKRs for feedback:

Red Flags to Identify

Weak Objectives:

  • Too vague: "Improve customer satisfaction"
  • Activity-focused: "Launch 3 marketing campaigns"
  • Sandbagging: Easily achievable with no stretch

Weak Key Results:

  • Not measurable: "Improve brand awareness"
  • Too many (6+) or too few (1)
  • All lagging indicators (no early warning)
  • Activities disguised as results: "Send 100 cold emails"
  • Missing baselines

Score Each Dimension (1–5)

Dimension1 (Poor)5 (Excellent)
AmbitionBusiness as usualReal stretch
ClarityVague/confusingCrystal clear
MeasurabilitySubjectiveObjectively verifiable
AlignmentDisconnectedDirectly supports mission
AchievabilityImpossible OR trivialChallenging but possible

Provide specific feedback on what to fix with rewritten examples.


Mode 3: Weekly Check-In

Quick 15-minute status update.

Flow:

  1. Ask for status on each Objective: "On track 🟢, At risk 🟡, or Off track 🔴?"
  2. For each, ask: "Any updates on the Key Results?"
  3. Identify blockers: "What's in the way?"
  4. Set focus: "What's the ONE thing to move forward this week?"

Output:

## Week [N] Check-In — [Date]

| Objective | Status | Trend | Notes |
|-----------|--------|-------|-------|
| O1: [Short title] | 🟢/🟡/🔴 | ↑↓→ | [Brief note] |
| O2: [Short title] | 🟢/🟡/🔴 | ↑↓→ | [Brief note] |

**This week's focus:** [ONE thing]
**Blocker to address:** [If any]

Mode 4: Monthly Review

Deeper 1-hour review with scoring.

Flow:

  1. Score each KR numerically (0.0–1.0):
    • Pull targets
    • Ask for actuals
    • Calculate: (Actual - Baseline) / (Target - Baseline)
  2. Calculate Objective scores (average of KRs)
  3. Identify:
    • What's working? (KRs ≥0.6)
    • What's struggling? (KRs <0.4)
    • What needs to change?
  4. Adjust tactics (not goals) if needed

Output: Monthly scorecard with scores and recommendations


Mode 5: Grade OKRs (End of Period)

Full retrospective and grading.

Flow:

  1. Final score for every KR with evidence (target vs actual)
  2. Grade each Objective:
    • Committed: 1.0 expected, <0.8 needs explanation
    • Aspirational: 0.7 = success
  3. Reflection questions:
    • What was your biggest win?
    • What was your biggest miss?
    • What surprised you?
    • What will you do differently next period?
  4. Determine what carries forward vs. retires
  5. Prompt: "Ready to draft next period's OKRs?"

Output:

## [Period] OKR Grade Report

### Summary
- Objectives: [N]
- Average Score: [X.XX]
- Committed achieved: [X/Y]
- Aspirational at ≥0.7: [X/Y]

### O1: [Objective] — Score: X.XX ✓/✗

| KR | Target | Actual | Score |
|----|--------|--------|-------|
| KR1 | [Target] | [Actual] | 0.XX |
| KR2 | [Target] | [Actual] | 0.XX |

**What worked:** [Insight]
**What blocked:** [Insight]
**Carry forward:** [Yes/No + what]

### Key Learnings
1. [Learning]
2. [Learning]

Adaptations by Type

Solopreneur

ChallengeAdaptation
No one checks your OKRsSchedule weekly 15-min self-review
Wearing all hatsLimit to 2–3 Objectives max
Revenue pressureAlways include at least one revenue-tied KR
Context switchingGroup related KRs under one Objective
IsolationShare OKRs publicly for accountability
PerfectionismRemember: 70% = success for stretch goals

Small Team

  • Assign each KR a single owner
  • Do weekly team check-ins (15 min)
  • Make OKRs visible to whole team
  • Cascade from company → team level

Larger Company

  • Cascade: Company → Department → Team
  • Balance committed (operational) and aspirational (growth)
  • Cross-team OKRs need explicit coordination
  • Quarterly formal reviews with stakeholders

Personal

  • Cover multiple life areas (don't just optimize one)
  • Include maintenance goals (what to keep doing)
  • No revenue pressure — focus on what matters to you
  • Lower stakes, more experimentation allowed

Time Horizon Guidelines

PeriodPurpose# ObjectivesReview Cadence
AnnualDirection/vision2–3Monthly
Half (H1/H2)Strategic priorities2–3Bi-weekly
QuarterlyExecution focus2–4Weekly

Cascading: Annual → Half → Quarter should align. Each quarterly OKR should advance a half-year priority.


Quick Reference

Scoring Scale

ScoreMeaning
0.0–0.3Failed / minimal progress
0.4–0.6Made progress, gap remains
0.6–0.7Success for aspirational
0.8–1.0Full achievement (committed target)

The 70% Test

For every KR, ask: "If we only achieved 70%, would it still be meaningful?"

  • Yes → Good KR
  • No → Rephrase or mark as Committed

Common Mistakes

MistakeFix
Too many objectivesLimit to 2-4 max
Activities as KRsRewrite as outcomes
No baselinesAlways establish starting point
All lagging indicatorsAdd at least one leading indicator
SandbaggingPush for real stretch
Fantasy goalsGround in reality

Reference Files

For detailed examples and templates, see:

  • references/okr-examples.md — Sample OKRs by domain
  • references/grading-guide.md — Detailed scoring rubrics
  • references/strategic-planning-worksheet.md — Standalone worksheet version

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.