BF food-nutrition
AI食品营养管理助手。自然语言记录饮食，查询食物营养成分，生成每日/每周营养报告(HTML)，基于中国膳食指南(DRIs 2024)提供个性化饮食建议。内置80+常见中国食物数据库，支持TianAPI在线查询。触发器: 营养, 食物, 饮食记录, 热量查询, 减肥饮食, 今天吃了, 营养成分, 饮食报告, 饮食建议, food nutrition, 卡路里, 吃什么, 记饮食。
AI食品营养管理助手。自然语言记录饮食，查询食物营养成分，生成每日/每周营养报告(HTML)，基于中国膳食指南(DRIs 2024)提供个性化饮食建议。内置80+常见中国食物数据库，支持TianAPI在线查询。触发器: 营养, 食物, 饮食记录, 热量查询, 减肥饮食, 今天吃了, 营养成分, 饮食报告…
As a process F 35/100 · Will not run — References files that are not bundled: scripts/html_report.py, scripts/nutrition_calc.py
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Bash WebFetch
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: AI食品营养管理助手。自然语言记录饮食，查询食物营养成分，生成每日/每周营养报告(HTML)，基于中国膳食指南(DRIs 2024)… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/html_report.py - warning
missing-refreference to a missing file: scripts/nutrition_calc.py - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: scripts/html_report.py, scripts/nutrition_calc.py
- 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
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 413 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
- +1No license
- +2Single-language instructions
- +3Description length 190: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 52.