BC update-guardian
更新守护者是面向Agent平台与已安装技能包的自动更新能力包。它不只是设个每日cron跑 update命令，更解决四个高频痛点：更新引入破坏性变更导致线上崩、更新后无法回滚、 依赖版本冲突、更新时机撞上业务高峰。 核心能力： - 预检干跑：先dry-run检查兼容性，发现breaking change先告警不自动应用 - 版本快照：更新前自动快照当前版本与配置，可一键回滚 - 兼容性矩阵：检测新版本与已安装技能/依赖的版本冲突 - 智能调度：按业务低峰期调度更新，避开高峰 - 配置备份：更新前备份配置文件，更新后自动diff校验 - 健康检查：更新后跑健康检查，失败自动回滚 适用场景： - Agent平台与技能包每日自动更新 - 担心更新引入破坏性变更 - 更新后出问题不知怎么回滚 - 多技能依赖同一库的不同版本冲突 - 需要在业务低峰期安全更新 差异化： - 原始版本只设cron跑update，本版补齐"预检+快照+回滚"三段式安全更新 - 移除原仓库特定烙印，通用化适配任意Agent平台与技能包管理器 - 新增兼容性矩阵与依赖冲突检测 - 新增智能调度（业务低峰期） - 新增健康检查失败自动回滚 触发关键词：自动更新、技能更新、版本回滚、破坏性变更、兼容性检查、快照、更新调度
更新守护者是面向Agent平台与已安装技能包的自动更新能力包。它不只是设个每日cron跑 update命令，更解决四个高频痛点：更新引入破坏性变更导致线上崩、更新后无法回滚、 依赖版本冲突、更新时机撞上业务高峰。 核心能力： - 预检干跑：先dry-run检查兼容性，发现breaking…
As a process C 58/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.
- 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 · 0
✓ No critical or high findings
Files scanned: 2. 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") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1886 tokens
- 100Running it twice. No mutating operations
- 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 552: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (16 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.