AD fitbuddy
专属健身追踪与饮食记录助手。支持体重/饮食/运动/饮水记录、BMR/TDEE自动计算、碳循环等饮食策略、食物数据库自动计算营养素、营养知识问答、训练计划制定、趋势图表、定时提醒。触发词：记录饮食/体重/运动/饮水、健身打卡/设置/初始化、今天吃了/练了、查看进度、训练建议、喝水了吗、蛋白质/碳水/脂肪/热量相关、饮食建议。Use when user mentions fitness tracking, diet logging, weight recording, exercise logging, calorie counting, nutrition questions, or asks about their fitness progress.
As a process D 46/100 · Unfinished process — 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: 20. 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 46/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
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 736 tokens
- 100Running it twice. No mutating operations
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
- -32 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 329: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (9 of 10)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.