CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

okr

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

52

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/okr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 commendably lean and the single-action workflow is mostly clear, but the skill delegates all substance to a script and SKILL.md that are not present in this bundle, leaving it not fully actionable. References that resolve within the bundle and brief flag explanations are the main fixes.

Suggestions

Bundle or correctly reference the generator script (and the referenced SKILL.md) so the paths resolve within the skill's own directory, e.g. scripts/okr_cascade_generator.py.

Document or exemplify the --teams and --contribution options with a concrete example, not just --json, so the full CLI surface is actionable.

Remove the duplication between 'Supported strategies' and the 'Examples' list, and use the freed space to show a sample of the generated OKR output structure.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation and assumes Claude's competence, but there is minor redundancy: the five strategies are listed in 'Supported strategies' and repeated verbatim in 'Examples', and 'Input Format' restates the header summary. Fits anchor 4 rather than 5 because of this duplication.

4 / 5

Actionability

Concrete command syntax, script CLI arguments (--teams, --contribution, --json), and exact example invocations are present, but the referenced script does not exist in the bundle, the --teams and --contribution options are never explained or exemplified, and no output structure is shown. Guidance is concrete yet incomplete, fitting anchor 3 rather than 4.

3 / 5

Workflow Clarity

This is a simple single-action skill and the action (/okr generate <strategy> with enumerated supported strategies) is mostly unambiguous. It is not a 5 because the script path points outside the bundle and the optional flags lack any explanation, leaving minor gaps.

4 / 5

Progressive Disclosure

Both references ('product-team/skills/product-strategist/scripts/okr_cascade_generator.py' and the Skill Reference SKILL.md) point to files absent from the bundle, making the skill a pointer card whose navigation fails against the actual bundle structure. This fits anchor 2 (references effectively buried/broken) rather than 3, where references would at least resolve.

2 / 5

Total

13

/

20

Passed

Description

53%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 states a clear, specific capability but omits any when-to-use trigger guidance and lacks natural synonym terms users might say. Distinctiveness is decent thanks to the OKR-cascade niche. Adding a 'Use when...' clause and common synonyms (goals, quarterly planning, objectives and key results) would lift it substantially.

Suggestions

Add a 'Use when...' trigger clause, e.g. 'Use when the user wants to create OKRs, cascade company strategy into team goals, or plan quarterly objectives.'

Include natural synonym terms users would actually say, such as 'objectives and key results', 'goals', 'goal setting', and 'quarterly planning', to broaden trigger coverage.

Enumerate the concrete deliverables (company-level, department-level, and team-level objectives and key results) as separate actions to strengthen specificity.

DimensionReasoningScore

Specificity

"Generate OKR cascades from company strategy to team objectives" names the domain and one concrete action with its scope, matching the 1-2-concrete-actions anchor. It is not a 4 because it does not list several distinct actions, and not a 2 because it is more specific than merely naming the domain.

3 / 5

Completeness

The description gives a clear 'what' (generate OKR cascades from company to team level) but has no 'Use when...' clause or equivalent trigger guidance; "Usage: /okr generate <strategy>" is invocation syntax, not a when-to-use statement. Per the judging guideline, completeness is capped at 3.

3 / 5

Trigger Term Quality

Keywords like "OKR", "cascades", "company strategy", "team objectives", and "key results" are relevant, but common user variations such as "goals", "quarterly planning", or "objectives and key results" are missing. Coverage is relevant but incomplete, fitting anchor 3 rather than anchor 4.

3 / 5

Distinctiveness Conflict Risk

"OKR cascades" is a fairly distinct niche unlikely to trigger the wrong skill, with only minor overlap risk against generic strategy/planning/goal-setting skills. It is not a 5 because there are no explicit distinct trigger phrases and some overlap with planning-related skills remains.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Revision

27cfcd0

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill