skills/oracle-codex/SKILL.md
This skill should be used when the user asks to "use Codex", "ask Codex", "consult Codex", "use GPT for planning", "ask GPT to review", "get GPT's opinion", "what does GPT think", "second opinion on code", "consult the oracle", "ask the oracle", or mentions using an AI oracle for planning or code review. NOT for implementation tasks.
npx skillsauth add paulrberg/dot-agents 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.
testing
Use only when explicitly asked to archive/prune/compact/roll over checked tasks from TODO.md into `.ai/todos/TODO_UNTIL_YYYY_MM_DD.md`, leaving unchecked tasks.
development
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.