BC claw-bond
Lets two OpenClaw agents negotiate, coordinate, and commit to tasks in real time — peer-to-peer task negotiation, commitment tracking, and deadline reminders. Uses a relay for connection setup; all messages are end-to-end encrypted.
As a process C 62/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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 7
✓ No critical or high findings
Medium and low: 7
-
low Secrets in code
secret-high-entropy-tokennegotiate.py:109High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)NOISE_PATTERN: bytes = b"Nois…256"
detector -
low Dangerous commands
cmd-cron-mentionnegotiate.py:2739Mentions editing / listing crontab (string literal in code, not executed)f.write("# crontab -e\n\n")code literal -
low Dangerous commands
cmd-cron-mentionnegotiate.py:2774Mentions editing / listing crontab (string literal in code, not executed)f"To activate Path A alerts: run `crontab -e` and paste that line.\n"
code literal -
low Dangerous commands
cmd-cron-mentionnegotiate.py:2857Mentions editing / listing crontab (string literal in code, not executed)print(f"Crontab entry written to: {cron_file}\nRun `crontab -e` and paste that line to activate Path A alerts.")code literal -
low Dangerous commands
cmd-cron-mentionpermissions.json:76Mentions editing / listing crontab (quoted — discussed, not commanded)"cron_note": "negotiate.py install writes a ready-to-paste crontab line to skills/claw-bond/crontab-entry.txt. No cron entry is registered automatically. The user pastes it manually via crontab -e. cr
quoted -
low Exfiltration
read-dotenvrelay/docker-compose.yml:4Reads a .env file (code comment)# cp .env.example .env # then fill in RELAY_SECRET
comment -
low Exfiltration
read-dotenvrelay/README.md:16Reads a .env filecp .env.example .env
Files scanned: 24. 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
body-longSKILL.md body ≈ 5761 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 62/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70Execution cost. Instruction body is 5761 tokens
- 100Steps. 81 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 21 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (6 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
- +1No license
- +2Single-language instructions
- +3Description length 232: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 81 items
- +4Has examples (39 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.