BC logo-design-guide
logo设计原则与AI图像生成实用指南,帮助用户产出专业logo。覆盖字标、字母标、图形、抽象、吉祥物、组合型等logo类型,讲解提示词结构、色彩心理学、尺寸适配规范、文件格式交付全流程,并提供通义万相、文心一格等国内AI平台适配方案与错误码体系。当用户请求设计logo、品牌标志、AI生成图标、企业徽标时触发本技能。
logo设计原则与AI图像生成实用指南,帮助用户产出专业logo。覆盖字标、字母标、图形、抽象、吉祥物、组合型等logo类型,讲解提示词结构、色彩心理学、尺寸适配规范、文件格式交付全流程,并提供通义万相、文心一格等国内AI平台适配方案与错误码体系。当用户请求设计logo、品牌标志、AI生成图标、企业徽标时触发本技能。
As a process C 53/100 · Has gaps — 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: 2. 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 "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 54 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2089 tokens
- 100Running it twice. No mutating operations
- low 19 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
- +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
- +2Single-language instructions
- +3Description length 159: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.