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
Quality
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 essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, lacks any description of capabilities or actions, and provides no guidance on when to use it. The only distinguishing element is the 'OKR' domain term.
Suggestions
Add specific actions the skill performs, e.g., 'Creates OKR tracking spreadsheets, defines objectives and key results, tracks progress percentages, generates quarterly OKR reports'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about objectives and key results, quarterly goals, OKR templates, goal tracking, or performance metrics'
Remove the duplicate trigger term and expand to include variations users would naturally say: 'OKRs', 'objectives', 'key results', 'goal tracker', 'quarterly planning'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Okr Tracker Creator') without describing any concrete actions. There are no verbs or specific capabilities listed - no indication of what creating/tracking OKRs actually involves. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' line just repeats the skill name rather than describing use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('okr tracker creator, okr tracker creator'). Missing natural user phrases like 'objectives', 'key results', 'goals', 'quarterly planning', 'OKR spreadsheet', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'OKR' is a somewhat specific domain term that wouldn't conflict with many skills, the lack of detail about what kind of tracker (spreadsheet? dashboard? document?) and what actions are supported creates potential overlap with general document or spreadsheet skills. | 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 content is essentially a placeholder template with no actual instructional value. It describes what the skill claims to do without providing any concrete guidance, code, examples, or workflows for creating an OKR tracker. The content would need to be completely rewritten with actual implementation details.
Suggestions
Add concrete, executable code or configuration examples showing how to create an OKR tracker (e.g., data schema, API endpoints, or spreadsheet templates)
Define a clear step-by-step workflow for OKR tracker creation with specific actions at each step
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual implementation guidance
Include specific examples of OKR structures, validation rules, and expected outputs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about OKR tracker creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, commands, examples, or specific instructions are provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, steps, or executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The content only describes trigger phrases and vague capabilities without any actual process for creating an OKR tracker. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no structure pointing to detailed materials. There are no references to additional files, examples, or deeper documentation—just empty marketing-style sections. | 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
0c08951
- 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.