metric-calculator
Metric Calculator - Auto-activating skill for Data Analytics. Triggers on: metric calculator, metric calculator Part of the Data Analytics skill category.
33
0%
Does it follow best practices?
Impact
95%
1.00xAverage 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/metric-calculator/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 repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be indistinguishable from any other data or analytics skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Computes aggregated metrics such as averages, sums, percentages, growth rates, and KPIs from tabular data.'
Add a 'Use when...' clause with natural trigger terms like 'calculate metrics', 'KPIs', 'growth rate', 'aggregate data', 'compute averages', 'dashboard metrics'.
Differentiate from other analytics skills by specifying the unique scope, e.g., whether it handles time-series metrics, business KPIs, statistical summaries, or specific data formats.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Metric Calculator' and 'Data Analytics' but provides no concrete actions. There is no indication of what calculations, metrics, or operations are performed. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is essentially just the skill name repeated. There is no explicit trigger guidance or meaningful use-case description. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'metric calculator' repeated twice. These are not natural terms users would say — users are more likely to say 'calculate metrics', 'KPIs', 'averages', 'aggregations', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Data Analytics' and 'Metric Calculator' could overlap with virtually any analytics, statistics, or data processing skill. Nothing distinguishes it from other data-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 actual instructional content. It contains only meta-descriptions of what the skill claims to do without providing any concrete guidance, code, formulas, or workflows for metric calculation. It fails on every dimension because there is effectively no substantive content to evaluate.
Suggestions
Add concrete, executable SQL examples for common metric calculations (e.g., retention rate, conversion rate, MoM growth) with specific query patterns.
Define a clear workflow: identify metric → write query → validate results → visualize, with explicit validation steps such as checking for NULL handling and date range boundaries.
Include specific formulas and their SQL/Python implementations rather than abstract descriptions of capabilities.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities' descriptions) and replace with actionable content that teaches Claude how to actually calculate and validate business metrics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about metric calculation. Every section restates the same vague concept without adding value. | 1 / 3 |
Actionability | There are no concrete code examples, SQL queries, formulas, commands, or specific instructions. The skill describes what it could do in abstract terms ('provides step-by-step guidance') without actually providing any guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, validation checkpoints, or any indication of how to actually calculate a metric. The content is purely meta-description with no operational substance. | 1 / 3 |
Progressive Disclosure | There are no references to supporting files, no structured navigation, and no content worth disclosing progressively. The skill is a monolithic block of placeholder text with no meaningful organization of actual instructional content. | 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.