acp-router
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill’s routing purpose is coherent, but it directs the agent to automatically repair/install ACPX components and use shell-driven harness sessions, so it should be reviewed before use.
Use this skill only if you want OpenClaw to drive ACP-compatible coding harnesses. Before allowing repair, confirm any npm install into `extensions/acpx` and any gateway restart. Prefer the ACP runtime path over raw exec when possible, and avoid sending secrets or broad workspace context to persistent external harness sessions.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the ACP backend fails, the agent may download/install package code and modify local OpenClaw extension artifacts before the user has explicitly chosen that repair path.
This directs the agent to perform a runtime npm install that modifies the ACPX extension area. The behavior is disclosed, but it is automatic repair behavior and is not represented by an install spec or declared binary requirements.
First attempt automatic local repair: ... ensure plugin-local pinned acpx is installed in `extensions/acpx` ... If binary is missing or version mismatched, install plugin-local pinned version: `cd extensions/acpx && npm install --omit=dev --no-save acpx@<pinnedVersion>`
Require explicit user approval before npm install or repair, pin the exact package version and integrity, document required binaries, and add a clear rollback or cleanup path.
The agent may run local CLI commands to relay prompts to coding harnesses; poorly quoted prompts or paths could cause unintended command behavior.
Direct acpx operation is central to the skill, but it relies on shell command construction with user-supplied prompt and workspace placeholders.
Use `exec` commands that call `${ACPX_CMD}` ... `${ACPX_CMD} codex -s oc-codex-<conversationId> --cwd <workspacePath> --format quiet "<prompt>"`Prefer the scoped `sessions_spawn` ACP runtime path when available, and ensure any direct `exec` command safely quotes prompt text, session names, and paths.
Information sent to the harness may remain available in that persistent session and influence later responses in the same conversation.
The skill intentionally preserves external harness context across turns using deterministic session names.
Reuse a stable session name per conversation so follow-up prompts stay in the same harness context.
Avoid sending secrets unless necessary, and provide users a way to start a fresh session or clear the harness context.