BC ansible
MeshOps distributed coordination mesh for OpenClaw gateways: ring-of-trust admission, CRDT-synced state, capability-contract routing, and governed delegation. Named for the ansible from Ender's Game, not the infrastructure tool.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
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: 20. 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: MeshOps distributed coordination mesh for OpenClaw gateways: ring-… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 54/100
- 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. 17 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (ansible) differs from the folder (meshops-control-plane)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 51 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1686 tokens
- low 16 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
- +4No input/output examples
- -45 reference files, but SKILL.md never points to them: the model will not open them
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 228: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 51 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.