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 names a category ('Data Analytics') and a skill name ('Metric Calculator') but provides zero detail about what metrics are calculated, what inputs are expected, or when the skill should be activated. The trigger terms are just the skill name duplicated, offering no useful disambiguation.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Calculates KPIs such as conversion rates, averages, growth rates, and aggregations from tabular data.'
Add a 'Use when...' clause with natural trigger terms like 'calculate metrics', 'KPIs', 'averages', 'growth rate', 'aggregation', 'summary statistics'.
Differentiate from other analytics skills by specifying the unique scope, e.g., what types of metrics, data sources, or output formats this skill handles.
| 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 a vague label, and the 'when' clause is essentially just the skill name repeated. There is no explicit trigger guidance or 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 | 'Data Analytics' and 'Metric Calculator' are extremely broad and generic terms that could overlap with virtually any data processing, reporting, or analytics skill. | 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 actual content. It contains only generic boilerplate headings and placeholder text that could apply to literally any skill topic. There is nothing specific to metric calculation, data analytics, SQL, visualization, or any of the claimed capabilities.
Suggestions
Add concrete, executable code examples showing how to calculate common business metrics (e.g., SQL for MRR, churn rate, conversion rate, retention cohorts).
Define a clear workflow for metric calculation: identify metric → write query → validate results → visualize output, with specific validation steps at each stage.
Include specific examples with input data and expected output, such as a sample dataset and the resulting metric calculations.
Replace all generic boilerplate sections ('When to Use', 'Capabilities', 'Example Triggers') with actual actionable content like SQL templates, statistical formulas, or visualization code snippets.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate with no substantive information. It explains nothing Claude doesn't already know and provides zero domain-specific knowledge about metric calculation. | 1 / 3 |
Actionability | There is no concrete code, no executable commands, no specific examples, and no actual guidance on how to calculate metrics. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no linked resources, and no meaningful structure beyond generic headings that contain no 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 | |
- 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.