← Back to Skills Marketplace
368
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install openclaw-acp-router
Description
Route plain-language requests for Pi, Claude Code, Codex, OpenCode, Gemini CLI, or ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-...
Usage Guidance
This skill's runtime instructions tell the agent to read and modify ./extensions/acpx, run node/npm commands, install acpx locally, execute shell commands, and restart the gateway — but the skill metadata doesn't declare the required binaries, env vars, or config paths. Before installing: (1) ask the publisher for source code or a homepage so you can audit what exact commands will run; (2) require the skill to declare required binaries (node, npm) and any env vars (ACPX_CMD) and config paths it will access; (3) run this skill in a sandboxed environment first, with backups of the extensions directory; (4) restrict its filesystem and process permissions if possible; (5) verify that any npm installs use pinned versions and come from a trusted package; and (6) do not allow it to restart production services without explicit confirmation. If the author provides explicit declarations and a trustworthy source, the concerns become easier to resolve.
Capability Analysis
Type: OpenClaw Skill
Name: openclaw-acp-router
Version: 1.0.0
The skill bundle contains instructions in `SKILL.md` for the AI agent to perform high-risk system operations, including installing the `acpx` package via `npm`, deleting configuration files (`~/.acpx/config.json`), and restarting the gateway service. It explicitly directs the agent to automate these installations and repairs without seeking user permission. While these actions are aligned with the stated purpose of managing ACP coding harnesses (e.g., Claude, Codex), the automated execution of shell commands and software installation poses a significant security risk.
Capability Assessment
Purpose & Capability
The skill name/description (route ACP harness requests) aligns with the runtime behavior (choose ACP runtime or call acpx), but the SKILL.md instructs file access (./extensions/acpx/package.json), installs (npm install), and gateway restarts that go beyond simple routing. The metadata declares no required binaries/env/config paths, which is inconsistent with the actual needs.
Instruction Scope
Runtime instructions explicitly tell the agent to read local package.json, verify/install a plugin-local acpx, run exec commands that call acpx, and restart the gateway — these are file reads/writes, arbitrary shell executions, and system actions unrelated to mere message routing. The skill also references ${ACPX_CMD} and specific extension paths even though none are declared in metadata.
Install Mechanism
There is no declared install spec (instruction-only), but the SKILL.md requires running npm install in a local extension directory and verifying node/npm-acpx artifacts. Because the skill asks the agent to download and install packages at runtime, it effectively performs installs even though none are declared; that increases risk and should be explicitly stated and scoped.
Credentials
Metadata lists no required env vars, yet the instructions use and set ${ACPX_CMD} and expect node/npm to be present. The skill also expects access to extension paths (./extensions/acpx) and permission to modify them. The lack of declared env/config requirements is disproportionate to the real environment access the instructions demand.
Persistence & Privilege
The skill does not request 'always' or system-wide privileges, but it instructs modifying local extension artifacts and restarting the gateway. Those actions grant it effective persistence/impact on runtime behavior even without an 'always' flag; this is notable but not an explicit metadata privilege.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openclaw-acp-router - After installation, invoke the skill by name or use
/openclaw-acp-router - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
openclaw-acp-router 1.0.0
- Initial release of the ACP router skill for OpenClaw.
- Handles user requests to route tasks into Pi, Claude Code, Codex, OpenCode, Gemini, or ACP harness sessions.
- Supports both OpenClaw ACP runtime sessions (using `sessions_spawn`) and direct `acpx`-driven ("telephone game") flows, with comprehensive intent detection.
- Includes robust fallback and repair/recovery logic if ACP backends are unavailable, with strict local install/version handling for `acpx`.
- Provides detailed policies for agent ID mapping and session handling, avoiding unauthorized fallbacks or manual CLI delegation.
- Adds clear rules and command templates for thread, session, and one-shot management, ensuring seamless user experience.
Metadata
Frequently Asked Questions
What is acp-router?
Route plain-language requests for Pi, Claude Code, Codex, OpenCode, Gemini CLI, or ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-... It is an AI Agent Skill for Claude Code / OpenClaw, with 368 downloads so far.
How do I install acp-router?
Run "/install openclaw-acp-router" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is acp-router free?
Yes, acp-router is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does acp-router support?
acp-router is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created acp-router?
It is built and maintained by zch-danny (@zch-danny); the current version is v1.0.0.
More Skills