BF linkfox-aigc-imagegen-product
商品图生成(非服饰类)。支持单张或套图:白底主图、场景图、特写图、卖点版式图、A+详情页图。单张单类型直接出图;多张多类型自动编排规划。用户说"做套图""做白底图""做场景图""做卖点图""做A+图""做特写图"时触发。纯图片编辑操作走 linkfox-aigc-imagegen。
商品图生成(非服饰类)。支持单张或套图:白底主图、场景图、特写图、卖点版式图、A+详情页图。单张单类型直接出图;多张多类型自动编排规划。用户说"做套图""做白底图""做场景图""做卖点图""做A+图""做特写图"时触发。纯图片编辑操作走 linkfox-aigc-imagegen。
As a process F 31/100 · Will not run — References files that are not bundled: abs_path, <abs_path>, references/types/<type>.md
The same skill appears in 1 more place: ClawHub
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 · 0
✓ No critical or high findings
Files scanned: 38. 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
missing-refreference to a missing file: abs_path - warning
missing-refreference to a missing file: <abs_path> - warning
missing-refreference to a missing file: references/types/<type>.md - warning
missing-refreference to a missing file: scripts/...
Process rating: all ten parameters 31/100
- 0Tools and files. 4 referenced file(s) missing: abs_path, <abs_path>, references/types/<type>.md
- 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
- 40Consistency. Frontmatter name (linkfox-aigc-imagegen-product) differs from the folder (linkfox-expert-aigc-imagegen-product)
- 100Steps. 43 steps
- 100Execution cost. Instruction body is 2856 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 tags): a typed call is more reliable
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 141: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (3 code blocks)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.