BD diary-force
每晚 23:00 自动催日记 + 思维模型分析 + 内化记忆。**强制型习惯养成工具**,适合有写日记习惯但经常拖延的人。包含 6 种思维模型深度分析,将日常经历转化为结构化认知。
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
medium Dangerous commands
cmd-eval-dynamicscripts/diary_force.py:458Dynamic code execution from decoded/untrusted inputos.system('git add . && git commit -m "memory: sync {}" && git push'.format(date)) -
medium Dangerous commands
cmd-eval-dynamicscripts/diary_force.py:491Dynamic code execution from decoded/untrusted inputos.system(f'git add . && git commit -m "memory: sync {date}" && git push') -
medium Dangerous commands
cmd-eval-dynamicscripts/think.py:126Dynamic code execution from decoded/untrusted inputos.system('git add . && git commit -m "memory: sync {}" && git push'.format(date))
Files scanned: 5. 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")
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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (git, python) that frontmatter does not declare
- 100Steps. 43 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1189 tokens
- low 10 top-level sections: this looks like several domains in one skill
- medium 5 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
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 90: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 26 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (12 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.