BC flowforge-builder-free
用JSON定义自动化工作流,支持定时触发、文件监控、手动触发三种触发方式。
用JSON定义自动化工作流,支持定时触发、文件监控、手动触发三种触发方式。
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureSoftware developmentCustomer supporttype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 Dangerous commands
cmd-cron-mentionSKILL.md:78Mentions editing / listing crontabcrontab -e
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 41 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2808 tokens
- 100Progress reporting. Reports progress
- low 10 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)
- +3Description length 37: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 39 headings
- +3Step-by-step instructions: 41 items
- +4Has examples (22 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.
External checks
ClawHub: clean
This is a workflow-automation skill whose file, network, command, watch, and cron examples are disclosed and aligned with its stated purpose, though users should scope workflows carefully.
LLM: benign (high) · VirusTotal: · 22 Jul 2026