OpenClaw Claude Codex Workflow

在 OpenClaw 中需要 Claude Code 负责编排/评审、Codex 实现后端、Gemini 实现前端的多模型流水线时启用；尤其适用于需要 OPSX/spec 对齐、分阶段 artifacts、以及 claude→codex→gemini→claude 闭环交付的任务。

This skill appears to implement the multi-model orchestration it advertises, but its metadata fails to list the real runtime requirements. Before installing or running it: - Do not run it in a production or privileged repository until you confirm its behavior. Prefer a disposable clone. - Confirm you trust the claude/codex/gemini CLIs the script will invoke; those CLIs will receive prompts and context files and may execute commands. - Provide API keys only if you understand the CLIs' security model; avoid placing secrets in global shell profiles if possible (use a dedicated process env or a secrets manager). - Change the workspace from /root/.openclaw/workspace to a non-root workspace path to avoid requiring elevated privileges. - Use --dry-run and review generated .claude/plan.md and any commands before letting the orchestrator execute them (set DRY_RUN=1 or pass --dry-run). - Ask the publisher to update registry metadata to list required binaries and required environment variables (CLAUDE_API_KEY, CODEX_API_KEY, GOOGLE_API_KEY, and the required CLIs) so you can perform a complete risk assessment. If you want, I can extract a checklist of the exact commands and env vars the skill expects so you can validate them locally before running.

Type: OpenClaw Skill Name: openclaw-claude-codex-workflow Version: 0.1.0 The skill bundle provides a legitimate orchestration framework for a multi-model development pipeline involving Claude, Codex, and Gemini. The primary logic resides in `scripts/ccg_orchestrator.sh`, which safely uses Bash arrays to wrap official CLI commands without evidence of shell injection or unauthorized data exfiltration. While the workflow requires sensitive API keys (e.g., `CLAUDE_API_KEY`, `GOOGLE_API_KEY`), the instructions in `SKILL.md` and the supporting documentation in the `references/` directory are transparent, align with the stated purpose, and include safety constraints such as dry-run modes and git-cleanliness checks.