DC wanxiang-scroll
游戏资料包与创意文艺工具，56种文风即时切换，交互式协作叙事，回合制异世界人生模拟，Apex创作引擎，拆书融合创作，纯指令版dsv4，文笔润色与文笔提升
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 4
-
high Obfuscation
uni-zero-widthreferences/ch09-拆书融合/01-workflow-guide.md:1Zero-width / invisible characters (possible hidden text) (8 occurrences)# 拆书融合创作工作流指南
-
high Obfuscation
uni-zero-widthreferences/ch09-拆书融合/03-quality-and-rules.md:1Zero-width / invisible characters (possible hidden text) (8 occurrences)# 质量标准与数据传递规则
-
high Obfuscation
uni-zero-widthreferences/index.md:1Zero-width / invisible characters (possible hidden text) (8 occurrences)# 万象绘卷 - 参考文档索引
-
high Obfuscation
uni-zero-widthreferences/原始草稿/00-大数据包.md:1Zero-width / invisible characters (possible hidden text) (8 occurrences)# 大数据包
Files scanned: 80. 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")
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. No external tools needed
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 379 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 76: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.