BD 项目Solution自动分类工具**
根据项目属性（如Competency、名称、描述、EP、公司类型等），从预定义的解决方案列表中为其标注最合适的Solution标签。
As a process D 49/100 · Unfinished process — 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 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.
- 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-wordassets/Competency的Solution清单.csv:6Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (2 occurrences)Customer?,Commercial Mix Modeling & Analytics,��Ŀ������/Ӫ����ļ�Ч���������ü�ˡ�KPI������ӯ��������������������Ϊ���ģ��ǵ��͵���ҵ�����뼨Ч�������� LotusӪ����ˡ����ۼ����˶…
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit keys need to be on a single line at line 2, column 1: name: 项目Solution自动分类工具** version:1.0 ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/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
- 40Consistency. Frontmatter name (项目Solution自动分类工具**) differs from the folder (solution-tag)
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Execution cost. Instruction body is 1256 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 66: 120–800 characters recommended
- +4Structure: 0 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Step-by-step instructions: 9 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 50.