
openclaw-relay
OpenClaw session relay: prompts/posts via local/remote acpx over SSH.
- Installs
- 116
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/steipete/agent-scripts --skill openclaw-relay- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads openclaw-relay automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
OpenClaw Relay
Use this when the job is:
- "talk to Molty"
- "relay this into an OpenClaw channel session"
- "use acpx"
- "send this through the gateway via acp"
- "work through a remote OpenClaw bridge over SSH"
Not for team.openclaw.ai: starting or inspecting Roboclaw sessions on the Team server is
$team-handoff from openclaw/agent-skills (one Gateway request as Peter through Cloudflare Access; operator values live in ~/.config/openclaw/team-handoff.env).
One skill. Two transports:
localssh
Default to local for direct telephone-game work from the current OpenClaw checkout. Use ssh when the target agent/session lives on another machine.
For Peter's setup, Molty normally lives on the Mac Studio gateway, reached as steipete@steipete-macstudio.local; avoid the mac-studio SSH alias for one-shot relay work because that alias auto-attaches tmux.
Script path: scripts/openclaw_relay.py
Target aliases file: config/session_aliases.json
Mode Selection
Choose local when:
- the user explicitly says
acpx - the target session is on the current machine
- the goal is quick relay or private ask
Choose ssh when:
- the target agent/session lives on another host
- you want a persistent bridge session
- you need async queue/wait/show flows on a remote machine
Defaults
The script avoids baked-in personal paths. Override with env or flags when needed.
- transport:
local - local repo cwd: current working directory
- local acpx repo:
<cwd>/extensions/acpx - ssh host:
steipete@steipete-macstudio.local - remote repo cwd:
<remote-home>/clawdbot - remote acpx repo:
<remote-home>/Projects/oss/acpx - gateway token file:
<home>/.openclaw/gateway.token - control session name:
codex-bridge - target aliases file:
config/session_aliases.json
Useful env vars:
OPENCLAW_RELAY_TRANSPORTOPENCLAW_RELAY_HOSTOPENCLAW_RELAY_CWDOPENCLAW_RELAY_ACPX_REPOOPENCLAW_RELAY_GATEWAY_URLOPENCLAW_RELAY_GATEWAY_TOKEN_FILEOPENCLAW_RELAY_SESSIONOPENCLAW_RELAY_TARGETS_FILE
Quick Start
Health check:
python3 scripts/openclaw_relay.py doctor
List known target aliases:
python3 scripts/openclaw_relay.py targets
Resolve a target alias:
python3 scripts/openclaw_relay.py resolve --target maintainers
Ask a target session a question privately:
python3 scripts/openclaw_relay.py ask \
--target maintainers \
--message "Summarize the current vibe in this channel."
Force-send text to the resolved target:
python3 scripts/openclaw_relay.py force-send \
--target maintainers \
--text "Deploy is done."
For multiline posts, use --text-file <path> or --text-file - instead of
shell-quoting the message.
Force-send media when the user explicitly wants a channel post:
python3 scripts/openclaw_relay.py force-send \
--transport ssh \
--host steipete@steipete-macstudio.local \
--target maintainers \
--text "Demo video." \
--media /tmp/demo.mp4
Use the persistent control session:
python3 scripts/openclaw_relay.py ensure
python3 scripts/openclaw_relay.py send --message "Reply with exactly OK."
python3 scripts/openclaw_relay.py show
Remote host example:
python3 scripts/openclaw_relay.py doctor --transport ssh --host steipete@steipete-macstudio.local
python3 scripts/openclaw_relay.py send \
--transport ssh \
--host steipete@steipete-macstudio.local \
--message "Reply with exactly OK."
Async Workflow
Queue work and poll the same control session:
python3 scripts/openclaw_relay.py start --message "Work on X and reply when done."
python3 scripts/openclaw_relay.py wait --after-seq <last-seq>
python3 scripts/openclaw_relay.py show
Target Aliases
config/session_aliases.json ships with placeholders. Replace them with real values for your setup.
Example shape:
{
"main": "agent:<agentId>:main",
"maintainers": "agent:<agentId>:discord:channel:<channelId>"
}
Session Rules
Use these rules when choosing a command:
- Want a private reply from a specific session:
ask - Want the target session to decide whether to post:
publish - Want a guaranteed direct post:
force-send - Want blocking continuity with the control brain:
send - Want fire-and-forget async:
start, thenwaitandshow - Want to stop queued work:
cancel
Failure Handling
If relay work fails:
- Run
doctor. - Run
status. - Run
show. - If the control session is wedged, run
cancel, thenensure, then retry.
If route discovery is uncertain:
- Resolve the target first.
- Prefer alias or exact session key.
- Use a tiny probe ask before sending the real payload.
Output Relay
Return the actual assistant text or delivery result, not shell noise.
For relay tasks, report:
- transport used
- target session key
- whether the route probe/resolve succeeded
- final posted or returned result
FAQ
What does the openclaw-relay skill do?
OpenClaw session relay: prompts/posts via local/remote acpx over SSH.
How do I install openclaw-relay?
Run npx skills add https://github.com/steipete/agent-scripts --skill openclaw-relay in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/openclaw-relay/ (personal) or .claude/skills/openclaw-relay/ (project).
Which AI agents can use openclaw-relay?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is openclaw-relay safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains openclaw-relay?
It is published by steipete in steipete/agent-scripts. It has 116 recorded installs.
More from steipete/agent-scripts
video-transcript-downloader
steipete/agent-scripts
yt-dlp downloads: video, audio, subtitles, transcripts, clips, playlists.
brave-search
steipete/agent-scripts
Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.
skill-cleaner
steipete/agent-scripts
Codex/OpenClaw skill audit: live budget, usage, duplicates, compact descriptions.
create-cli
steipete/agent-scripts
CLI UX/spec: args, flags, help, output, errors, config, dry-run.
markdown-converter
steipete/agent-scripts
Markdown conversion: PDF, Office, HTML, data, OCR, audio, ZIP, YouTube.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available