BD auto
Helps automate repetitive tasks with scripts, scheduled jobs, and simple workflows. Use when the user wants to script an action, run something on a schedule (cron, Task Scheduler), automate builds or deploys, or reduce manual steps in a workflow.
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- 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
✓ No critical or high findings
Medium and low: 2
-
medium Dangerous commands
cmd-persistenceSKILL.md:39Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)- 命令行创建：`schtasks /create /tn "任务名" /tr "powershell -File C:\path\to\script.ps1" /sc daily /st 09:00`（参数依需求改）。
quoted -
low Dangerous commands
cmd-cron-mentionSKILL.md:43Mentions editing / listing crontab (quoted — discussed, not commanded)- **cron**：`crontab -e`，一行一条。格式：分 时 日 月 周 命令。
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 49/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
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 353 tokens
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 246: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 20 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.