AC openclaw-git-manager
Use when you want to track, commit, compare, or rollback OpenClaw configuration changes. Triggers when the user mentions "commit the config", "save this version", "what changed in my config", "restore the previous config", "rollback", "config history", or "git manager". Also activates when OpenClaw configuration files (openclaw.json, credentials, skills) have been modified and need a stable versioned checkpoint before further changes.
Triggers when the user mentions "commit the config", "save this version", "what changed in my config", "restore the previous config", "rollback", "config…
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 43 mutating operations with no state check
- 40Consistency. Frontmatter name (openclaw-git-manager) differs from the folder (git-watcher)
- 60Tools and files. Uses tools (bash, git) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 76 steps, 1 vague phrases
- 100Failures and branches. 5 branches, has a failure section
- 100Execution cost. Instruction body is 2068 tokens
- 100Progress reporting. Reports progress
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (9 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
- +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
- +5Description quotes 7 example trigger phrases
- +3Description length 438: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 76 items
- +4Has examples (3 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.