BC flow-manager-pro-pro
流程管理器专业版是在免费版基础上的全功能升级，为IoT团队与自动化运维提供企业级Node-RED实例管理能力。除核心流程操作外，解锁多实例管理、完整备份恢复、Docker容器编排、性能监控告警、批量节点操作、流程版本对比回滚、审计日志七大高级功能。Use when 需要系统监控、日志分析、运维告警、部署管理时使用。不适用于物理硬件维修。
流程管理器专业版是在免费版基础上的全功能升级，为IoT团队与自动化运维提供企业级Node-RED实例管理能力。除核心流程操作外，解锁多实例管理、完整备份恢复、Docker容器编排、性能监控告警、批量节点操作、流程版本对比回滚、审计日志七大高级功能。Use when…
As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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
-
low Exfiltration
read-dotenvSKILL.md:81Reads a .env filecp .env.example .env
Files scanned: 2. 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: All mapping items must start at the same column at line 10, column 1: description: "流程管理器专业版是在免费版基础上的全功能升级，为IoT团队与自动化运维提供企业级Node-RED实例管理能力。除核心流程操作外，解… 核心能力：多Node-RED实例并行管理与一键切换、完整备份恢复（流程+上下文+环境变量+节点配置）、Docker容器编排（启停/日志/扩缩容）、实时性能… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 169 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 60/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
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 42 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3805 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 17 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
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 169: enough signal without eating the budget
- +4Structure: 56 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (24 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.