REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
When Claude keeps giving you bad answers, make 100 versions of it fight to the death. Same task, 100 different strategies, a bracket, one answer left. Free Claude Code skill.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/jakeschincariol-arena-skill)在同一工作中把 AI 连到服务的 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同类工作,排序与 Skill 列表相同
| 本项 arena-skill | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | Jakeschincariol | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 1,535 | 467,235 | 234,125 | 149,873 | 144,332 |
| 最近代码更新 | 2026年9月27日 | 2026年11月18日 | 2026年4月20日 | 2026年11月18日 | 2026年11月18日 |
| 许可证 | MIT | MIT | – | Apache-2.0 | MIT |
Jakeschincariol 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude Code
依据开发者 README 和 repo 中的文件夹
GitHub account Jakeschincariol (person), 1 years old
★ 1,535 stars · code last changed 2026年9月27日
1 scripts that can run on a computer: bracket.py
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit df07b8e (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (541). Use "Let the AI install it" instead
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /arena,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
/plugin marketplace add Jakeschincariol/arena-skill
/plugin install arena-skill@arena-skill摘自开发者 README,会下载并运行开发者的代码
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/jakeschincariol/arena-skill.git /tmp/popnx-skill-jakeschincariol-arena-skill-df07b8e && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-jakeschincariol-arena-skill-df07b8e/skills/arena' ~/.claude/skills/arenaChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 arena 文件夹放到 ~/.agents/skills/arena
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/jakeschincariol/arena-skill.git /tmp/popnx-skill-jakeschincariol-arena-skill-df07b8e && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-jakeschincariol-arena-skill-df07b8e/skills/arena' ~/.agents/skills/arenaChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/jakeschincariol/arena-skill.git /tmp/popnx-skill-jakeschincariol-arena-skill-df07b8e && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-jakeschincariol-arena-skill-df07b8e/skills/arena' ~/.agents/skills/arena复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 arena
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/jakeschincariol/arena-skill.git /tmp/popnx-skill-jakeschincariol-arena-skill-df07b8e && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-jakeschincariol-arena-skill-df07b8e/skills/arena' ~/.cursor/skills/arena适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月17日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: arena
description: >-
Make 100 versions of Claude fight to the death over one task. Spins up N
sub-agents (default 100, --quick for 16), gives every one the exact same
task plus a different strategy card (reasoning mode, workflow, strategy),
then runs a single-elimination bracket: they attack each other's solutions,
defend and revise, and a judge scores every match on a written rubric until
one solution survives. Use when the user is not satisfied with an answer,
calls it a bad answer, says try again or do better, says "arena", or asks
to make them compete.
argument-hint: "[--agents N | --quick] [--seed S] <task>"
---
# arena
For when Claude keeps giving a bad answer. Instead of asking again and again, this runs a tournament:
N sub-agents get the exact same task, each attacks it with a different reasoning mode, workflow and
strategy, and then they attack each other in a bracket until one solution is left. You are the
orchestrator. You never compete and you never judge.
What the user typed after `/arena`: `$ARGUMENTS`
If that is blank, or still reads like a placeholder, nothing was passed: take the task from the
conversation.
## The tool
Every piece of bookkeeping goes through `bracket.py` in this skill's folder:
```bash
python3 "${CLAUDE_SKILL_DIR}/bracket.py" <command>
```
Below, `ARENA` means exactly that command. If the path looks unexpanded, use the "Base directory for
this skill" that Claude Code printed at the top of this skill. The state lives in
`.arena/<run>/arena.json` in the current directory, and every command after `init` finds it through
`.arena/LATEST`.
## Step 1: size it, and get a yes if nobody asked for it
Read the flags out of the request. Everything that is not a flag is the task.
| flag | meaning |
| --- | --- |
| `--agents N` | N competitors. Default 100. |
| `--quick` | 16 competitors. The everyday setting. |
| `--seed S` | Fixes the cards and the pairings. Default: random, and recorded. |
| `--wave W` | Sub-agents per wave. Default 10. Only raise it if the user raised Claude Code's limit. |
No task text at all means: the task is the user's most recent request in this conversation, and your
last answer to it is the baseline to beat.
Run `ARENA plan --agents N` (or `--quick`). It prints the rounds, the sub-agent calls and the waves.
- **The user asked for the arena** (typed `/arena`, said "arena", or asked to make them compete):
tell them in one line how big it is, for example "100 agents, 7 rounds, 595 sub-agent calls", and
start.
- **This skill fired because the user is unhappy** ("that's wrong", "try again", "bad answer") and
never mentioned the arena: ask once before spending anything. Offer three options: the full arena
(100 agents, 595 sub-agent calls), `--quick` (16 agents, 91 calls), or an ordinary retry. Wait for
the answer.
Sub-agents write their work into `.arena/` in the current directory. In the default permission mode
that is one approval per file, which is hundreds on a big run. Before the spawn phase, suggest
accept-edits mode (Shift+Tab) for the run. Do not change the user's settings yourself.
## Step 2: write the task file
This is the step that decides the result. **Sub-agents cannot see this conversation.** Every
competitor, attacker and judge knows only what is in the task file, so write `.arena/task.md` to stand
on its own:
- The request, in the user's own words where you can.
- Every requirement and constraint the user stated anywhere in the conversation: audience, length,
format, tone, stack, deadline, what must not change.
- The context a stranger would need: absolute paths of the files that matter, pasted data, what the
product is, the conventions in the codebase.
- What "done" looks like, if the user said.
- If there is an answer to beat: what the user disliked about it, in their words.
Do not add requirements the user never gave. Do not write your own view of the right answer into it:
that pushes 100 agents the same way, which is the opposite of the point.
If there is an earlier answer the user was not satisfied with, write it word for word to
`.arena/baseline.md`.
## Step 3: init
```bash
ARENA init --agents N --seed S --task-file .arena/task.md --baseline-file .arena/baseline.md
```
Leave out `--baseline-file` when there is nothing to beat, and `--seed` to get a random one. `init`
copies the task into the run folder, deals every competitor a different strategy card with no
repeats, pairs round 1, and writes `arena.json`.
## Step 4: the loop
Always drive it with `ARENA next`. It reads the state on disk and tells you the next step and the
exact command.
Every phase that runs sub-agents works the same way:
1. `ARENA prompts <phase>` writes one brief per job and lists the jobs still to run, in waves.
2. Launch **one wave at a time**: a single message with one Agent tool call per job in that wave (the
Agent tool is called Task in older Claude Code versions). Each call is:
- `subagent_type`: `general-purpose`
- `description`: `arena <job id>`
- `prompt`: `Read <prompt path> and follow it exactly. It is your whole brief.`
- `run_in_background`: false, where the tool has that option, so the wave comes back together.
Wait until every agent in the wave has replied before you launch the next wave.
3. After the last wave, run `ARENA next`. If an output is missing it sends you back to the same
phase, and `prompts` then lists only the missing jobs. Re-run those once. If a job fails twice,
write the single line `NO OUTPUT` into each of its output files (`ARENA check <phase>` lists
them) and move on. A missing attack counts as no attacks. A missing solution loses its match. A
judge that fails twice gets a third, fresh run: never decide a match yourself.
The order `next` takes you through:
- **spawn**, once: every competitor writes its own solution to the task.
- then every round: **attack** (two per match) → **defend** (two per match) → **judge** (one per
match) → `ARENA collect` → `ARENA advance`.
- **final**, once, only when there is a baseline: a judge compares the champion with the answer the
user rejected, blind to which is which. Then `ARENA collect`.
- `next` prints DONE: go to step 5.
After each `advance`, give the user one line, such as "Round 2 done: 25 of 100 left." Nothing more.
Never paste pairings, attacks, verdicts or solutions into the chat.
Why waves: Claude Code runs at most 10 tool calls at once by default (the
`CLAUDE_CODE_MAX_TOOL_USE_CONCURRENCY` setting). So a 100-agent spawn is 10 waves of 10, and a
100-agent arena is 70 waves in total, 71 with the final check.
## Step 5: the result
Run `ARENA winner`, then read the champion's solution file at the path it prints. That is the only
solution file you read in the whole run. Give the user:
1. **The winning solution**, in full.
2. **Why it won**: the attacks it survived, from `winner`, as a short list. Its card on one line
(reasoning mode + workflow + strategy).
3. **Rounds**: for example "7 rounds, 100 agents in, 1 left."
4. **Against the answer you rejected**, if there was one: the final check's scores, honestly. If the
old answer scored higher, say so plainly and show both.
5. Where the full record lives: the run folder.
If the solution changes files in the user's project, do not apply it. Ask: apply it, or change it?
## Rules for the orchestrator
- You run the tournament. You do not compete, attack or judge, and you never pick a winner.
`collect` records what the judges decided. `record` is only for fixing bookkeeping when the user
asks you to.
- Every sub-agent gets the task through its brief, which `prompts` builds from the one task file,
byte for byte the same for everyone. Never paraphrase the task for one agent or add a hint to one
agent's call.
- Do not read solutions, attacks or verdicts during the run. There are hundreds of them. The state
is on disk, and `next`, `status` and `pairings` are all you need.
- If 提问、分享技巧或报告无法使用。按“有帮助”数量排序。