adapters/openclaw/skills/clade-control/SKILL.md
Start, stop, or manage Clade autonomous coding loops remotely
npx skillsauth add shenxingy/claude-code-kit clade-controlInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Start, stop, or manage autonomous coding loops on a remote machine.
User wants to:
Endpoint: POST {CLADE_BASE_URL}/control
Headers:
Authorization: Bearer {CLADE_API_KEY}
Content-Type: application/json
Start a new autonomous coding loop with a goal.
Request:
{
"project": "/home/user/myproject",
"action": "start",
"goal": "Fix all failing tests and ensure 100% pass rate",
"max_iter": 5,
"max_workers": 4,
"model": "sonnet"
}
Translating user intent to parameters:
max_iter: 3model: "opus"max_workers: 2max_iter: 3, model: "haiku"max_iter: 10, model: "opus"max_iter: 10, max_workers: 4, model: "sonnet"The goal can be:
"Fix the login page CSS on mobile""/home/user/myproject/goals/feature-x.md"Response:
{
"ok": true,
"action": "start",
"pid": 12345,
"goal": "/home/user/myproject/.claude/monitor-goal.md",
"max_iter": 5
}
Stop the currently running loop gracefully.
Request:
{
"project": "/home/user/myproject",
"action": "stop"
}
Response:
{"ok": true, "action": "stop", "sentinel": "/home/user/myproject/.claude/stop-start"}
Clear blockers so the loop can be restarted.
Request:
{
"project": "/home/user/myproject",
"action": "clear-blockers"
}
🚀 Loop started!
📋 Goal: {goal summary, first 80 chars}
⚙️ Config: {max_iter} iterations, {max_workers} workers, {model}
🔢 PID: {pid}
Use "status" to check progress.
🛑 Stop signal sent. The loop will finish its current task and exit gracefully.
🧹 Blockers cleared. You can now restart the loop.
development
Orchestrate a fleet of parallel `codex exec` workers with you (Claude Code) as the supervisor — spawn one per isolated git worktree, dispatch headless, verify each INDEPENDENTLY, PR/merge. The manual "codex-ultracode" pattern for fanning out real implementation, research, or review work onto Codex. Bakes in the hard gotchas (stdin blocking, background tracking, don't-trust-self-reports, writer isolation). Triggers on — orchestrate codex, codex workers, codex fleet, spawn codex, delegate to codex in parallel, manual ultracode, 开 codex 小弟, 派 codex worker — NOT for a single cross-vendor opinion (use the `second-opinion-codex` agent), NOT for web-UI worker decomposition (use `/orchestrate`).
development
Create and manage git worktrees for parallel Codex sessions
development
Verify project behavior anchors — compilation, tests, and interaction checks after autonomous runs. NOT the Codex built-in /verify (which runs the app to observe a single change working) — this one walks the AGENTS.md "Features (Behavior Anchors)" list.
documentation
End-of-session documentation sync — updates TODO.md and PROGRESS.md only (run /commit after to commit everything)