Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/consult-codex
Multi-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving.
Passed 13 of 17 test cases with the skill, and 6 of 17 without it.
and 7 more in the full report
9 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We completed turn 1 of a Codex consultation and obtained session ID `9b1deb4d-3b7d-4bad-9bdd-2b0d7b3d0011`. We want to run a follow-up query using `codex exec resume 9b1deb4d-3b7d-4bad-9bdd-2b0d7b3d0011`. Should we pass `-s workspace-write` on the `resume` command?
| Checked | Without skill | With skill |
|---|---|---|
| Omits the `-s` sandbox flag when executing `codex exec resume`. | Missed | Passed |
The instructions your model reads when the skill loads.
Multi-turn consultation with Codex CLI. Maintains a conversation across multiple turns using session persistence, unlike single-shot /codex-exec.
Identify the 2-5 files most relevant to the problem. Formulate a clear, specific question. Include what has been tried and relevant constraints.
Run codex exec with -o to capture the response cleanly. Default to -s read-only for safety. Use -s workspace-write when the consultation requires running code or reading files outside the workspace.
All codex Bash calls require dangerouslyDisableSandbox: true (network access to OpenAI API). Use .turbo/ as the temp directory — it is in the working directory (sandbox-writable), gitignored, and avoids $TMPDIR path mismatches between sandbox and non-sandbox mode.
Non-piped codex exec invocations require < /dev/null to avoid hanging on stdin. Codex reads from stdin whenever stdin is non-TTY, and in subprocess contexts the harness leaves stdin connected to a pipe that never EOFs — codex blocks forever, printing only Reading additional input from stdin.... The piped form (cat file | codex exec "...") is safe — cat closes the pipe after the file.
Generate a random session tag at the start to keep files unique for parallel use, and print the absolute path prefix it produces:
CODEX_TAG=$(head -c 4 /dev/urandom | xxd -p) && mkdir -p "$PWD/.turbo/codex" && echo "$PWD/.turbo/codex/$CODEX_TAG"
Substitute the printed value for <prefix> in every later command of this consultation. Shell variables do not survive between Bash tool calls, and an earlier cd in a compound command leaves the session in a different directory, so a relative path resolves against that directory instead.
codex exec -s read-only -o "<prefix>.txt" "<question>" < /dev/null
Structure the question using XML tags for clearer Codex responses:
<task>: The concrete question and relevant context.<compact_output_contract>: Desired output shape and brevity requirements.<structured_output_contract>: Same purpose but for structured/schema responses.<grounding_rules>: When claims must be evidence-based (review, research, root-cause analysis).<dig_deeper_nudge>: Push past surface-level findings to check for second-order failures.<verification_loop>: When correctness matters — ask Codex to verify before finalizing.<merit_only>: When a recommendation is wanted, bar answers that appeal to scope.<style_constraints>: When the answer must follow a house style, name the shapes that style forbids.test cases passed, vs 6 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.