cross-eval — Claude Code skill: what it does, how to install
Runs board memos and strategy briefs through Claude, Codex, and Gemini. Flags hidden blind spots before irreversible business choices.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install c-level-agents@claude-code-skillsWhat cross-eval does
The skill evaluates high-stakes business briefs by dispatching them to multiple AI models acting as independent C-suite reviewers. Each model identifies three top concerns, three supporting arguments, and casts a vote: APPROVE, REJECT, or DEFER. It probes your environment for OPENAI_API_KEY or codex CLI, and GEMINI_API_KEY or gemini CLI. Claude acts as the primary voice.
All outputs are synthesized into ~/.claude/cross-eval/YYYY-MM-DD-.md. The report lists tally votes, consensus flags where two or more models agree, isolated divergences, and open questions for the founder. Depending on consensus, it issues a GO, PAUSE, or STOP signal.
Install this when preparing term sheets, restructuring plans, or critical pivots. Single-model reviews often show systematic bias, so cross-model disagreement serves as an early warning signal.
What it helps with
- stress-test board memos before critical votes
- reconcile divergent risk evaluations across Claude, Codex, and Gemini
- review term sheets and pivot proposals for blind spots
- generate targeted questions for founders before irreversible commitments
Example prompts for the agent
- /c-level-agents:cross-eval memos/series-a-terms.md
- /c-level-agents:cross-eval strategy-pivot-brief.txt
- /c-level-agents:cross-eval docs/board-memo-q3.md
How to install cross-eval
1Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install c-level-agents@claude-code-skillsThis installs the whole c-level-agents plugin with all its skills
2Skills CLI (Vercel)
npx skills add alirezarezvani/claude-skills --skill cross-eval -a claude-code3Manually: put the files in place
~/.claude/skills/cross-eval/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cross-eval/
Manually: put the files in place
.agents/skills/cross-eval/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/cross-eval/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install alirezarezvani/claude-skills cross-eval2Manually: put the files in place
.github/skills/cross-eval/SKILL.mdPlatform CLI
gemini skills install https://github.com/alirezarezvani/claude-skills --path c-level-agents/skills/cross-evalManually: put the files in place
.devin/skills/cross-eval/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set349
The whole set →Similar
Questions about cross-eval
How do I install cross-eval in Claude Code?
Run /plugin marketplace add alirezarezvani/claude-skills and install the package with /plugin install c-level-agents@claude-code-skills. Alternatively, run npx skills add alirezarezvani/claude-skills --skill cross-eval -a claude-code.
What does cross-eval do?
It runs a strategic memo through Claude, Codex, and Gemini simultaneously, comparing their feedback and tallying votes to provide a clear GO, PAUSE, or STOP recommendation.
What happens if OpenAI or Gemini keys are missing?
The skill falls back to adversarial mode using Claude alone. It performs three separate passes using distinct system prompts: standard reviewer, devil's advocate, and steelman.
Source text
SKILL.md · MIT
---
name: "cross-eval"
description: "/c-level-agents:cross-eval [memo] — Multi-model consensus on a board memo or strategy brief. Claude + Codex + Gemini cross-review with graceful degradation. Use when a high-stakes memo needs an independent sanity check before the boardroom — e.g. a bet-the-company pivot or fundraise terms."
---
# /c-level-agents:cross-eval — Multi-Model Consensus
**Command:** `/c-level-agents:cross-eval <memo-or-brief>`
Runs the same memo through multiple model providers and reconciles divergences. Use for **high-stakes, irreversible decisions** where single-model bias is too costly: M&A, major fundraises, layoffs, strategic pivots, regulatory commitments.
Adapted from gstack's `/codex` cross-review pattern, generalized to **business memos** instead of code PRs.
## When to Run
- Before signing a term sheet
- Before announcing a layoff
- Before committing to a regulated market
- Before any decision where reversing costs > 6 months of company time
- When the boardroom vote was split or had a CRITICAL dissent
## Models Used (graceful degradation)
The command tries to invoke each available model in order:
1. **Claude** (primary, always available) — the boardroom's native voice
2. **Codex / OpenAI** (if `OPENAI_API_KEY` or `codex` CLI available)
3. **Gemini** (if `GEMINI_API_KEY` or `gemini` CLI available)
If only Claude is available, the command runs **Claude-only with adversarial mode** — same model, different prompt seeds — and clearly labels the output as single-model.
## Workflow
1. Read the memo / brief
2. Probe environment for available model CLIs / API keys
3. For each available model:
- Send the memo with this prompt prefix:
> "You are an independent C-suite reviewer. The following is a board memo from another company's boardroom. Identify the top 3 concerns, the top 3 supports, and your vote (APPROVE / REJECT / DEFER). Do not deferentially agree — assume the memo's reasoning is flawed until proven otherwise."
4. Collect three independent reviews
5. Reconcile: where do they agree? Where do they diverge?
6. Surface the divergences as questions for the founder
## Output Format
Saved to `~/.claude/cross-eval/YYYY-MM-DD-<slug>.md`:
```markdown
# Cross-Eval: <memo title>
**Date:** YYYY-MM-DD
**Memo reviewed:** <link>
**Models invoked:** Claude / Codex / Gemini (or noted fallbacks)
## Vote Tally
| Model | Vote | Confidence |
|---|---|---|
| Claude | APPROVE | High |
| Codex | DEFER | Med |
| Gemini | APPROVE | Low |
## Consensus Concerns (≥2 models flagged)
1. <concern> — flagged by Claude + Codex
2. <concern> — flagged by all 3
## Divergent Concerns (1 model flagged)
- <Codex only:> <concern> — worth a second look
- <Gemini only:> <concern> — likely noise, but check
## Consensus Supports (≥2 models endorsed)
1. <support>
2. <support>
## Recommendation
- 🟢 GO if 2+ models APPROVE and no CRITICAL concerns from any model
- 🟡 PAUSE if any model is DEFER or any concern is CRITICAL
- 🔴 STOP if 2+ models REJECT
## Open Questions for Founder
1. <question raised by divergence>
2. <question raised by divergence>
```
## Why This Matters
Single-model recommendations have systematic biases. Claude trends helpful and may under-weight risk. Codex (OpenAI) trends more cautious on emerging-market and regulatory topics. Gemini trends more cautious on technical scale claims. Disagreement is signal, not noise.
This is the **safety net before irreversibility** — not a replacement for outside counsel or a real board.
## Graceful Degradation
If only Claude is available:
```markdown
**Models available:** Claude only
**Mode:** ADVERSARIAL — running 3 independent Claude passes with different system prompts:
1. Standard reviewer
2. Devil's advocate (must find 3 critical concerns)
3. Steelman (must find 3 strongest reasons to approve)
This is weaker than true multi-model. Treat the result as suggestive, not conclusive.
```
## Routing
- `/c-level-agents:decide` — if consensus is GO
- `/c-level-agents:freeze` — if consensus is PAUSE
- `/c-level-agents:boardroom` (re-run) — if consensus is STOP
## Related
- Skills: [`board-meeting`](${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/board-meeting/SKILL.md), [`executive-mentor`](../../../c-level-advisor/executive-mentor/)
- Inspiration: gstack's `/codex` cross-review pattern (adapted to business memos)
---
**Version:** 1.0.0
© Alireza Rezvani · MIT · alirezarezvani/claude-skills