AB discord-cross-gateway-delegation
Set up and operate full cross-gateway task delegation between two OpenClaw Discord bots across different PCs/gateways. Use when: another OpenClaw bot lives on a different machine and you want private-lane delegation, structured worker protocols, DM natural-language triggers, worker-side intake, and result relay-back into the original DM. Triggers: 'delegate work to another OpenClaw bot', 'cross-gateway delegation', 'connect another gateway bot', 'Discord worker bot setup', 'maekjini', 'kaijini', 'worker lane', 'DM auto delegation'. NOT for: same-gateway session routing, normal DM chat without delegation, or non-Discord automation.
As a process B 70/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenexamples/task-protocol.md:7High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)id: TASK…ake
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/task-protocol.md:29High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)id: TASK…ake
fixture -
low Secrets in code
secret-high-entropy-tokenexamples/task-protocol.md:42High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)id: KAI-…eck
fixture
Files scanned: 8. 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 70/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 21 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 580 tokens
- 100Running it twice. No mutating operations
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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 638: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 21 items
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.