metric-calculator
Metric Calculator - Auto-activating skill for Data Analytics. Triggers on: metric calculator, metric calculator Part of the Data Analytics skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill metric-calculatorOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It only provides the skill name, a redundant trigger term, and a generic category label. The description completely fails to communicate what the skill does, what specific calculations or metrics it handles, or when it should be selected over other analytics-related skills.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Calculates business metrics including conversion rates, growth percentages, averages, and KPIs from datasets')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to calculate metrics, compute KPIs, analyze performance numbers, or derive statistics from data')
Differentiate from other analytics skills by specifying the types of metrics or domains covered (e.g., 'financial metrics', 'marketing KPIs', 'operational statistics')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Metric Calculator') and category ('Data Analytics') without describing any concrete actions. There are no specific capabilities listed like 'calculate averages', 'compute KPIs', or 'aggregate data'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just the skill name repeated. There is no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'metric calculator' repeated twice, which is the skill name itself rather than natural user language. Users would more likely say 'calculate metrics', 'compute KPIs', 'analytics calculations', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Data Analytics' is extremely broad and could conflict with many other skills. Without specific capabilities or distinct triggers, this could easily be confused with any analytics, statistics, or calculation-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual content. It describes what a metric calculator skill should do without providing any concrete guidance on calculating metrics, SQL queries, statistical formulas, or visualization approaches. The entire content could be replaced with a single sentence: 'This skill helps with metric calculations' - which would be equally unhelpful but more honest about its emptiness.
Suggestions
Add concrete SQL examples for common metric calculations (e.g., conversion rates, growth rates, moving averages) with executable code
Include specific formulas and their implementations for statistical metrics (mean, median, standard deviation, percentiles)
Provide a clear workflow for metric calculation: define metric -> write query -> validate results -> visualize output
Replace generic capability claims with actual reference materials or inline examples that demonstrate the patterns mentioned
| 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 code, no commands, no specific examples of metric calculations. The content describes what the skill supposedly does but never shows how to actually calculate any metrics. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains no actual steps. There's no sequence, no validation, and no process for calculating metrics. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic statements with no structure for discovery. No references to detailed materials, no examples file, no API reference - just empty promises of capabilities. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.