AC vdot-running-calculator
Calculates VDOT (Jack Daniels' running fitness score) and all five Daniels training paces — Easy, Marathon, Threshold, Interval, Repetition — from one recent race time, using the exact 1979 Daniels-Gilbert VO2/velocity and %VO2max equations that are still the unchanged, industry-standard method used by coaches and elite distance programs today. Use when a user asks for their VDOT score, Jack Daniels training paces, a running pace calculator, race time equivalents/predictions across distances, or "what pace should I run my easy/tempo/threshold/interval/repetition runs at".
Calculates VDOT (Jack Daniels' running fitness score) and all five Daniels training paces — Easy, Marathon, Threshold, Interval, Repetition — from one recent…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1689 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 578: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.