How do I install the Coding Router skill?

Run npx skillmds@latest add kesslerio/coding-router in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Coding Router skill do?

Compatibility entry skill for plan-first coding work in OpenClaw. It is listed under Coding & Dev Tools on SkillMD.

Is Coding Router safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Coding Router?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Coding Router free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Coding Router?

kesslerio (@kesslerio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Coding Router by kesslerio — Agent Skill

Name: Coding Router
Rating: 4.2 (5 reviews)
Author: kesslerio

File contents

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

If user asks to plan/scope/estimate/design, follow plan-issue behavior.
For non-trivial implementation requests, produce a plan first and wait for exact APPROVE before any writes.
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

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

---name: coding-routerdescription: Compatibility entry skill for plan-first coding work in OpenClaw.---# 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 Rules1. 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 ContractWhen 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 LimitationIssue #43 (upstream) may affect spawned ACP run observability and browser relayprofile alias mapping. Use repo-side mitigations and bounded fallback guidance in:- `references/acp-troubleshooting.md`## Non-Negotiable Gates1. 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.

Frequently asked questions

Coding Router