CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openclaw-relay

OpenClaw session relay: prompts/posts via local/remote acpx over SSH.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/openclaw-relay/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, operationally dense skill body: copy-paste-ready commands for every flow, explicit mode-selection criteria, a genuine failure-recovery loop, and disciplined scope (including a pointer to a different skill for the Team-server case). The main weaknesses are a referenced aliases file that is missing from the shipped bundle and a few implicit checkpoints (e.g., obtaining <last-seq>, running doctor up front).

Suggestions

Actually ship config/session_aliases.json with the placeholder values the body promises (or state that the file must be created), so `targets`/`resolve` work out of the box instead of silently resolving to no aliases.

State in the Async Workflow where <last-seq> comes from (e.g., printed by `start` or visible via `show`) so the wait command is unambiguous.

Lead the Quick Start with a one-line "run `doctor` first" checkpoint to make the validation step explicit in the happy path, not only in Failure Handling.

DimensionReasoningScore

Conciseness

The body is command-first and lean with no explanation of concepts Claude already knows; sections like "Session Rules" and "Output Relay" are terse checklists. Minor trimmable instances exist: the SSH host is repeated across several examples, and the Defaults list overlaps the env-var list. Not 5 because of that repetition; not 3 because there is no real over-explanation.

4 / 5

Actionability

Every flow comes with copy-paste-ready commands (doctor, targets, resolve, ask, force-send, ensure/send/show, start/wait, ssh variants) with real flags, plus a multiline escape hatch (--text-file) and a JSON example shape for aliases. This matches the anchor-5 example of fully executable commands covering the common cases.

5 / 5

Workflow Clarity

Mode selection has explicit criteria, the async flow is sequenced (start -> wait --after-seq -> show), and failure handling provides a recovery loop (doctor -> status -> show -> cancel -> ensure -> retry) plus a probe-before-send rule for uncertain routes. Not 5 because checkpoints like where to obtain <last-seq> and when to run doctor proactively are left implicit rather than stated as an ordered checklist.

4 / 5

Progressive Disclosure

Sections are clear and references are one level deep: "scripts/openclaw_relay.py" exists in the bundle and is well signaled. The gap is that "config/session_aliases.json" is referenced and claimed to "ship with placeholders" but is absent from the bundle (the script silently falls back to empty aliases), and the 31KB script's full CLI surface stays inline-only. These are minor organization gaps, matching anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is compact, technically precise, and highly distinctive, but it reads like a compressed label rather than a trigger-rich description. It lacks a "Use when..." clause and omits the natural trigger phrases and action breadth that would let a user (or Claude) reliably select this skill.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user says 'use acpx', asks to relay a message into an OpenClaw channel/session, or wants a remote bridge over SSH."

Broaden the action coverage beyond "prompts/posts" to the concrete verbs the skill supports (ask, publish/force-send, queue async work and wait), matching the body's Session Rules.

Include the natural synonyms users say ("bridge", "gateway", "ACP", "relay this") in the description itself so they surface at skill-selection time.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ("prompts/posts via local/remote acpx over SSH") plus transport detail, but stops short of the broader action coverage (ask, publish, force-send, async queue/wait) that would make it comprehensive. Fits anchor 3 better than 4 because it lists only two actions rather than several.

3 / 5

Completeness

The "what" is clear (relay prompts/posts across local/remote sessions over SSH), but there is no "Use when..." or equivalent explicit trigger guidance, which caps this dimension at 3 per the judging guidelines. Not 2 because the "what" half is concrete and specific.

3 / 5

Trigger Term Quality

Relevant keywords are present ("OpenClaw", "session relay", "acpx", "SSH"), but common natural variations a user might say ("bridge", "gateway", "send/relay a message", "ACP") are missing from the description itself. Not 4 because the body's own richer trigger phrases never make it into the description.

3 / 5

Distinctiveness Conflict Risk

"OpenClaw session relay" with "acpx" occupies a clear niche with distinct, unlikely-to-collide identifiers; minimal conflict risk with other skills. Clearly matches the anchor-5 example pattern of a distinct niche with specific triggers.

5 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

steipete/agent-scripts

Path

skills/openclaw-relay/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.