Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows coding-router

Coding Router

Compatibility entry skill for plan-first coding work in OpenClaw.

144 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Compatibility entry skill for plan-first coding work in OpenClaw.

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Coding Router Skill 💻; Routing Rules; Command Routing (Channel Aliases); Runtime Status Contract; Known ACP Runtime Limitation; Non-Negotiable Gates. It includes spec-recommended sections: edge cases.

File analysis

File analysis: besides SKILL.md, the body references scripts/plan-review, scripts/plan-review-live, references/reviews.md, references/acp-troubleshooting.md. Those resources load on demand.

Coding Router Skill 💻Routing RulesCommand Routing (Channel Aliases)Runtime Status ContractKnown ACP Runtime LimitationNon-Negotiable Gates

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
coding-router
description
Compatibility entry skill for plan-first coding work in OpenClaw.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 4
  • scripts/plan-review
  • scripts/plan-review-live
  • references/reviews.md
  • references/acp-troubleshooting.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "coding-router" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-eceeb6be5f49a4ce-Coding-Router.html
Save it as .cursor/skills/coding-router/SKILL.md or .claude/skills/coding-router/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/kesslerio/coding-agent-openclaw-skill instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/kesslerio/coding-agent-openclaw-skill' --list

npx skills add 'https://github.com/kesslerio/coding-agent-openclaw-skill' --skill 'coding-router'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout

name: coding-router description: "Compatibility entry skill for plan-first coding work in OpenClaw." metadata: {"openclaw":{"emoji":"💻","requires":{"bins":["gh"],"anyBins":["codex","claude"],"env":[]}}}

Coding Router Skill 💻

This file exists for backward compatibility with single-entry skill setups (for example /coding). Canonical sibling skills live at:

  • skills/plan-issue/SKILL.md
  • skills/coding-agent/SKILL.md

Routing Rules

  1. If user asks to plan/scope/estimate/design, follow plan-issue behavior.
  2. For non-trivial implementation requests, produce a plan first and wait for exact APPROVE before any writes.
  3. Only after APPROVE, follow coding-agent behavior with ACP-aware execution routing and CLI fallback.

Command Routing (Channel Aliases)

When invoked via channel aliases:

  • /coding → use this compatibility skill as router.
  • /plan → route directly to plan-issue behavior.
  • /plan-review → route to plan review flow using scripts/plan-review.
  • /plan-review-live → route to interactive plan review checkpoints using scripts/plan-review-live (Lobster in-repo workflow first, legacy fallback).
  • /review_pr → route to review flow using references/reviews.md.

Runtime Status Contract

When wrappers are used for planning/review:

  • Emit RUN_EVENT start at run start.
  • If the run exceeds 30s, emit RUN_EVENT heartbeat every 20s.
  • If interrupted or timed out, emit RUN_EVENT interrupted immediately with exit code.
  • On non-interruption failure, emit RUN_EVENT failed.
  • On success, emit RUN_EVENT done.

Known ACP Runtime Limitation

Issue #43 (upstream) may affect spawned ACP run observability and browser relay profile alias mapping. Use repo-side mitigations and bounded fallback guidance in:

  • references/acp-troubleshooting.md

Non-Negotiable Gates

  1. Never write files, install packages, commit, or open PRs before explicit APPROVE.
  2. Never default to bypass flags (--yolo, --dangerously-skip-permissions).
  3. Use bypass flags only when the user explicitly asks to bypass approvals.

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…