mcp-codex_skill

Overview

This skill integrates the codex-cli MCP shell tool with Claude Code to execute shell commands, run builds, and perform file operations as part of skill-driven workflows. It manages skill loading, command execution via codex-cli, and structured result processing to decide next steps. Use it when you need reliable, auditable shell execution coordinated by Claude.

How this skill works

Claude reads and interprets the relevant skill files, creates a concrete work plan, then calls the codex-cli shell tool to run commands in the specified absolute workdir. codex-cli returns structured results (exit_code, output, duration, timed_out) which Claude analyzes to determine success, retry, or error-handling actions. The skill enforces workdir specification, exit code checks, and retry limits.

When to use it

• Running builds, tests, or deployment scripts
• Reading, writing, or manipulating project files and directories
• Checking system environment and dependencies
• Automating skill-based workflows that require shell execution
• Orchestrating multi-step CI tasks where Claude plans and codex-cli runs commands

Best practices

• Always load and let Claude interpret skill files before invoking codex-cli
• Provide an absolute workdir for every codex-cli call
• Check exit_code and treat 0 as success; analyze non-zero codes and timeouts
• Limit retries to avoid infinite loops (max 3 attempts recommended)
• Avoid passing prompts or expecting AI responses from codex-cli; it only runs shell commands

Example use cases

• Initialize a project from an infrastructure skill: generate docker-compose.yml, run docker-compose up -d, then verify with docker-compose ps
• Perform code review automation: list changed files, read them, then run npm run lint and npm run test via codex-cli
• Staging deployment: build with npm run build, run tests, and execute a deploy script in the target workdir
• Environment checks: run dependency installers and diagnostic commands to confirm system readiness