AC inspector
OpenClaw inspector for registering tracked sessions, inspecting stuck or inactive sessions, checking the current session UUID, listing status, and preparing platform-specific watcher services. Use when the user wants session recovery monitoring, inactivity inspection, registration/unregistration, or diagnosis of why a session was or was not inspected. Only perform install/start/enable/restart actions when the user explicitly asks.
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-persistencescripts/inspector.js:225Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed; test fixture / example file)`launchctl load ${shellQuote(plistPath)}`,code literalfixture -
low Dangerous commands
cmd-execpolicy-bypassscripts/inspector.js:244Runs PowerShell with execution policy bypassed (test fixture / example file; quoted — discussed, not commanded)`powershell -ExecutionPolicy Bypass -File "${psPath}"`,fixturequoted
Files scanned: 8. 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 61/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. 1 mutating operations with no state check
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 100Steps. 56 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1485 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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 434: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.