CD seedance-food-beverage
为 Seedance 2.0（Higgsfield）生成食品和饮料视频提示。在用户想要食品视频、食谱内容、餐厅宣传、饮料广告、烹饪视频、食品 ASMR、菜单展示、食品配送广告、咖啡馆内容或任何食品/饮料视频时使用。在以下情况下触发：食品视频、食谱、烹饪、餐厅、饮料、食品广告、食品 ASMR、菜单、咖啡馆、鸡尾酒、食品摄影视频、开胃吸引力、食品造型、美食直播或任何食品/饮料视频请求。即使是"让我的食物看起来美味"或"餐厅宣传视频"也适用。
为 Seedance 2.0（Higgsfield）生成食品和饮料视频提示。在用户想要食品视频、食谱内容、餐厅宣传、饮料广告、烹饪视频、食品 ASMR、菜单展示、食品配送广告、咖啡馆内容或任何食品/饮料视频时使用。在以下情况下触发：食品视频、食谱、烹饪、餐厅、饮料、食品广告、食品…
As a process D 41/100 · Unfinished process — weak spots: when it triggers, inputs and preconditions, failures and branches
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 files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 Obfuscation
uni-mixed-script-wordSKILL.md:560Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (1 occurrence)**Hero Moment**: The final 3 seconds of latte art being poured. The completed design (leaf, heart, or rosetта) coming into full view as the pour concludes.
Files scanned: 1. 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") - warning
body-longSKILL.md body ≈ 12912 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 41/100
- 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. 26 mutating operations with no state check
- 40Consistency. Frontmatter name (seedance-food-beverage) differs from the folder (zh-CN)
- 40Execution cost. Instruction body is 12912 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 503 steps, 3 vague phrases
- low 17 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 220: enough signal without eating the budget
- +4Structure: 99 headings
- +3Step-by-step instructions: 503 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.