BF agentrelay
Reliable agent-to-agent communication protocol for transferring large payloads via shared files with pointer references and secret code verification. Triggered by explicit 'AgentRelay:' prefix in messages.
As a process F 33/100 · Will not run — References files that are not bundled: /Users/gavinliu/.openclaw/workspace/skills/agentrelay/README.md, /Users/gavinliu/.openclaw/workspace/skills/agentrelay/RELEASE_NOTES.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: /Users/gavinliu/.openclaw/workspace/skills/agentrelay/README.md - warning
missing-refreference to a missing file: /Users/gavinliu/.openclaw/workspace/skills/agentrelay/RELEASE_NOTES.md
Process rating: all ten parameters 33/100
- 0Tools and files. 2 referenced file(s) missing: /Users/gavinliu/.openclaw/workspace/skills/agentrelay/README.md, /Users/gavinliu/.openclaw/workspace/skills/agentrelay/RELEASE_NOTES.md
- 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1805 tokens
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 tags): a typed call is more reliable
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -214 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 205: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (23 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.