BF post-update-maintenance
After an OpenClaw version bump, fix what post-update-awareness noticed. Syncs drifted externalized plugins, restarts the gateway, verifies channel health, and prints a patch for stale openclaw.json entries. Every mutation is dry-run by default and gated behind --apply or explicit user confirmation. Requires post-update-awareness to be installed (reuses its drift detector). Use after an OpenClaw update when post-update-awareness reports drift or stale config, or when the user asks to fix what the awareness skill flagged.
After an OpenClaw version bump, fix what post-update-awareness noticed.
As a process F 53/100 · Will not run — References files that are not bundled: scripts/resolve.sh, scripts/check-plugin-drift.sh
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/resolve.sh - warning
missing-refreference to a missing file: scripts/check-plugin-drift.sh
Process rating: all ten parameters 53/100
- 0Tools and files. 2 referenced file(s) missing: scripts/resolve.sh, scripts/check-plugin-drift.sh
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 8 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 60 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3163 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (23 tags): a typed call is more reliable
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
- -31 of 7 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 525: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 60 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.