okr
Create quarterly OKRs based on team goals and role. Generates 3 Objectives with 3 Key Results each (9 total), with 70%/100% achievement criteria.
69
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 excels at specificity with concrete deliverables (3 Objectives, 3 Key Results each, achievement criteria) and has a distinct niche in OKR creation. However, it lacks an explicit 'Use when...' clause and could benefit from additional trigger terms that users naturally say when requesting OKR help.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'when the user asks about OKRs, quarterly planning, goal setting, or performance objectives'
Include additional natural trigger terms users might say: 'goal setting', 'quarterly planning', 'performance goals', 'KPIs', 'objectives and key results'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create quarterly OKRs', 'Generates 3 Objectives with 3 Key Results each (9 total)', and specifies '70%/100% achievement criteria'. These are precise, measurable outputs. | 3 / 3 |
Completeness | Clearly answers 'what' (create OKRs with specific structure and criteria) but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through context. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'OKRs', 'Objectives', 'Key Results', 'team goals', 'quarterly', but missing common variations users might say like 'goal setting', 'performance goals', 'KPIs', or 'planning cycle'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct domain (OKRs specifically) and specific structural details (3x3 format, achievement criteria). Unlikely to conflict with general goal-setting or planning skills due to OKR-specific terminology. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid command interface structure but lacks the concrete examples that would make it truly actionable. The output format section describes what OKRs should contain but doesn't show an actual example of generated output. The role-specific guidance is helpful but too abstract to guide quality OKR generation.
Suggestions
Add a concrete example showing actual generated OKR output (one complete Objective with 3 Key Results including 70%/100% targets) so Claude knows exactly what format to produce
Include a brief workflow for interactive mode explaining the question-answer flow and how refinement works
Transform role-specific bullet points into example OKRs or templates that demonstrate the expected style and specificity for each role
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary structure like the extensive tables for options that could be more compact. The role-specific considerations section adds value but could be tighter. | 2 / 3 |
Actionability | Provides command syntax and examples, but lacks concrete output examples showing what generated OKRs actually look like. The role-specific sections are bullet points rather than actionable templates or examples. | 2 / 3 |
Workflow Clarity | The command usage is clear, but there's no workflow for the interactive mode, no guidance on how to refine results, and no validation steps for reviewing generated OKRs before finalizing. | 2 / 3 |
Progressive Disclosure | For a skill of this size, the structure is appropriate with clear sections. References to sample files are mentioned in options without unnecessary nesting. Content is well-organized for discovery. | 3 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
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.