AC session-openclaw-bridge
Configure, validate, and troubleshoot a Session Messenger ↔ n8n ↔ OpenClaw bridge for two-way text messaging and image exchange when the hosted relay supports attachments. Use when setting up or repairing the n8n/OpenClaw side of a Session relay, importing or patching the n8n workflow, validating relay endpoints like /health, /poll, and /send, checking whether the deployed relay matches the expected API, confirming attachment capability for photos/files, or preparing the integration for publication on ClawHub.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-password-literalscripts/validate_relay.py:35Hard-coded password / key literal (may be an example)api_key = sys.argv[2] if len(sys.argv) > 2 else None
Files scanned: 5. 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 56/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 594 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 515: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.