Metric Calculator - Auto-activating skill for Data Analytics. Triggers on: metric calculator, metric calculator Part of the Data Analytics skill category.
33
Quality
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 severely underdeveloped and fails on all dimensions. It provides no concrete actions, uses redundant and unnatural trigger terms, lacks both 'what' and 'when' guidance, and is too generic to be distinguishable from other data-related skills. The description appears to be a template or placeholder rather than a functional skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Calculates business metrics including conversion rates, growth percentages, averages, and statistical measures from raw data.'
Add a 'Use when...' clause with natural trigger terms like 'calculate metrics', 'compute KPIs', 'percentage change', 'growth rate', 'statistical analysis'.
Differentiate from general data analytics by specifying the unique scope, e.g., focus on specific metric types, data sources, or calculation methods this skill handles.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Metric Calculator' and 'Data Analytics' without describing any concrete actions. There are no specific capabilities listed like 'calculate averages', 'compute KPIs', or 'generate statistical summaries'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague 'Metric Calculator' label, and the 'when' guidance is limited to the redundant trigger phrase. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'metric calculator, metric calculator' (duplicated). These are not natural terms users would say - users would more likely say 'calculate metrics', 'compute statistics', 'analyze numbers', or specific metric names. | 1 / 3 |
Distinctiveness Conflict Risk | 'Data Analytics' is extremely broad and would conflict with many other analytics, statistics, or data processing skills. Nothing distinguishes this from general data analysis, spreadsheet analysis, or other calculation-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 entirely meta-content with no actual instructional value. It describes what a metric calculator skill would do without providing any concrete guidance, code examples, SQL queries, or calculation methods. The content is a template placeholder rather than a functional skill.
Suggestions
Add concrete SQL examples for common metric calculations (e.g., calculating averages, growth rates, percentages, aggregations)
Include specific code snippets for statistical analysis and visualization libraries (pandas, matplotlib, etc.)
Define actual workflows for metric calculation tasks with clear steps and validation checkpoints
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no SQL examples, no code, no specific commands, no actual metric calculation methods. The skill describes what it claims to do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains no actual steps. There are no processes, sequences, or validation checkpoints for any metric calculation task. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual resources. No references to detailed materials, examples, or related documentation that would contain real 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 | |
0c08951
Table of Contents
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.