BD chef-cooking
AI 智能家庭厨助。输入食材/想吃的菜/饮食偏好，自动推荐菜谱、输出烹饪步骤指导、食材替换建议、多日菜单规划、烹饪技巧问答，生成卡片式交互 HTML 报告。覆盖八大菜系+家常菜，内置 200+ 菜谱库 + 联网搜索补充。Triggers: 做什么菜, 怎么做, 菜谱, 食谱, 烹饪, 做饭, 下厨房, 今天吃什么, 推荐菜, 炒菜, 红烧, 清蒸, 煲汤, 家常菜, 川菜, 粤菜, 菜单规划, 食材替换, 烹饪技巧, 厨房安全, chef, cooking, recipe, 帮我做菜, 晚餐吃什么, 午餐吃什么, 怎么炒, 怎么炖, 怎么煮
AI 智能家庭厨助。输入食材/想吃的菜/饮食偏好，自动推荐菜谱、输出烹饪步骤指导、食材替换建议、多日菜单规划、烹饪技巧问答，生成卡片式交互 HTML 报告。覆盖八大菜系+家常菜，内置 200+ 菜谱库 + 联网搜索补充。Triggers: 做什么菜, 怎么做, 菜谱, 食谱, 烹饪, 做饭, 下厨房, 今天吃什么…
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "agent_created"
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. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 822 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 273: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (6 code blocks)
- +3All 8 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.