BC config-validator
A utility skill to validate OpenClaw configuration files (openclaw.json, .env, package.json) and ensure critical settings are present and correctly formatted.
A utility skill to validate OpenClaw configuration files (openclaw.json, .env, package.json) and ensure critical settings are present and correctly formatted.
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.
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:68High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…B4t+D+OBkj…bcE+mWTyvVV7D/zsdE…1Rw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:130High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…XgO/OSZV…lro+7Hf6…5Fj+EDe8gO/lxc1…xvA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:212High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…PuQ+lMYsoxB126+t8fw…I65/Y2OW…8zg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:310High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…kPx+VjMt…8tT+jb3vk/RyaK…M0b+adUT…H2w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:330High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…J7Z+fhpwIAtmCUdZIWZ/YP5R…Nss/dk3u…xGg==",
detector
Files scanned: 4. 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. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 161 tokens
- 100Running it twice. No mutating operations
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 158: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.