codex-consult

Consult OpenAI Codex CLI for second opinions on errors, architecture, and unfamiliar APIs.

3|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/waki285/dotfiles --skill codex-consult-waki285
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-consult
Source: https://github.com/waki285/dotfiles/tree/main/dot_claude/skills/codex-consult
Command: npx skills add https://github.com/waki285/dotfiles --skill codex-consult-waki285

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you are stuck on an obscure error, facing a difficult architectural trade-off, or working with an unfamiliar library, a single AI perspective can miss blind spots. This Skill runs OpenAI Codex CLI (codex exec) to obtain an independent second opinion and merges it with the primary analysis. ## Core Features & Use Cases - Second-Opinion Consultation: Runs codex exec with a structured prompt (context, problem, code, question) and saves the response to ~/.claude/second-opinions/. - Auto-Trigger Guidelines: Defines when to proactively consult Codex, such as after 2+ failed debugging attempts, architectural decisions, or plan-mode validation. - Fallback Handling: Retries without the ym profile if the primary provider errors, and enforces a 10-minute timeout for long-running queries. - Use Case: After failing twice to fix a Rust lifetime error, ask the assistant to consult Codex; it runs the CLI, reads the saved response, and presents a combined recommendation highlighting where the two perspectives agree or differ. ## Quick Start Ask the assistant to consult Codex about your current error or design decision, for example by saying "ask Codex for a second opinion on this architecture".

Frequently Asked Questions about codex-consult

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a second opinion from Codex CLI on a coding problem?▼

Ask the assistant to consult Codex, and it runs codex exec with a structured prompt containing context, problem, code snippet, and question. The response is saved to ~/.claude/second-opinions/ and synthesized with the assistant's own analysis.

When should I consult Codex instead of searching the web?▼

Consult Codex when stuck on an obscure error after 2+ failed attempts, facing architectural trade-offs, or working with a library not covered by Context7. Skip it when the answer is straightforward or web search already suffices.

What happens if the codex exec command fails with the ym profile?▼

The Skill retries the same consultation without the -p ym flag as a fallback. This handles cases where the voids provider errors while still returning a Codex response.

Why does codex exec need a long timeout?▼

Codex can take up to 10 minutes for complex queries, so the Bash tool timeout is set to 600000 milliseconds. Shorter timeouts may cut off legitimate long-running consultations.

What information should never be included in a Codex consultation prompt?▼

Never include API keys, tokens, passwords, personal identifiable information, or proprietary business logic unless the user explicitly permits it. Prompts should summarize code rather than dump entire files.