skills/oracle-codex/SKILL.md
This skill should be used when the user asks to consult Codex/GPT for planning or code review, or wants a second opinion on code. Trigger phrases include "ask Codex", "consult Codex", "second opinion on code", "consult the oracle". NOT for implementation tasks.
npx skillsauth add paulrberg/agent-skills oracle-codexInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use OpenAI Codex CLI as a read-only oracle — planning, review, and analysis only. Codex provides its perspective; you synthesize and present results to the user.
Sandbox is always read-only. Codex must never implement changes.
Parse $ARGUMENTS for:
--reasoning <level> — override reasoning effort (low, medium, high, xhigh). Optional; default is xhigh.Run the check script before any Codex invocation:
scripts/check-codex.sh
If it exits non-zero, display the error and stop. Use the wrapper for all codex exec calls:
scripts/run-codex-exec.sh
| Setting | Default | Override |
| --------- | ----------- | ------------------------------------------------ |
| Model | gpt-5.5 | Allowlist only (see references/codex-flags.md) |
| Reasoning | xhigh | --reasoning <level> or user prose |
| Sandbox | read-only | Not overridable |
| Complexity | Effort | Timeout | Criteria |
| ---------- | -------- | -------- | ------------------------------------ |
| Simple | low | 300000ms | <3 files, quick question |
| Moderate | medium | 300000ms | 3–10 files, focused analysis |
| Complex | high | 600000ms | Multi-module, architectural thinking |
| Maximum | xhigh | 600000ms | Full codebase, critical decisions |
For xhigh tasks that may exceed 10 minutes, use run_in_background: true on the Bash tool and set CODEX_OUTPUT so you can read the output later.
See references/codex-flags.md for full flag documentation.
$ARGUMENTS for query and --reasoningscripts/check-codex.sh — abort on failurexhigh reasoning effort unless --reasoning overrides itBuild a focused prompt from the user's query and any relevant context (diffs, file contents, prior conversation). Keep it direct — state what you want Codex to analyze and what kind of output you need. Do not implement; request analysis and recommendations only.
Invoke via the wrapper with HEREDOC. Set the Bash tool timeout per the reasoning effort table above.
EFFORT="<effort>" \
CODEX_OUTPUT="/tmp/codex-${RANDOM}${RANDOM}.txt" \
scripts/run-codex-exec.sh <<'EOF'
[constructed prompt]
EOF
For xhigh, consider run_in_background: true on the Bash tool call, then read CODEX_OUTPUT when done.
Read the output file and present with attribution:
## Codex Analysis
[Codex output — summarize if >200 lines]
---
Model: gpt-5.5 | Reasoning: [effort level]
Synthesize key insights and actionable items for the user.
testing
Use ONLY to check or update the project-scoped agent skills installed under .agents/skills so they match the current state of the repo. Do not trigger for creating, finding, or installing skills, or for README/AGENTS.md updates.
testing
Use when CSV, TSV, or Excel (.xlsx) is the primary input/output: inspect, clean, transform, dedupe, merge, validate, convert, recalc formulas, or create/fix spreadsheets. Do not trigger when tabular data is incidental.
development
This skill should be used when the user asks to consult Codex/GPT for planning or code review, or wants a second opinion on code. Trigger phrases include "ask Codex", "consult Codex", "second opinion on code", "consult the oracle". NOT for implementation tasks.
databases
This skill should be used when the user asks to create a monochrome technical diagram, schematic, or systems/architecture diagram in black-and-white line-art style. Trigger phrases include "create a diagram", "monochrome diagram", "systems diagram", "draw a schematic".