BC yu-product-image-generator
AI 商品图生成器 - 多方案选择、12 种语言、分镜规划与批量生成
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Secrets in code
secret-labelled-tokencore/image_generator.py:406Labelled token / key literal (vendor format unknown — verify it is not a live credential)api_key = "sk-6…232"
-
medium Secrets in code
secret-labelled-tokenutils/feishu_sender.py:16Labelled token / key literal (vendor format unknown — verify it is not a live credential)APP_SECRET = "V40t…wYh"
-
low Secrets in code
secret-password-literalcore/image_generator.py:406Hard-coded password / key literal (may be an example)api_key = "sk-6…232"
-
low Secrets in code
secret-labelled-tokentest_generate.py:15Labelled token / key literal (vendor format unknown — verify it is not a live credential) (test fixture / example file)API_KEY = "sk-6…232"
fixture -
low Secrets in code
secret-password-literaltest_generate.py:15Hard-coded password / key literal (may be an example) (test fixture / example file)API_KEY = "sk-6…232"
fixture -
low Secrets in code
secret-high-entropy-tokenutils/feishu_sender.py:16High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)APP_SECRET = "V40t…wYh"
quoted
Files scanned: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 100Tools and files. No external tools needed
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 203 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)
- +3Description length 34: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 4 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.