AC hi-register
Register the Hi agent on this OpenClaw host AFTER the `clawhub:hirey` ClawPack plugin has been installed. Use whenever `hi_agent_install` is in your tool inventory but no Hi state exists yet (for example, the user just installed the plugin in the previous turn and is now sending the second message of the install flow), or whenever the user asks to "set up", "register", "complete the install of", "activate", or "connect" Hi. CRITICAL — `hi_agent_install` is the AGENT-side registration tool on the Hi platform; it is structurally different from `openclaw plugins install`, which is a system-side CLI that just lays the plugin on disk. Never confuse the two. Never report a fabricated `agent_id`.
Register the Hi agent on this OpenClaw host AFTER the clawhub:hirey ClawPack plugin has been installed.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 2. 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 55/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
- 30Running it twice. 6 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 20 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 1189 tokens
- 100Progress reporting. Reports progress
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
- +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
- +5Description quotes 5 example trigger phrases
- +3Description length 698: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 20 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.