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 that restates the skill name without providing any meaningful information about capabilities, use cases, or trigger conditions. It fails on all dimensions: no concrete actions, no natural trigger terms, no explicit 'when to use' guidance, and no distinguishing characteristics.
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.'
Replace the duplicate trigger term with varied natural language phrases users would actually say, such as 'KPI', 'key performance indicator', 'define metrics', 'what should I measure', 'performance tracking'.
| 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 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explicit 'Use when...' clause and no description of capabilities beyond the skill name itself. | 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 many other skills, and 'kpi definition helper' without further specificity doesn't carve out a clear niche or distinguish it from other analytics or metrics-related 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/placeholder with no substantive content. It contains no actionable guidance for KPI definition—no example KPIs, no SQL queries, no metric formulas, no data modeling patterns, and no concrete instructions of any kind. It fails on every dimension by providing only generic boilerplate that repeats the skill name without teaching Claude anything useful.
Suggestions
Add concrete KPI definition examples with actual SQL queries, metric formulas (e.g., churn rate = lost customers / total customers), and dimensional breakdowns.
Provide a clear workflow for defining a KPI: identify business objective → choose metric → define calculation → write SQL → set targets → validate data quality.
Include executable code examples such as SQL templates for common KPIs (revenue growth, customer retention, conversion rate) that Claude can adapt.
Remove all boilerplate sections (When to Use, Example Triggers, Capabilities) that just restate the skill name and replace with actual instructional content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'kpi definition helper' excessively, and provides zero domain-specific information. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is no concrete guidance, no executable code, no SQL examples, no KPI definitions, no formulas, no schemas—nothing actionable whatsoever. The skill describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The 'step-by-step guidance' mentioned in Capabilities is never actually provided. There are no validation checkpoints or sequences. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful content organization. No bundle files exist to reference either. | 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
3a2d27d
- 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.