mcpbeat

Codex Advisor

fcakyon/codex-advisor

This skill should be used when the user asks for a "GPT second opinion", wants a "cross-model review", needs to "check a plan before committing", wants another view after repeated failures, or explicitly invokes "codex-advisor".

2k tokens
context cost
the whole folder, loaded on every use
3
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
955
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/fcakyon/claude-codex-settings --skill codex-advisor

The instruction itself

4 sections, as written by the author

Codex Advisor

Get a focused second opinion from GPT through the Codex CLI, without handing the

work over to it.

Route by tool

  • In Claude Code, delegate to the native codex-advisor agent. It receives the

recent conversation automatically, so do not paste the history yourself.

  • Elsewhere, run this exact shape from this skill's directory so the request

reaches standard input:

   node scripts/ask_codex.mjs <<'REVIEW'
   the review request
   REVIEW

State the decision, the evidence behind it, and any constraint that changes the

verdict. Name the paths that matter: the reviewer has read-only access and

checks load-bearing claims itself.

Return the answer without rewriting it. If codex is missing or unauthenticated,

surface the error and ask the user to install it or sign in. Never review in its

place.

Reviewer

Pinned to gpt-5.6-sol at medium reasoning effort. Inside Codex that may be the

model already doing the work, so set CODEX_ADVISOR_MODEL to a different one.

Weighing the answer

Give the verdict serious weight. If a step it recommends fails when tried, or a

file contradicts a specific claim, surface the conflict instead of following the

review blindly.

How to use it

Copy the folder

Take fcakyon/codex-advisor from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.