AB fitness-coach
Create beginner-friendly workout plans, calorie and macro estimates, meal structures, food plans, and fitness-oriented recipe suggestions. Use when a user asks for help with fat loss, muscle gain, body recomposition, maintenance calories, macros, meal planning, workout programming, or turning goal-aligned meal ideas into concrete recipes.
As a process B 75/100 · Nearly there — weak spots: consistency, running it twice
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: 6. 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 75/100
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (fitness-coach) differs from the folder (training-and-nutrition-coach)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 12 branches
- 85Steps. 71 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1199 tokens
- 100Progress reporting. Reports progress
- 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 340: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 71 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.