okr-tracker-creator
Okr Tracker Creator - Auto-activating skill for Enterprise Workflows. Triggers on: okr tracker creator, okr tracker creator Part of the Enterprise Workflows skill category.
35
3%
Does it follow best practices?
Impact
94%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/okr-tracker-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak across all dimensions. It reads as an auto-generated stub with no substantive content—no concrete actions, no natural trigger terms beyond the skill name repeated, and no guidance on when Claude should select it. It would be nearly indistinguishable from other enterprise workflow skills and provides no useful information for skill selection.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates OKR tracking spreadsheets, defines objectives and key results, sets progress milestones, and generates quarterly goal reports.'
Add a 'Use when...' clause with natural trigger terms like 'OKR', 'objectives and key results', 'goal tracking', 'quarterly objectives', 'key results', 'KPI tracker', 'team goals'.
Remove the duplicate trigger term ('okr tracker creator' is listed twice) and expand with varied, natural phrases users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the skill ('Okr Tracker Creator') but provides no concrete actions. There is no indication of what it actually does—no verbs like 'creates', 'tracks', 'generates', or any specific capabilities listed. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of functionality and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'okr tracker creator' repeated twice. There are no natural keyword variations a user might say, such as 'OKR', 'objectives and key results', 'goal tracking', 'quarterly goals', 'KPI tracker', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'OKR Tracker Creator' is somewhat specific to a niche domain (OKR tracking), which provides some distinctiveness. However, the lack of concrete detail about what it does versus other enterprise workflow skills means overlap risk remains. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content. It repeatedly names the skill ('okr tracker creator') without providing any actionable guidance, code, examples, or workflows. It reads as auto-generated boilerplate that would provide zero value to Claude when attempting to help a user create an OKR tracker.
Suggestions
Add concrete, executable code or configuration examples for creating an OKR tracker (e.g., a data schema, spreadsheet template structure, or API integration code).
Define a clear multi-step workflow for building an OKR tracker, including steps like defining objectives, setting key results with measurable targets, assigning owners, and establishing review cadences.
Include at least one complete input/output example showing what a user request looks like and what the generated OKR tracker should contain.
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace them with actionable content that teaches Claude something it doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'okr tracker creator' excessively, and contains zero substantive information about how to actually create an OKR tracker. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no examples, no schemas, no specific steps. Every section is vague and abstract, describing what the skill supposedly does without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero steps. There are no sequences, no validation checkpoints, and no actual process described. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed materials, no links to related files, and no meaningful structural organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.