okr

Generate OKR cascades from company strategy to team objectives. Usage: /okr generate <strategy>

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/okr/SKILL.md

Quality

Content

85%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 lean, well-structured overview for a simple generative skill, with concrete executable commands and clearly signaled references. Minor conciseness redundancy and a missing script invocation example are the only gaps.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept re-explanation, but the "Input Format" section mildly restates the company-to-team cascade already in the intro, a minor trim opportunity.	4 / 5
Actionability	Concrete executable commands ("/okr generate growth", "--json") and a script argument spec cover common cases, with a minor gap: no explicit script invocation example or output sample.	4 / 5
Workflow Clarity	This is a simple single-action skill (pick a strategy keyword, run one command); the action is unambiguous, so the simple-skill exception applies and no destructive/batch validation cap is triggered.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized sections (Usage, Input Format, Examples, Scripts, Skill Reference) and clearly signaled one-level-deep references, satisfying the simple-skill progressive disclosure criterion.	5 / 5
	Total	18 / 20 Passed

Description

61%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 clear and domain-specific with a distinct command trigger, but it lacks an explicit "when to use" clause, which caps its completeness. Trigger term coverage is good though not exhaustive.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when planning OKRs, cascading company strategy to team objectives, or defining key results") to lift completeness above 3.

Include more natural trigger synonyms such as "key results" and "objectives and key results" to broaden trigger term coverage.

Name a second concrete action (e.g., alignment reporting or contribution weighting) to move specificity from a single action toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Generate OKR cascades from company strategy to team objectives" names the OKR domain plus one concrete action (cascade generation), but does not list several specific actions, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	A clear "what" is present ("Generate OKR cascades from company strategy to team objectives"), but there is no "Use when..." trigger clause, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms like "OKR cascades", "company strategy", "team objectives", and "/okr generate" give good coverage a user would say, though some synonyms (e.g. "key results") are absent.	4 / 5
Distinctiveness Conflict Risk	The OKR cascade niche and distinct "/okr" command make it mostly distinct, with only minor overlap risk against generic strategy/planning skills.	4 / 5
	Total	14 / 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: alirezarezvani/claude-skills
Path: .gemini/skills/okr/SKILL.md
Commit: 19392f7

Reviewed: ~11 hours 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.