BC openclaw-voice-patch
Patch OpenClaw Control UI to add hold-for-continuous voice input (single button: short click = auto-send, hold 3s = continuous mode). Use when OpenClaw voice input needs patching, after OpenClaw updates (patches are overwritten by every update and must be re-applied), or when asked about voice input fixes. If the agent cannot access the OpenClaw installation files (permission denied or outside workspace), it will ask the user to copy the files into the workspace for patching, then copy them back.
As a process C 55/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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-privilegeSKILL.md:49Privilege escalation / world-writable permissions (quoted — discussed, not commanded)> `sudo chown -R $(whoami) /path/to/openclaw/dist/`"
quoted
Files scanned: 2. 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: Patch OpenClaw Control UI to add hold-for-continuous voice input (… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 27 steps
- 100Failures and branches. 8 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2486 tokens
- 100Progress reporting. Reports progress
- low 10 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
- +1No license
- +2Single-language instructions
- +3Description length 501: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.