brainstorm-okrs

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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./pm-execution/skills/brainstorm-okrs/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a clear, actionable, well-structured instruction skill with a sensible multi-step workflow and useful domain framing. Its main weakness is conciseness: parts of the Domain Context re-explain OKR basics Claude already knows.

Suggestions

Trim the Domain Context basics (e.g., the SMART/qualitative-inspirational definition of an Objective) that Claude already knows, keeping only the OKR/KPI/NSM relationship guidance that is non-obvious.

Add a short explicit validation step or checklist in the Instructions (e.g., 'Verify each KR is independently measurable and outcome-focused') to promote the workflow_clarity and actionability from a 4 to a 5.

Consider moving the detailed OKR/KPI/NSM framing into a references/ file so SKILL.md reads as a leaner overview, improving progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but the Domain Context re-explains concepts Claude already knows (e.g., Objective = 'Qualitative, inspirational, time-bound goal… Should be SMART'). The OKR/KPI/NSM relationship framing earns its place, but the basics could be trimmed. Not a 2 because the bulk is genuinely task-relevant rather than padded filler.	3 / 5
Actionability	Provides concrete, executable guidance: generate exactly three OKR sets, exactly 3 Key Results, 60-70% confidence, a copy-paste example format, and a filename pattern. Not a 5 because there is no concrete method to validate KR quality beyond the soft Notes checklist.	4 / 5
Workflow Clarity	A clear 7-step numbered sequence (gather context → understand framework → think step by step → generate → example → structure → save) with the Notes section acting as a soft quality checklist. Not a 5 because there is no explicit validation/feedback loop, though the non-destructive task does not strictly require one.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Purpose, Context, Domain Context, Instructions, Notes, Further Reading) with externally-signaled Further Reading links; self-contained with no bundle files. Not a 5 because at ~80 lines the Domain Context could arguably live in a reference file, leaving the overview leaner.	4 / 5
	Total	15 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-crafted: it states what the skill does and when to use it with concrete, natural trigger phrases and a distinct OKR niche. Its only mild weakness is specificity, as the core action is essentially one thing (brainstorm OKRs) framed several ways.

Dimension	Reasoning	Score
Specificity	Names the OKR domain and a couple concrete actions ('Brainstorm team-level OKRs', 'aligned with company objectives', 'qualitative objectives with measurable key results') but coverage is not comprehensive. Not a 4 because it lists essentially one core action (brainstorming OKRs) rather than several specific distinct actions.	3 / 5
Completeness	Explicitly answers both 'what' ('Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results') and 'when' ('Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say — 'setting quarterly OKRs', 'aligning team goals', 'company strategy', 'drafting objectives', 'write effective OKRs'. Not a 5 because it lacks some common synonyms/variations (e.g., 'goal-setting', 'targets') and there are no file-extension triggers.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (team-level OKR brainstorming) with distinct triggers unlikely to fire for unrelated skills, minimizing conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: phuryn/pm-skills
Path: pm-execution/skills/brainstorm-okrs/SKILL.md
Commit: 18468a9

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.