skills.rest
seasonmac
seasonmacCOMMUNITY
Explore all skills by this author →
GitHub

acp-router

Route harness requests to ACP runtime or direct acpx sessions based on user intent.

1|Updated Apr 28, 2026
Search Tags:#routing#sessions#harness#openclaw#acp#thread-spawn
One-click install
npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill acp-router-seasonmac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/seasonmac/Full-Scene-Agents/tree/main/openclaw/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill acp-router-seasonmac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route requests to ACP harnesses for OpenClaw ACP runtime sessions or direct acpx-driven sessions, ensuring code runs in the correct context and that coding-agent thread spawns are handled after reading this skill.

Core Features & Use Cases

  • Intent-driven routing: Detects whether a request should use the ACP runtime or direct acpx flow based on user intent.
  • Mode selection and agent mapping: Chooses the correct harness agent and path (e.g., pi, claude, codex, openclaw, gemini, qwen) and handles thread-spawn requirements.
  • Robust session management: Guides thread creation through the ACP session flow and enforces preflight checks before spawning.

Quick Start

Provide a harness task and this skill will route it to the appropriate ACP path for execution.

Frequently Asked Questions about acp-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route coding-agent thread spawns to the correct ACP session path?▼

To route thread spawns, the system detects user intent and maps the request to either the OpenClaw ACP runtime or direct acpx session path, enforcing preflight checks before guiding thread creation.

When do I need to use ACP runtime sessions versus direct acpx sessions?▼

ACP runtime sessions are needed for OpenClaw orchestrated execution, whereas direct acpx sessions handle specific acpx-driven tasks, with routing determined automatically by analyzing the user's intent.

How does agentId mapping work when opening a harness session?▼

AgentId mapping selects the correct harness agent and path—such as pi, claude, codex, openclaw, gemini, or qwen—based on the specific harness interface and thread-spawn requirements detected in the request.

What happens if the ACP backend is unavailable during session routing?▼

If an ACP backend is unavailable, the routing logic applies safe fallback handling to manage the failure, preventing the thread spawn from proceeding without a valid execution context.

Can I use this to manage session routing for multiple harness interfaces?▼

Yes, this supports agent mapping for various harness interfaces, routing requests to the appropriate ACP session path by matching the detected intent with the correct runtime or direct acpx flow.

Related Skills

Explore More Software Engineering Skills→
openclaw-easyopenclaw-easy
14

acp-router

Routes natural-language requests to the correct OpenClaw ACP harness flow.

Community
Intermediate
borealBytesborealBytes
7

acp-router

Route coding-harness requests to ACP runtime or acpx-backed sessions.

Community
Advanced
lemonlqflemonlqf

acp-router

Route coding requests to AI harnesses via ACP runtime or acpx sessions.

Community
Advanced
zyj18860969891-bytezyj18860969891-byte

acp-router

Route user requests to the appropriate OpenClaw ACP harness path.

Community
Advanced