CC hermes-workflow-engine
Hermes DAG工作流引擎 v3.0 — 目标驱动的多步骤任务编排系统。 支持DAG依赖、并行执行、故障转移、资源监控、版本管理、模式检测、可视化面板、社区共享。 当用户要求执行工作流、运行workflow、自动化任务、多步骤任务、创建工作流、模式检测、 版本管理、DAG编排、并行执行、故障转移时触发。 适用场景：重复性多步骤任务自动化、需要暂停/恢复的长流程、跨工具协作编排。
Hermes DAG工作流引擎 v3.0 — 目标驱动的多步骤任务编排系统。 支持DAG依赖、并行执行、故障转移、资源监控、版本管理、模式检测、可视化面板、社区共享。 当用户要求执行工作流、运行workflow、自动化任务、多步骤任务、创建工作流、模式检测、 版本管理、DAG编排、并行执行、故障转移时触发。…
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 · 2
-
high Exfiltration
exfil-read-secret-filesreferences/clawhub-publishing.md:74Reads credential / secret filesscp ro…@….173.120.234:~/.ssh/id_ed25519 ~/.ssh/id_e…kup
-
high Exfiltration
exfil-read-secret-filesreferences/cross-server-deployment.md:67Reads credential / secret filesscp root@SOURCE_IP:~/.ssh/id_ed25519 ~/.ssh/id_e…kup
Files scanned: 21. 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 "triggers"
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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 77 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3707 tokens
- 100Progress reporting. Reports progress
- low 25 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
- -31 of 10 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 192: enough signal without eating the budget
- +4Structure: 41 headings
- +3Step-by-step instructions: 77 items
- +4Has examples (17 code blocks)
- +4Reference files are cited in the instructions (4 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.