AF openclaw-oa-operator
Install, configure, operate, and productize OA monitoring and self-heal workflows for OpenClaw workspaces. Use when Codex needs to set up or repair `oa-cli`, inspect or stabilize an `oa-project`, run or interpret `oa collect` and `oa serve`, explain G1-G5 metrics and self-heal signals, refine OA dashboards, or prepare the capability for ClawHub skill or plugin release.
As a process F 43/100 · Will not run — References files that are not bundled: scripts/start_oa_server.sh, scripts/stop_oa_server.sh, scripts/manage_oa_launchd.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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/start_oa_server.sh - warning
missing-refreference to a missing file: scripts/stop_oa_server.sh - warning
missing-refreference to a missing file: scripts/manage_oa_launchd.sh
Process rating: all ten parameters 43/100
- 0Tools and files. 3 referenced file(s) missing: scripts/start_oa_server.sh, scripts/stop_oa_server.sh, scripts/manage_oa_launchd.sh
- 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
- 30Running it twice. 4 mutating operations with no state check
- 100Steps. 43 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 989 tokens
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 371: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 43 items
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.