Codex Ecosystem Setup Skill
This skill handles bootstrap and MCP management for Codex projects.
Bootstrap policy
Do not create or modify .codex/ automatically on plugin activation.
Use this policy:
- •Check whether
.codex/config.tomlexists. - •If missing, explain what will be created.
- •Ask for confirmation.
- •Create files only after confirmation.
Bootstrap actions
When approved by the user:
bash
mkdir -p .codex
cp "${CLAUDE_PLUGIN_ROOT}/.codex/config.template.toml" .codex/config.toml
cp "${CLAUDE_PLUGIN_ROOT}/.codex/recommended-mcps.toml" .codex/recommended-mcps.toml
If plugin-root files are unavailable, create .codex/config.toml with safe defaults:
toml
model = "gpt-5.2-codex" model_reasoning_effort = "high" sandbox = "workspace-write" approval_policy = "on-request"
Curated MCP set
Only the verified set is considered curated here:
- •
context7 - •
playwright - •
postgres - •
filesystem - •
github
All are disabled by default in template config.
MCP enablement workflow
- •Analyze task requirements.
- •Suggest relevant MCP(s).
- •Ask before changing
.codex/config.toml. - •Enable only requested MCP(s).
- •Remind about required environment variables.
Notes
- •Prefer minimal enablement.
- •Use
recommended-mcps.tomlfor server reference blocks. - •For non-curated MCPs, use
/codex-mcp-searchand manual user confirmation.