BC developer-self-improve-core
开发者自改进核心技能 - 自动错误防重、自检、规则生成、记忆清洗、定时提醒 核心功能: - 每轮回答前:自动错误防重 - 每轮回答后:自动自检 + 生成规则草案 - 累计 10 轮对话/每周:自动记忆清洗扫描 - 自动提醒:每天 9:30 钉钉推送待确认规则 核心原则: - AI 只提议,人类终审 - 绝不自动写入/修改/删除长期记忆 - 用户指令 > 长期规则 > AI 临时草案
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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-mentionREADME.md:57Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-cron-mentionscripts/setup-automation.sh:47Mentions editing / listing crontab (string literal in code, not executed)echo " crontab -e"
code literal -
low Dangerous commands
cmd-cron-mentionSKILL.md:79Mentions editing / listing crontabcrontab -e
Files scanned: 10. 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 53/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
- 100Tools and files. No external tools needed
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1171 tokens
- 100Running it twice. No mutating operations
- low 11 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
- -214 emoji in the instructions: noise for the model
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 194: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (24 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: suspicious
This skill mostly matches its stated memory-helper purpose, but it includes an under-scoped auto-confirm path that can persistently change future agent behavior from free-form message text.
LLM: suspicious (high) · VirusTotal: · 29 May 2026