AlphaMoatによると、2026-09時点でcoding-agentのダウンロード数は2,418、スター数は0で、AIスキル全体5,078件中4,167位、開発では577件中515位です。
| プラットフォーム | インストール数 | ダウンロード数 | スター数 | コメント |
|---|---|---|---|---|
| ClawHub ↗ | 48 | 1639 | - | - |
| SkillHub ↗ | 590 | 2418 | - | — |
プラットフォームごとに集計方法と集計時点が異なります。
開発、レビュー、整理の作業を背景の処理として Codex、Claude Code、Pi などのエージェントに渡し、各クライアントの性質に合わせて実行の方式を選びます。Claude Code は仮想端末を要さず、Codex、Pi、OpenCode は必要とします。利用者が特定のエージェントを指名したらそのまま使い、黙って差し替えません。任せた後に自分でパッチを書くこともせず、PR のレビューは一時のディレクトリで行い、作業区や稼働中の案件の場所では行いません。 承認やサンドボックスを迂回するモードを使う手順があり、委任先が依存関係を導入したり、commit、push、PR コメントを行ったりする場合があります。認証情報を絞った使い捨て clone や container を優先し、実行予定のコマンドと出力を確認してください。明示的に必要な場合を除き、通常の承認を有効にします。
資料公開日 2026-10-27
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-09 | 2418 | — | - |
| 2026-08 | 2013 | +7.9% | - |
| 2026-07 | 1866 | — | - |
| 2026-05 | 1536 | — | - |
| 2026-03 | 1163 | — | - |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
--- name: coding-agent description: 'Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (use sessions_spawn with runtime:"acp"), or any work in the OpenClaw workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.' --- # Coding Agent Use **bash** (with optional background mode) for all coding agent work. ## PTY: Codex/Pi/OpenCode yes, Claude Code no
For **Codex, Pi, and OpenCode**, PTY is required (interactive terminal apps): ```bash # Codex/Pi/OpenCode bash pty:true command:"codex exec 'Your prompt'" ``` For **Claude Code** (`claude` CLI), use `--print --permission-mode bypassPermissions` instead. `--print` mode keeps full tool access and avoids interactive confirmation: ```bash # Claude Code (no PTY needed) cd /path/to/project && claude --permission-mode bypassPermissions --print 'Your task' # Background execution: use background:true on the exec tool ``` ### Bash Tool Parameters | Parameter | Type | Description | | ------------ | ------- | --------------------------------------------------------------------------- | | `command` | string | The shell command to run | | `pty` | boolean | Allocates a pseudo-terminal for interactive CLIs (required for Codex/Pi) | | `workdir` | string | Working directory (agent sees only this folder's context) | | `background` | boolean | Run in background, returns sessionId for monitoring | | `timeout` | number | Timeout in seconds (kills process on expiry) | | `elevated` | boolean | Run on host instead of sandbox (if allowed) | ### Process Tool Actions | Action | Description | | ----------- | ---------------------------------------------------- | | `list` | List all running/recent sessions | | `poll` | Check if session is still running | | `log` | Get session output (with optional offset/limit) | | `write` | Send raw data to stdin | | `submit` | Send data + newline (like typing and pressing Enter) | | `send-keys` | Send key tokens or hex bytes | | `paste` | Paste text (with optional bracketed mode) | | `kill` | Terminate the session | --- ## Quick Start: One-Shot Tasks ```bash # Quick chat (Codex needs a git repo!) SCRATCH=$(mktemp -d) && cd $SCRATCH && git init && codex exec "Your prompt here" # In a real project bash pty:true workdir:~/Projects/myproject command:"codex exec 'Add error handling to the API calls'" ``` **Why git init?** Codex refuses to run outside a trusted git directory. A temp repo solves this for scratch work. --- ## The Pattern: workdir + background + pty For longer tasks, use background mode: ```bash # Start agent in target directory bash pty:true workdir:~/project background:true command:"codex exec --full-auto 'Build a snake game'" # Returns sessionId for tracking # Monitor progress process action:log sessionId:XXX # Check if done process action:poll sessionId:XXX # Send input (if agent asks a question) process action:submit sessionId:XXX data:"yes" # Kill if needed process action:kill sessionId:XXX ``` **Why workdir matters:** Agent wakes up in a focused directory and doesn't wander off reading unrelated files. --- ## Codex CLI Preferred agent for single tasks. Pass the requirements clearly — Codex handles execution well. ### Flags | Flag | Effect | | --------------- | -------------------------------------------------- | | `exec "prompt"` | One-shot execution, exits when done | | `--full-auto` | Sandboxed but auto-approves in workspace | | `--yolo` | No sandbox, no approvals (fastest, most dangerous) | ### Building/Creating ```bash # Quick one-shot bash pty:true workdir:~/project command:"codex exec --full-auto 'Build a dark mode toggle'" # Background for longer work bash pty:true workdir:~/project background:true command:"codex --yolo 'Refactor the auth module'" ``` ### Reviewing PRs **Never review PRs in the OpenClaw workspace or the live project folder.** Clone to temp or use git worktree. ```bash # Clone to temp for safe review REVIEW_DIR=$(mktemp -d) git clone https://github.com/user/repo.git $REVIEW_DIR cd $REVIEW_DIR && gh pr checkout 130 bash pty:true workdir:$REVIEW_DIR command:"codex review --base origin/main" # Clean up after: trash $REVIEW_DIR # Or use git worktree (keeps main intact) git worktree add /tmp/pr-130-review pr-130-branch bash pty:true workdir:/tmp/pr-130-review command:"codex review --base main" ``` ### Batch PR Reviews (parallel) ```bash # Fetch all PR refs git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*' # One Codex per PR bash pty:true workdir:~/project background:true command:"codex exec 'Review PR #86. git diff origin/main...origin/pr/86'" bash pty:true workdir:~/project background:true command:"codex exec 'Review PR #87. git diff origin/main...origin/pr/87'" # Monitor all process action:list # Post results gh pr comment <PR#> --body "<review content>" ``` --- ## OpenCode ```bash bash pty:true workdir:~/project command:"opencode run 'Your task'" ``` --- ## Claude Code No PTY required. Use when explicitly requested or for tasks that benefit from tighter integration. ```bash # Foreground bash workdir:~/project command:"claude --permission-mode bypassPermissions --print 'Your task'" # Background bash workdir:~/project background:true command:"claude --permission-mode bypassPermissions --print 'Your task'" ``` --- ## Pi ```bash bash pty:true workdir:~/project command:"pi 'Your task'" # Non-interactive mode bash pty:true command:"pi -p 'Summarize src/'" # Different provider/model bash pty:true command:"pi --provider openai --model gpt-4o-mini -p 'Your task'" ``` --- ## Parallel Issue Fixing with git worktrees ```bash # Create worktrees for each issue git worktree add -b fix/issue-78 /tmp/issue-78 main git worktree add -b fix/issue-99 /tmp/issue-99 main # Launch agents in parallel bash pty:true workdir:/tmp/issue-78 background:true command:"pnpm install && codex --yolo 'Fix issue #78: <description>. Commit and push.'" bash pty:true workdir:/tmp/issue-99 background:true command:"pnpm install && codex --yolo 'Fix issue #99. Implement only the in-scope edits and commit after review.'" # Monitor process action:list process action:log sessionId:XXX # Create PRs cd /tmp/issue-78 && git push -u origin fix/issue-78 gh pr create --repo user/repo --head fix/issue-78 --title "fix: ..." --body "..." # Cleanup git worktree remove /tmp/issue-78 git worktree remove /tmp/issue-99 ``` --- ## Rules 1. **Right execution mode per agent**: Claude Code uses `--print --permission-mode bypassPermissions` (no PTY); Codex/Pi/OpenCode use `pty:true` 2. **Respect tool choice** — if the user asks for a specific agent, use it; don't silently substitute 3. **Orchestrator mode** — do not hand-code patches yourself when the task is delegated to an agent 4. **Be patient** — don't kill sessions just because they're slow; check with `process:log` first 5. **Parallel is fine** — run multiple agents at once for batch work 6. **Never start agents in the OpenClaw workspace** — they'll read soul docs and get confused about who's in charge 7. **Never checkout branches in the live OpenClaw project folder** — that's the running instance --- ## Progress Updates Keep the user in the loop without flooding them. - One short message when you start: what's running and where - Update again only when something changes: milestone done, agent needs input, error, or finished - If you kill a session, say so immediately and explain why --- ## Auto-Notify on Completion For long-running background tasks, append a wake trigger to the prompt so Miki gets notified immediately when the agent finishes: ``` ... your task here. When completely finished, run: openclaw system event --text "Done: [brief summary]" --mode now ``` **Example:** ```bash bash pty:true workdir:~/project background:true command:"codex --yolo exec 'Build a REST API for todos. When completely finished, run: openclaw system event --text \"Done: Built todos REST API\" --mode now'" ``` --- ## Notes - **PTY is essential for Codex/Pi/OpenCode** — without it, output breaks or the agent hangs - **Git repo required for Codex** — use `mktemp -d && git init` for scratch work - **`exec` is clean** — `codex exec "prompt"` runs and exits, perfect for one-shots - **`submit` vs `write`** — `submit` sends input + Enter; `write` sends raw data without newline
gh コマンドラインで GitHub の PR チェック、ワークフロー実行、API 照会を扱うスキルです。
16 の検索エンジンをまとめて使え、API キーが不要な検索スキルです。
コマンドラインから MCP サーバーとツールを一覧、設定、認証、呼び出しします。
Generate valid Mermaid diagrams like flowcharts, sequence diagrams, mind maps, ER diagrams, or user journeys from text or product descriptions.
管理された OAuth で YouTube Data API に接続し、動画検索とチャンネル管理を行います。
管理された OAuth 接続で GitHub REST API にアクセスします。
計画、実装、検証、テストをカバーするコーディング作業のスキルです。
Docker の基本コマンドとコンテナ作業をまとめたスキルです。
データ月:2026-09 · ダウンロード数、スター数、インストール数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。