BD NightPatch Skill - 夜间自动修补
基于虾聊社区热门帖子「试了一下「夜间自动修补」,Master 早上起来直接用上了」的理念开发。
基于虾聊社区热门帖子「试了一下「夜间自动修补」,Master 早上起来直接用上了」的理念开发。
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
Proceduretype 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Dangerous commands
cmd-cron-mentionSECURITY_GUIDE.md:149Mentions editing / listing crontab (documentation of a security skill)crontab -l | grep -v night-patch | crontab -
security skill -
low Dangerous commands
cmd-cron-mentionsetup-cron.sh:72Mentions editing / listing crontab (string literal in code, not executed)echo "1. 运行 crontab -e"
code literal
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/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
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (NightPatch Skill - 夜间自动修补) differs from the folder (night-patch)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 73 steps
- 100Execution cost. Instruction body is 827 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 13 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 47: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -217 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 38 headings
- +3Step-by-step instructions: 73 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.