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 ACM IMC submission is evaluated, covering double-blind multi-round review, the Accept / One-Shot-Revision / Reject decision categories, the…
MITAuto-check passed
Install Imc Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill imc-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills imc-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/IMC-Skills/skills/imc-review-process .claude/skills/imc-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 "imc-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IMC-Skills/skills/imc-review-process into .claude/skills/imc-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "imc-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/IMC-Skills/skills/imc-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 imc-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills imc-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/IMC-Skills/skills/imc-review-process .agents/skills/imc-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 "imc-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IMC-Skills/skills/imc-review-process into .agents/skills/imc-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "imc-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 imc-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills imc-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/IMC-Skills/skills/imc-review-process .cursor/skills/imc-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 "imc-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IMC-Skills/skills/imc-review-process into .cursor/skills/imc-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "imc-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 IMC-Skills/skills/imc-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 imc-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills imc-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/IMC-Skills/skills/imc-review-process .gemini/skills/imc-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 "imc-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IMC-Skills/skills/imc-review-process into .gemini/skills/imc-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "imc-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 imc-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 imc-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/IMC-Skills/skills/imc-review-process .github/skills/imc-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 "imc-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IMC-Skills/skills/imc-review-process into .github/skills/imc-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "imc-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 imc-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 imc-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/IMC-Skills/skills/imc-review-process .opencode/skills/imc-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 "imc-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IMC-Skills/skills/imc-review-process into .opencode/skills/imc-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "imc-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
imc-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 621 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 ACM IMC submission is evaluated, covering double-blind multi-round review, the Accept / One-Shot-Revision / Reject decision categories, the…
- Reasoning about how an ACM IMC submission is evaluated
- SKILL.md covers Process model, The One-Shot-Revision, precisely, Reading a decision against the… and How IMC differs from its…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering double-blind multi-round review
What it does
Imc Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an ACM IMC submission is evaluated, covering double-blind multi-round review, the Accept / One-Shot-Revision / Reject decision categories, the reviewer-champion rule and bounded action points, early rejection of consensus-reject papers, shepherding for artifact availability, and how IMC's two-deadline model differs from SIGCOMM/NSDI cycles.
Its SKILL.md is about 1.5k 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 ACM IMC submission is evaluated
- Covering double-blind multi-round review
- The Accept / One-Shot-Revision / Reject decision categories
- The reviewer-champion rule and bounded action points
Example prompts
- “/imc-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
Imc Review Process loads about 1.5k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 621 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). 621 words, ~1,500 tokens.
Download SKILL.mdSave it as
.claude/skills/imc-review-process/SKILL.md (or your agent's skills folder).- name
- imc-review-process
- description
- Use when reasoning about how an ACM IMC submission is evaluated, covering double-blind multi-round review, the Accept / One-Shot-Revision / Reject decision categories, the reviewer-champion rule and bounded action points, early rejection of consensus-reject papers, shepherding for artifact availability, and how IMC's two-deadline model differs from SIGCOMM/NSDI cycles.
IMC Review Process
Model the pipeline before interpreting any single review. IMC's process is built around two deadlines a year and a distinctive middle outcome — One-Shot-Revision — that is neither a plain reject nor an open-ended major revision. The most consequential mental shift for authors arriving from a single-round conference is that a good-but-incomplete measurement paper has a bounded path to acceptance across deadlines.
Process model
- Submission and review run on HotCRP with double-blind anonymity maintained through reviewing.
- Review proceeds in several rounds. Papers with a consensus for rejection are notified early, so authors can move the work to another venue without waiting for the full cycle.
- First decisions fall into Accept, One-Shot-Revision, or Reject. Reviewers weigh the significance of the measurement finding, the credibility of vantage points and ground truth, the soundness of methodology, honesty about limitations and confounds, the Ethics treatment, and artifact availability.
- Accepted papers may be shepherded by PC members — notably to ensure the artifacts promised in the availability declaration are actually made available.
The One-Shot-Revision, precisely
| Element | What the call specifies |
|---|---|
| Trigger | At least one reviewer champion advocating the work's relevance and timeliness |
| Scope | Up to 3 additions/changes — a bounded, concrete action list, not "revise broadly" |
| Resubmission | To the next deadline in the two-deadline cycle |
| Re-review | By the same reviewers, against the action points |
The strategic reading: a One-Shot-Revision is a contract. It is granted because someone
believes in the paper, and it is judged narrowly on whether the named action points were done.
Treat it as a near-accept with obligations, not a coin flip (see imc-author-response).
Reading a decision against the categories
| Decision | What it means | Author move |
|---|---|---|
| Accept | Finding and method hold; shepherding for availability | Deliver the promised artifact; do not reopen scope |
| One-Shot-Revision | A champion exists; a bounded set of gaps (a missing vantage point, a confound to address, an ethics clarification) | Execute exactly the named action points; resubmit next deadline to the same reviewers |
| Reject | Structural: unrepresentative vantage points, no ground truth, thin measurement, ethics failure | Reframe or reroute (SIGCOMM/NSDI/CoNEXT/PAM or a journal); do not lightly resubmit unchanged |
Design the submission so its weakest point is an addressable action item (an extra vantage point, a longitudinal slice, a bounded confound) rather than a structural flaw (a study design you cannot redo before the next deadline).
Show full SKILL.md (238 more words)Show less
How IMC differs from its siblings
- vs. SIGCOMM / NSDI: those reward systems and protocol design with a supporting evaluation; IMC rewards the measurement itself and enforces the Ethics gate and availability declaration harder. Never assume a shared calendar or template.
- vs. a single-deadline conference: IMC's two deadlines plus One-Shot-Revision give a within- year second chance with continuity of reviewers — closer to a lightweight revise-and-resubmit than to "reject and try next year."
- vs. a journal: the revision is one shot and bounded (up to a few action points), not an open iterative loop.
Who reads you
Expect measurement experts who will interrogate vantage-point representativeness, whether ground truth is real, whether the finding is a snapshot artifact of a moving Internet, and whether the active measurement was safe and ethical. Because IMC spans scanning, DNS, routing, web, security, and social measurement, papers are matched to subarea reviewers — a vague methodology gets caught, not skimmed.
Where author leverage actually exists
[Before submission] topic tags + vantage-point framing -> reviewer pool (largest lever)
[Initial reviews] factual corrections, clarifying vantage-point coverage, ethics clarifications
[One-Shot-Revision] the strongest lever: execute the bounded action points exactly, for the
same reviewers, and show each one done
[Shepherding] deliver the promised artifact; this is about availability, not new science
[After reject] no appeal; reroute to a sibling venue or a journalMisreadings to avoid
- Treating One-Shot-Revision as a full rewrite window — you get a bounded action list and the same reviewers; scope creep signals you missed the point.
- Treating One-Shot-Revision as guaranteed — the second read against the action points is real.
- Ignoring the early-reject signal — a consensus-reject notice is a routing prompt, not an invitation to argue.
- Underestimating shepherding — a promised dataset that never materializes is a real problem.
- Projecting last year's cadence — deadline dates and revision mechanics are per-edition.
Output format
[Process stage] pre-submission / awaiting reviews / one-shot-revision / shepherding / accepted
[Decision category] accept / one-shot-revision / reject, with the criterion driving it
[Champion?] is there a reviewer advocate? which review reads closest?
[Action points] <the bounded list to execute for the next deadline>
[Leverage plan] the next-stage action that can actually change the outcome
[Forbidden moves] identity leak / scope creep beyond the action points / undelivered artifact© 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 IMC-Skills/skills/imc-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Imc 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 |
|---|---|---|---|---|---|---|
| Imc Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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 Imc Review Process
What does Imc Review Process do?
A skill your agent uses when reasoning about how an ACM IMC submission is evaluated, covering double-blind multi-round review, the Accept / One-Shot-Revision / Reject decision categories, the…. Imc Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an ACM IMC submission is evaluated, covering double-blind multi-round review, the Accept / One-Shot-Revision / Reject decision categories, the reviewer-champion rule and bounded action points, early rejection of consensus-reject papers, shepherding for artifact availability, and how IMC's two-deadline model differs from SIGCOMM/NSDI cycles.
When should I use Imc Review Process?
Imc Review Process fits situations like: reasoning about how an ACM IMC submission is evaluated; covering double-blind multi-round review; the Accept / One-Shot-Revision / Reject decision categories; the reviewer-champion rule and bounded action points.
How do I install Imc Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill imc-review-process -a claude-code`. Or copy the skill folder (IMC-Skills/skills/imc-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/imc-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Imc Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill imc-review-process -a codex`. Or copy the skill folder (IMC-Skills/skills/imc-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/imc-review-process in your project. Codex loads it when a task matches its description.
Can I use Imc 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 imc-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/imc-review-process, .gemini/skills/imc-review-process, .github/skills/imc-review-process and .opencode/skills/imc-review-process in your project.
What does Imc Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Imc Review Process is instructions for the agent only.
Does Imc 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 Imc 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 Imc Review Process use?
Imc 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 Imc Review Process use?
About 1.5k tokens (SKILL.md is roughly 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 Imc Review Process?
Skills that share tags, products or a category with Imc 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 Imc 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.