AC agent-config-manager
Manage OpenClaw agent configurations, update models, modify bindings, and test configuration changes. Use when: (1) Updating agent model assignments, (2) Modifying channel bindings, (3) Adding/removing agents, (4) Testing config changes before apply, (5) Backing up/restoring agent configs, (6) Validating configuration syntax. Safe editing with validation and rollback support.
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Manage OpenClaw agent configurations, update models, modify bindin… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
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. No external tools needed
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 530 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 378: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (8 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.