coding-agent
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
What this skill does
# Coding Agent Use for background feature builds, PR reviews, large refactors, and issue-to-PR loops. Do not use for simple edits, read-only lookup, ACP thread-bound work, or any run inside `~/.openclaw`, `$OPENCLAW_STATE_DIR`, or active OpenClaw state dirs. ## Hard rules - Always launch with `background:true`. - Codex and OpenCode: use `pty:true`. - Claude Code: no PTY; use `claude --permission-mode bypassPermissions --print`. - Capture a real notification route before spawning. - Worker must send completion/failure via `openclaw message send`. - Do not rely on heartbeat, system events, or notify-on-exit. - Monitor with `process`; do not kill slow workers without cause. - If user asked for a specific agent, use that agent. - If worker fails/hangs, respawn or ask; do not silently hand-code instead. - Never checkout branches or run background coding agents in `~/Projects/openclaw`; use an isolated checkout. ## Notification block Append this shape to every worker prompt with real values: ```text Notification route: - channel: <notifyChannel> - target: <notifyTarget> - account: <notifyAccount or omit> - reply_to: <notifyReplyTo or omit> - thread_id: <notifyThreadId or omit> When finished, send exactly one completion or failure message using: openclaw message send --channel <channel> --target '<target>' --message '<brief result>' Add --account, --reply-to, or --thread-id only when present above. Do not use openclaw system event or heartbeat. ``` If no trustworthy route exists, say completion auto-notify is unavailable. ## Launch forms Write the worker prompt to a temp file first. This avoids shell quoting bugs when the required notification block contains quotes or newlines. ```bash PROMPT=$(mktemp -t openclaw-worker-prompt.XXXXXX) cat >"$PROMPT" <<'EOF' Task. <notification block> EOF printf 'prompt file: %s\n' "$PROMPT" ``` Use `$PROMPT` when launching from the same shell/session. If using a separate tool call, substitute the printed path. Codex: ```bash bash pty:true background:true workdir:/path/repo command:"codex exec - < \"$PROMPT\"" ``` Claude Code: ```bash bash background:true workdir:/path/repo command:"claude --permission-mode bypassPermissions --print < \"$PROMPT\"" ``` OpenCode: ```bash bash pty:true background:true workdir:/path/repo command:"opencode run < \"$PROMPT\"" ``` ## Long issue-to-PR work 1. Create/reuse a GitHub issue as durable spec. 2. Include issue URL, repo, base branch, expected PR, proof, and notification route. 3. Tell worker to branch, implement, test, run review until no accepted actionable findings, open PR. 4. Return issue URL and `sessionId` immediately. 5. Monitor with `process`; cancel through Task Registry if mirrored there. ## Scratch Codex Codex needs a trusted git repo: ```bash SCRATCH=$(mktemp -d) git -C "$SCRATCH" init PROMPT=$(mktemp -t openclaw-worker-prompt.XXXXXX) cat >"$PROMPT" <<'EOF' Build X. <notification block> EOF printf 'prompt file: %s\n' "$PROMPT" bash pty:true background:true workdir:$SCRATCH command:"codex exec - < \"$PROMPT\"" ``` ## Process actions - `list`: running/recent sessions. - `poll`: status. - `log`: output. - `submit`: send input + Enter. - `write`: raw stdin. - `paste`: paste text. - `kill`: terminate. ## Status to user - Say what started, where, and `sessionId`. - Update only on milestone, worker question, error, user action needed, or finish. - If killed, say why.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.