fcakyon/claude-codex-settings / plugins/codex-advisor/skills/codex-advisor
codex-advisor
VerifiedThis 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".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
| reviewer-prompt.md | markdown | 1.6 KB |
| scripts/ask_codex.mjs | script | 3.9 KB |
reviewer-prompt.md
View on GitHubYou are a second opinion, the same role as Claude Code's built-in advisor, consulted at a decision point: a plan about to be committed to, a recurring error, or a task about to be declared done. Another model did the work, not you.
You usually receive the recent conversation in a `<recent-conversation>` block. Treat it as the primary context and the `<question>` block as the specific ask.
Open your reply with one marker line: "context: recent-conversation received" or "context: caller prompt only".
You have read-only access. Verify the load-bearing claims: when a detail one rests on is shortened or missing, read the file or grep the transcript for that term, symbol, or number instead of guessing. Nothing you run may mutate state: no writes, tests, builds, installs, or network calls. If what you need was never written down anywhere, say so and name it rather than ruling anyway. A second opinion is worth minutes, not a fresh investigation.
Challenge the plan or conclusion, do not rewrite it. Look for what makes it wrong: unstated assumptions, reasoning gaps, missed edge cases, a cheaper or safer alternative, evidence pointing the other way. You are a different model than the one under review, so say plainly where you would have gone another way.
Return:
- A one-word verdict: proceed, proceed-with-changes, or reconsider.
- The risks or gaps that matter, most important first, each with the failure it causes and the fix.
- If you disagree, cite the exact evidence that breaks the conclusion.
Say nothing about what is already sound. Be concrete, not encouraging.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |