원클릭으로
competition
Agents work in parallel on the same task; judges evaluate and select the winner.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Agents work in parallel on the same task; judges evaluate and select the winner.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Coordination guidance for the narrow case of multiple desktop-backed agents active concurrently in the same desktop-backed coordination context. Use ONLY when two or more desktop peers are running at the same time; normal CLI agents and single desktop peers should ignore this skill. Read this BEFORE concurrent desktop-to-desktop handoffs to keep sender labels unique, identity routing cooperative, and material handoffs proven.
Mandatory near-live communication discipline ("the Law") for the two DESKTOP agents (claude-desktop and codex-desktop) on the Interlateral mesh. Read this BEFORE any desktop-to-desktop peer communication, peer-superset, ready-rock-quartet, sprint-overseer, gate-keeper, sprint handoff, or substantial delegation. It forces correct live comms and prevents the recurring failure modes. Normal CLI agents, Warp/terminal peers, and single non-desktop workflows should ignore this skill and use the ordinary repo protocols.
Join the Antigravity CLI (agy, Gemini 3.5 Flash) to the Interlateral mesh as a native CLI peer with its own tmux session, identity stamping, and the agy.js send helper. Use this instead of the Antigravity desktop-app CDP path.
Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.
Initialize the standard Interlateral two-agent CLI mesh from a bootstrap agent by running me.sh, launching Claude Opus 4.7 plus Codex 5.5, proving live ACK, and waiting for "Reporting for Duty!". The bootstrap agent is not part of the mesh.
Operate or troubleshoot Interlateral CLI mesh transport: tmux socket discovery, direct-send helpers, comms.md ledger, identity stamping, idle checks, ACK proof, and safe prompt injection. This is comms mechanics only, not a collaboration workflow.
| name | competition |
| description | Agents work in parallel on the same task; judges evaluate and select the winner. |
| metadata | {"owner":"interlateral","version":"1.0","weight":"heavy"} |
| compatibility | Three or more explicitly selected agents. Default to Claude Code + Codex peers; Gemini and Antigravity are opt-in only when the human explicitly selects them. |
Multiple agents independently create solutions to the same challenge. Judges evaluate the submissions blind (if possible) and select a winner. Encourages diverse approaches and best-idea-wins culture.
Use mesh-comms-core first if direct competitor notification has not already been proven. comms.md is the ledger, not the wake-up path.
Default roster: use Claude Code and Codex peers. Do not use Gemini CLI, Antigravity CLI, or Antigravity Desktop as competitors or judges unless the human prompt explicitly names that peer.
| Role | Description |
|---|---|
COMPETITOR | Creates an independent solution to the challenge |
JUDGE | Evaluates submissions against criteria, selects winner |
Competitors work in isolation. Judges deliberate together.
PHASE 1: CHALLENGE
- Challenge announced with clear criteria
- Competitors acknowledge and begin work
PHASE 2: PARALLEL WORK
- Competitors work independently (no collaboration)
- Each submits with [ENTRY]
PHASE 3: JUDGING
- Judges review all entries
- Score against criteria
- Deliberate on winner
PHASE 4: DECISION
- Judges announce winner with [WINNER]
- Provide feedback on all entries
- Optional: Synthesize best elements from all entries
[CHALLENGE]
TASK: [What competitors must create]
CRITERIA:
1. [Criterion 1] - [Weight]
2. [Criterion 2] - [Weight]
3. [Criterion 3] - [Weight]
DEADLINE: [Turn count]
[ENTRY - COMPETITOR]
SUBMISSION: [The work product]
APPROACH: [Brief explanation of strategy]
[SCORE - JUDGE]
ENTRY: [Competitor name]
Criterion 1: [Score/10]
Criterion 2: [Score/10]
Criterion 3: [Score/10]
TOTAL: [Sum]
NOTES: [Qualitative feedback]
[WINNER]
SELECTED: [Competitor name]
REASON: [Why this entry won]
SYNTHESIS: [Optional: Best ideas from all entries to combine]
All inputs come from the prompt.
Optional:
output: File path for winning entrywork: File containing challenge detailsmax_turns: Override default (40)Use competition to design a logo concept.
Competitors: CX, CC-peer-02.
Judge: CC.
Use competition for writing a product tagline.
Competitors: CC, CX.
Judges: CC-peer-02.
Criteria: Memorable, Clear, Under 8 words.
Output: projects/marketing/tagline.md
Use competition for architecture proposal.
Competitors: CC, CX.
Judges: CC-peer-02 (technical), CX-peer-02 (business).
Criteria: Scalability, Maintainability, Cost.
Output: projects/arch/winner.md
comms.md[CHALLENGE]
TASK: Write a one-paragraph product description for Interlateral
CRITERIA:
1. Clarity - Is it easy to understand? (30%)
2. Compelling - Does it make you want to learn more? (40%)
3. Accuracy - Does it reflect the actual product? (30%)
DEADLINE: 4 turns
[ENTRY - CC]
SUBMISSION:
"Interlateral is a multi-agent collaboration framework that turns
AI chaos into orchestrated teamwork. Instead of wrestling with
single-agent limitations, deploy teams of specialized AI agents
that communicate, negotiate, and build together. Six proven
design patterns—from simple peer review to full democratic
governance—let you match the collaboration style to the task."
APPROACH: Led with the problem (chaos), offered the solution (teamwork),
ended with concrete value (six patterns).
[ENTRY - CX]
SUBMISSION:
"What if AI agents could actually work together? Interlateral
makes it happen. Our framework connects multiple AI systems
into collaborative teams that tackle complex
projects through natural conversation. Choose from battle-tested
patterns like peer collaboration, competitive challenges, or
democratic decision-making. Your AI team, your rules."
APPROACH: Started with a hook question, emphasized multi-vendor,
ended with user empowerment.
[SCORE - CC-peer-02 (JUDGE)]
ENTRY: CC
Clarity: 8/10 - Clear but "AI chaos" might confuse newcomers
Compelling: 7/10 - Solid but a bit formal
Accuracy: 9/10 - Correctly describes patterns and value prop
TOTAL: 24/30
NOTES: Professional tone, accurate, but could be punchier.
ENTRY: CX
Clarity: 9/10 - Very accessible, question hook helps
Compelling: 9/10 - "Your AI team, your rules" is sticky
Accuracy: 8/10 - Multi-vendor angle is good but less about patterns
TOTAL: 26/30
NOTES: More engaging, slight sacrifice on technical depth.
[WINNER]
SELECTED: CX
REASON: Higher engagement factor while maintaining clarity. The
question hook and "your rules" ending create better reader connection.
SYNTHESIS: Consider combining CX's hook with CC's specific mention
of "six proven design patterns" for best of both worlds.
[DONE]
SKILL: competition
STATUS: DONE
TURNS: 8
OUTPUT: projects/marketing/description.md
COMPETITORS: CC, CX
JUDGES: CC-peer-02
WINNER: CX
SCORES: CC=24, CX=26