kpi-definition-helper
Kpi Definition Helper - Auto-activating skill for Data Analytics. Triggers on: kpi definition helper, kpi definition helper Part of the Data Analytics skill category.
34
0%
Does it follow best practices?
Impact
98%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/kpi-definition-helper/SKILL.mdQuality
Discovery
0%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 with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would employ, and provides no guidance on when Claude should select this skill. It would be indistinguishable from other data analytics skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Helps define, document, and refine Key Performance Indicators (KPIs) including setting targets, identifying data sources, and establishing measurement methodologies.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about defining KPIs, key performance indicators, business metrics, success measures, OKRs, or needs help choosing what to measure.'
Remove the duplicate trigger term and replace the auto-generated boilerplate with a human-written description that clearly distinguishes this skill from general data analytics or reporting skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it is a 'kpi definition helper' and belongs to 'Data Analytics' but never describes what it actually does (e.g., define KPIs, suggest metrics, create dashboards). | 1 / 3 |
Completeness | Neither the 'what does this do' nor the 'when should Claude use it' questions are meaningfully answered. The description lacks any explanation of capabilities and has no explicit 'Use when...' clause with real trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'kpi definition helper' repeated twice, which is not a natural phrase a user would say. Missing natural terms like 'KPI', 'key performance indicator', 'metrics', 'define metrics', 'business goals', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Data Analytics' could overlap with countless other skills, and 'kpi definition helper' is too vague to carve out a clear niche or distinguish it from other analytics or reporting skills. | 1 / 3 |
Total | 4 / 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 substantive content. It repeatedly references 'kpi definition helper' without ever defining what a KPI definition helper does, how to use it, or providing any concrete guidance. Every section contains only generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable examples of KPI definitions (e.g., SQL queries for calculating specific KPIs like customer churn rate, revenue growth, etc.) with input/output examples.
Define a clear workflow for KPI definition: identify business objective → select metric → define calculation logic → validate with sample data → document thresholds and targets.
Include a structured KPI template or schema (e.g., name, description, formula, data source, frequency, owner, target) that Claude can use to generate consistent KPI definitions.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content such as common KPI patterns by domain (finance, marketing, operations) with specific SQL or Python examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'kpi definition helper' excessively, and provides zero domain-specific information or actionable content. | 1 / 3 |
Actionability | There are no concrete steps, code examples, commands, or specific guidance. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any steps. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints — just generic claims about capabilities without any actual process. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to external files, no structured navigation, and no meaningful organization of content across 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
c8a915c
- 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.