Best for
- Backend/analysis + frontend/UI work in one request
- Code review from multiple perspectives (architecture + design/UX)
- Cross-validation where Codex and Antigravity/Gemini may disagree
Yeachan-Heo/oh-my-claudecode/skills/ccg/SKILL.md
Claude-Codex-Gemini tri-model orchestration via /ask codex + /ask antigravity (or gemini), then Claude synthesizes results
Decision brief
CCG routes through the canonical /ask skill (/ask codex + /ask antigravity), then Claude synthesizes both outputs into one answer.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Declared | Source record | Install path and trigger |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill "skills/ccg"Inspect the Agent Skill "ccg" from https://github.com/Yeachan-Heo/oh-my-claudecode/blob/41a4c0f77144c5beb5f5f000a89cff379c680606/skills/ccg/SKILL.md at commit 41a4c0f77144c5beb5f5f000a89cff379c680606. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Backend/analysis + frontend/UI work in one request
Codex CLI: npm install -g @openai/codex (or @openai/codex)
Review the “How It Works” section in the pinned source before continuing.
When invoked, Claude MUST follow this workflow:
Permission review
The documentation asks the agent to run terminal commands or scripts.
### 2. Invoke advisors via CLIEvidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 87/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 38,325 | Source | Repository attention, not individual Skill quality |
| Compatibility | 1 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
CCG routes through the canonical /ask skill (/ask codex + /ask antigravity), then Claude synthesizes both outputs into one answer.
Use this when you want parallel external perspectives without launching tmux team workers.
npm install -g @openai/codex (or @openai/codex)agy binary
per the official Antigravity instructions (inspect any
installer before running it). Verify: agy --versionnpm install -g @google/gemini-cliomc ask command available1. Claude decomposes the request into two advisor prompts:
- Codex prompt (analysis/architecture/backend)
- Antigravity prompt (UX/design/docs/alternatives) — use gemini for enterprise
2. Claude runs via CLI (skill nesting not supported):
- `omc ask codex "<codex prompt>"`
- `omc ask antigravity "<antigravity prompt>"`
(or `omc ask gemini "<gemini prompt>"` for enterprise)
3. Artifacts are written under `.omc/artifacts/ask/`
4. Claude synthesizes both outputs into one final response
When invoked, Claude MUST follow this workflow:
Split the user request into:
Note: Skill nesting (invoking a skill from within an active skill) is not supported in Claude Code. Always use the direct CLI path via Bash tool.
Run both advisors (use antigravity or gemini depending on your setup):
omc ask codex "<codex prompt>"
omc ask antigravity "<antigravity prompt>"
Enterprise fallback:
omc ask gemini "<gemini prompt>"
Read latest ask artifacts from:
.omc/artifacts/ask/codex-*.md
.omc/artifacts/ask/antigravity-*.md
.omc/artifacts/ask/gemini-*.md
Return one unified answer with:
If one provider is unavailable:
If both unavailable:
/oh-my-claudecode:ccg <task description>
Example:
/oh-my-claudecode:ccg Review this PR - architecture/security via Codex and UX/readability via Antigravity
Alternatives
wanshuiyin/Auto-claude-code-research-in-sleep
Two-thread adversarial review: a fresh reviewer constructs the strongest 200-word rejection memo, then a second fresh reviewer defends the paper point-by-point and surfaces still-unresolved critical issues. Use when user says "kill argument", "adversarial review", "hostile review", "rebuttal preparation", "reviewer-2 simulation", or before submitting a theory paper that has already passed standard review rounds.
wanshuiyin/Auto-claude-code-research-in-sleep
Two-thread adversarial review: a fresh reviewer constructs the strongest 200-word rejection memo, then a second fresh reviewer defends the paper point-by-point and surfaces still-unresolved critical issues. Use when user says "kill argument", "adversarial review", "hostile review", "rebuttal preparation", "reviewer-2 simulation", or before submitting a theory paper that has already passed standard review rounds.
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations tasks; the detail page covers purpose, installation, and practical steps.
cameronfreer/lean4-skills
Use when editing .lean files, debugging Lean 4 builds (type mismatch, sorry, failed to synthesize instance, axiom warnings, lake build errors), searching mathlib for lemmas, formalizing mathematics in Lean, finding a counterexample to, refuting, or disproving a Lean statement, or learning Lean 4 concepts. Also trigger when the user asks for help with Lean 4, mathlib, or lakefile. Do NOT trigger for Coq/Rocq, Agda, Isabelle, HOL4, Mizar, Idris, Megalodon, or other non-Lean theorem provers.