Arize Evaluator
github/awesome-copilot
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…
A skill your agent uses when reasoning about how an ECAI submission is evaluated — double-blind review, the summary-reject first phase, area chairs / senior PC, the single author-response (rebuttal)…
MITAuto-check passed
Install Ecai Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ECAI-Skills/skills/ecai-review-process .claude/skills/ecai-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ecai-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-review-process into .claude/skills/ecai-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ECAI-Skills/skills/ecai-review-process .agents/skills/ecai-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ecai-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-review-process into .agents/skills/ecai-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ECAI-Skills/skills/ecai-review-process .cursor/skills/ecai-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ecai-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-review-process into .cursor/skills/ecai-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ECAI-Skills/skills/ecai-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ECAI-Skills/skills/ecai-review-process .gemini/skills/ecai-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ecai-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-review-process into .gemini/skills/ecai-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ECAI-Skills/skills/ecai-review-process .github/skills/ecai-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ecai-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-review-process into .github/skills/ecai-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ECAI-Skills/skills/ecai-review-process .opencode/skills/ecai-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ecai-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-review-process into .opencode/skills/ecai-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ecai-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 754 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how an ECAI submission is evaluated — double-blind review, the summary-reject first phase, area chairs / senior PC, the single author-response (rebuttal)…
- Reasoning about how an ECAI submission is evaluated — double-blind review
- SKILL.md covers Process model (IJCAI-ECAI 2026), Reading the decision categories, How ECAI differs from its… and Who reads you, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The summary-reject first phase
What it does
Ecai Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an ECAI submission is evaluated — double-blind review, the summary-reject first phase, area chairs / senior PC, the single author-response (rebuttal) window, an accept/reject decision (no journal-style major-revision round), and how ECAI's process and its joint IJCAI-ECAI 2026 form differ from AAAI, IJCAI standalone, and AAMAS.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Reasoning about how an ECAI submission is evaluated — double-blind review
- The summary-reject first phase
- Area chairs / senior PC
- The single author-response (rebuttal) window
Example prompts
- “/ecai-review-process”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ecai Review Process loads about 1.6k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 754 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 754 words, ~1,638 tokens.
Download SKILL.mdSave it as
.claude/skills/ecai-review-process/SKILL.md (or your agent's skills folder).- name
- ecai-review-process
- description
- Use when reasoning about how an ECAI submission is evaluated — double-blind review, the summary-reject first phase, area chairs / senior PC, the single author-response (rebuttal) window, an accept/reject decision (no journal-style major-revision round), and how ECAI's process and its joint IJCAI-ECAI 2026 form differ from AAAI, IJCAI standalone, and AAMAS.
ECAI Review Process
Model the pipeline before interpreting any single review. ECAI runs a single-round, double-blind conference review with a rebuttal — not a journal-style revise-and-resubmit. The most consequential mental shift for authors arriving from a journal (or from a venue with a major- revision decision) is that there is no second submission: the paper you submit, plus one short author response, is the whole story. The current edition, IJCAI-ECAI 2026, follows the IJCAI process because ECAI 2026 is being run jointly with IJCAI.
Process model (IJCAI-ECAI 2026)
- Submission and review are double-blind; identities are hidden from reviewers throughout.
- A summary-reject first phase filters clearly-out-of-scope or below-bar submissions early (IJCAI-ECAI 2026 summary-reject notification: 4 March 2026). A paper cleared past summary reject goes to full review.
- Full review is organized under area chairs / senior PC who oversee reviewers in a topic area and lead the discussion. Reviewers weigh significance of the AI contribution, technical soundness (proofs and/or experiments), clarity, and fit.
- Authors get one author-response (rebuttal) window (IJCAI-ECAI 2026: 7-10 April 2026) to answer factual points before the final decision.
- The decision is accept or reject (final notification 29 April 2026). There is no guaranteed revision round; camera-ready changes are minor, not a re-review.
Reading the decision categories
| Decision | What it means | Author move |
|---|---|---|
| Accept | Contribution and evidence hold | Camera-ready in the correct template; do not expand scope |
| Reject (after full review) | A soundness, significance, or clarity gap the rebuttal did not close | Revise substantively and reroute (AAAI/IJCAI/a specialist venue) or resubmit next ECAI |
| Summary reject | Out of scope, below bar, or a formatting/anonymity violation caught early | Do not appeal into the void — fix the structural issue before any resubmission |
The strategic reading: because there is no major-revision safety net, the submitted paper must already be complete — the proof finished, the baseline fair, the claim matched to the evidence. A gap you were "planning to fix in revision" has nowhere to go.
How ECAI differs from its siblings
- vs. a journal / major-revision venue: ECAI has no Major Revision decision. You cannot count on a second round; there is one rebuttal, then accept/reject.
- vs. AAAI: AAAI and ECAI are both general-AI, double-blind, single-round with rebuttal, but on
different calendars and templates (AAAI style vs
ecai.cls/ijcai.sty) and governed by different bodies (AAAI vs EurAI). Never assume shared dates or format. - vs. IJCAI (standalone years): ECAI is EurAI's European flagship; IJCAI is the international
one. In 2026 they are the same event (joint IJCAI-ECAI), so the process is IJCAI's — but in a
standalone ECAI year the FAIA/
ecai.clsconventions and PAIS co-location return. - vs. AAMAS / KR / specialist venues: those run their own reviewing for multi-agent systems or
knowledge representation; a paper matched better to a specialist reviewer pool may fare better
there than in ECAI's broad pool (
ecai-topic-selection).
Show full SKILL.md (291 more words)Show less
Who reads you
Expect several reviewers under an area chair drawn from your topic area — and note that by submitting you volunteer for the reviewer pool yourself (IJCAI-ECAI 2026 policy). Because ECAI spans symbolic AI, planning, KR, multi-agent systems, and ML, matching your topics well is what gets you expert reviewers rather than distant ones. Vague method descriptions get caught in the discussion the area chair runs, not skimmed.
Where author leverage actually exists
[Before submission] topics/keywords -> area chair + reviewer pool (largest lever)
[Summary-reject risk] scope, formatting, anonymity, page budget correct BEFORE upload
[Rebuttal] correct factual misreadings, supply one asked-for number,
answer the specific objection each reviewer raised
[After reject] no appeal that reopens the decision; reroute or resubmit next cycleA rebuttal moves borderline papers when it corrects a factual misreading or provides a clarification a reviewer said was missing; it does not move papers when it argues taste or promises future work. With only one response and no revision round, the rebuttal is a precision instrument, not a plan.
Reading a review packet
Weight reviews before answering. A review that cites your definitions, lemmas, and tables was read closely; its author is your likely advocate if the rebuttal holds. A review that discusses only novelty has left soundness to the others — answer each reviewer on the axis they raised. The area chair, not any single reviewer, drives the outcome in discussion, so a response that gives the AC a clean reason to champion the paper is worth more than one that "wins" against a hostile reviewer.
Misreadings to avoid
- Expecting a revision round — there is none; the submission is final bar minor camera-ready.
- Treating the rebuttal as a debate — the AC-led discussion decides; your text is evidence for an advocate, not a closing argument.
- Ignoring summary-reject risk — a formatting, anonymity, or scope slip can end the paper before review even begins.
- Projecting last year's process — a standalone ECAI and a joint IJCAI-ECAI year differ in organizer, template, and sometimes mechanics; confirm the current edition.
Output format
[Process stage] pre-submission / summary-reject phase / under review / rebuttal / final
[Edition regime] standalone ECAI / joint IJCAI-ECAI (IJCAI process)
[Decision] accept / reject / summary reject, with the criterion driving it
[Criterion map] each review point -> significance | soundness/proof | evidence | clarity | fit
[Leverage plan] the rebuttal move that can actually change this AC's recommendation
[Forbidden moves] identity leak / new unsupported claims / promising a revision that cannot happen© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ECAI-Skills/skills/ecai-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ecai Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ecai Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 1 repos | ~8.1k | Automated safety check: Notes | MIT | |
| LLM Evaluationdavila7/claude-code-templates | 33k | 12 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Agent Evaluationsickn33/agentic-awesome-skills | 47k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Deepseek Reasonruvnet/ruflo | 74k | — | ~626 | Automated safety check: Notes | MIT | |
| EvaluatorsArize-ai/phoenix | 12k | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
LLM Evaluation
davila7/claude-code-templates
Master comprehensive evaluation strategies for LLM applications, from automated metrics to human evaluation and A/B testing.
Agent Evaluation
sickn33/agentic-awesome-skills
Evaluate agent behavior with versioned cases and explicit verifiers.
Deepseek Reason
ruvnet/ruflo
Reasoning-mode completion against DeepSeek's deepseek-reasoner model (R1) via /v1/chat/completions.
Evaluators
Arize-ai/phoenix
Author or refine a Phoenix evaluator — code or LLM-as-a-judge — that scores a run's output.
Agent Evaluation Reporting
sickn33/agentic-awesome-skills
A skill your agent uses when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Ecai Review Process
What does Ecai Review Process do?
A skill your agent uses when reasoning about how an ECAI submission is evaluated — double-blind review, the summary-reject first phase, area chairs / senior PC, the single author-response (rebuttal)…. Ecai Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an ECAI submission is evaluated — double-blind review, the summary-reject first phase, area chairs / senior PC, the single author-response (rebuttal) window, an accept/reject decision (no journal-style major-revision round), and how ECAI's process and its joint IJCAI-ECAI 2026 form differ from AAAI, IJCAI standalone, and AAMAS.
When should I use Ecai Review Process?
Ecai Review Process fits situations like: reasoning about how an ECAI submission is evaluated — double-blind review; the summary-reject first phase; area chairs / senior PC; the single author-response (rebuttal) window.
How do I install Ecai Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-review-process -a claude-code`. Or copy the skill folder (ECAI-Skills/skills/ecai-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ecai-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Ecai Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-review-process -a codex`. Or copy the skill folder (ECAI-Skills/skills/ecai-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ecai-review-process in your project. Codex loads it when a task matches its description.
Can I use Ecai Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ecai-review-process, .gemini/skills/ecai-review-process, .github/skills/ecai-review-process and .opencode/skills/ecai-review-process in your project.
What does Ecai Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Ecai Review Process is instructions for the agent only.
Does Ecai Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ecai Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ecai Review Process use?
Ecai Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ecai Review Process use?
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ecai Review Process?
Skills that share tags, products or a category with Ecai Review Process: Arize Evaluator (github/awesome-copilot, 40k stars), LLM Evaluation (davila7/claude-code-templates, 33k stars), Agent Evaluation (sickn33/agentic-awesome-skills, 47k stars) and Deepseek Reason (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ecai Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.