BC feature-matrix-parity
Update the OpenClaw and Hermes comparison columns of the ZeroClaw feature-and-support matrix. Use this skill when the user wants to refresh, fill, or verify parity data in docs/book/feature-matrix-parity.toml, add a new comparison row or section to the feature matrix, or re-walk the competitor repos for support status. Trigger on: 'update the feature matrix', 'refresh parity', 'fill the parity TOML', 'walk OpenClaw and Hermes', 'the matrix shows Unknown', 're-verify the comparison columns', 'add a row to the feature matrix'.
Update the OpenClaw and Hermes comparison columns of the ZeroClaw feature-and-support matrix.
As a process C 57/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: 1. 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 57/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 11 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2362 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 530: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.