metric-calculator

Compute well-defined metrics from existing formulas, datasets, or test outputs. Use as an explicit/manual helper when the metric definition is already known, not for choosing the overall analysis owner or dashboard strategy.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/metric-calculator/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and well-structured for a simple skill, but it lacks concrete executable guidance and an explicit sequenced workflow with validation checkpoints, keeping actionability and workflow clarity at 3.

Suggestions

Add a short concrete worked example or formula template for a representative metric computation to raise actionability.

Provide a minimal sequenced workflow (e.g. identify formula -> gather inputs -> compute -> sanity-check units/denominators) with an explicit validation checkpoint.

Spell out the sanity-check step as a verifiable action rather than just listing it as a possible output.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no padding or explanation of concepts Claude already knows; every section earns its place, matching the anchor 5 example.	5 / 5
Actionability	As an instruction-only skill it gives concrete-ish guidance (metric types, conversion targets, sanity checks), but the guidance stays generic without specific formulas or executable steps, fitting anchor 3.	3 / 5
Workflow Clarity	No sequenced multi-step workflow is provided and validation checkpoints are only mentioned as an output rather than a process step; even for a simple skill this lands at anchor 3 due to implicit sequence and missing checkpoints.	3 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, needs no external references, and is organized into clear sections, meeting the simple-skill exception for a score of 5.	5 / 5
	Total	16 / 20 Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is reasonably specific and distinguishes the skill from neighbors, but it lacks an explicit 'Use when...' trigger clause and broad keyword coverage, capping completeness and trigger-term quality at 3.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when you need to compute a known metric such as a rate, ratio, or scorecard from available data.'

Broaden trigger terms to include natural synonyms users say, such as KPIs, benchmarks, measures, or scorecards.

Enumerate a few more concrete computation actions (e.g. compute rates, ratios, deltas) to lift specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the metric-computation domain and a couple of concrete actions ('Compute well-defined metrics from existing formulas, datasets, or test outputs'), but does not enumerate several specific actions, fitting anchor 3 rather than 4.	3 / 5
Completeness	A clear 'what' is present, and there is 'when' framing via 'Use as an explicit/manual helper when the metric definition is already known', but there is no explicit 'Use when...' trigger clause, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant keywords like 'metrics', 'formulas', 'datasets', and 'test outputs' appear, but common synonyms users might say (e.g. KPIs, benchmarks, measure) are missing, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	The 'not for choosing the overall analysis owner or dashboard strategy' caveat carves out a clear niche and reduces conflict with adjacent skills, sitting between anchors 4 and 5 and fitting 4 best.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/metric-calculator/SKILL.md
Commit: d5ae560

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.