Decide
alirezarezvani/claude-skills
/cs:decide <memo — Log a decision to two-layer memory via decision-logger.
A skill your agent uses when reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference, HotCRP double-blind reviewing, the accept/revise/reject…
MITAuto-check passed
Install Eurosys Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-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/EuroSys-Skills/skills/eurosys-review-process .claude/skills/eurosys-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 "eurosys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-review-process into .claude/skills/eurosys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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/EuroSys-Skills/skills/eurosys-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 eurosys-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-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/EuroSys-Skills/skills/eurosys-review-process .agents/skills/eurosys-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 "eurosys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-review-process into .agents/skills/eurosys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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 eurosys-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-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/EuroSys-Skills/skills/eurosys-review-process .cursor/skills/eurosys-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 "eurosys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-review-process into .cursor/skills/eurosys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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 EuroSys-Skills/skills/eurosys-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 eurosys-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-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/EuroSys-Skills/skills/eurosys-review-process .gemini/skills/eurosys-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 "eurosys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-review-process into .gemini/skills/eurosys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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 eurosys-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 eurosys-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/EuroSys-Skills/skills/eurosys-review-process .github/skills/eurosys-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 "eurosys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-review-process into .github/skills/eurosys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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 eurosys-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 eurosys-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/EuroSys-Skills/skills/eurosys-review-process .opencode/skills/eurosys-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 "eurosys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-review-process into .opencode/skills/eurosys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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
eurosys-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 627 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 EuroSys decides papers — the two independent yearly rounds feeding one April conference, HotCRP double-blind reviewing, the accept/revise/reject…
- Works in 4 steps: Verifiable evaluation fairness — tuned… → A mechanism the reviewer can retell — if… → Claims scoped to evidence — a paper that… → …
- Reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference
- SKILL.md covers One conference, two juries, The outcome triple, Who is reading and What moves a PC discussion here, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Eurosys Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference, HotCRP double-blind reviewing, the accept/revise/reject outcome triple, the same-season resubmission ban after rejection, and community structures like the Shadow PC that shape who reviews.
Its SKILL.md is about 1.4k 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 EuroSys decides papers — the two independent yearly rounds feeding one April conference
- HotCRP double-blind reviewing
- The accept/revise/reject outcome triple
- The same-season resubmission ban after rejection
Example prompts
- “/eurosys-review-process”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Verifiable evaluation fairness — tuned baselines, named versions,
- A mechanism the reviewer can retell — if the design section cannot be
- Claims scoped to evidence — a paper that says where it loses earns the
- Deployment plausibility — EuroSys values systems that could run outside
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
Eurosys Review Process loads about 1.4k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 627 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). 627 words, ~1,430 tokens.
Download SKILL.mdSave it as
.claude/skills/eurosys-review-process/SKILL.md (or your agent's skills folder).- name
- eurosys-review-process
- description
- Use when reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference, HotCRP double-blind reviewing, the accept/revise/reject outcome triple, the same-season resubmission ban after rejection, and community structures like the Shadow PC that shape who reviews.
EuroSys Review Process
Use this to model the decision machinery around a EuroSys submission. Facts below are the 2026/2027 cycles as rendered on 2026-07-08 from the EuroSys CFPs and conference pages; per-round mechanics (rebuttal windows, review counts, online PC meeting format) are set inside each HotCRP instance — 待核实 there.
One conference, two juries
Each EuroSys edition accepts papers through two temporally separate rounds — for 2027: spring (papers May 14, 2026 → notification August 21, 2026) and fall (papers September 24, 2026 → notification January 29, 2027). Both cohorts are published in the same proceedings and presented at the same April conference. Strategically this means:
- Your competition is round-local; the PC calibrates within the round it reads.
- A spring reject cannot simply "try again in the fall": the CFP bars a rejected paper from returning until the same round of the next edition — a full year, not one deadline.
- A revision offer, by contrast, explicitly bridges rounds: revise-and-resubmit at the subsequent deadline, judged against the issued condition list.
The outcome triple
| Outcome | What it means | Author's next move |
|---|---|---|
| Accept | Into the edition's proceedings | Camera-ready + artifact evaluation |
| One-shot revision | Conditional path to the next round | Condition-by-condition execution plan |
| Reject | One-year same-season ban | Substantial rework, or a different venue |
"One-shot" is literal: the revision is evaluated once, against the conditions, by a process designed for continuity with the original reviews. There is no second revision offer downstream of the first.
Who is reading
- A double-blind HotCRP process: reviewers do not see authors, and conflicts declared at abstract registration drive assignments.
- The PC spans the breadth of European and international systems research — kernels, distributed systems, storage, cloud runtimes, virtualization, systems security, and increasingly systems-for-ML. Expect at least one reviewer whose home sub-area differs from yours; the paper's framing must carry them.
- EuroSys has repeatedly run a Shadow PC (e.g.,
2026.eurosys.org/shadow-pc.html), where early-career researchers review real submissions in parallel as training. Practical consequence: write for a rigorous but possibly junior reader, and expect the community's reviewing norms to be unusually explicit and well-documented.
Show full SKILL.md (291 more words)Show less
What moves a PC discussion here
- Verifiable evaluation fairness — tuned baselines, named versions, disclosed hardware — because the deepest systems-review instinct is to distrust a benchmark table.
- A mechanism the reviewer can retell — if the design section cannot be summarized in three sentences at the PC meeting, no champion can defend it.
- Claims scoped to evidence — a paper that says where it loses earns the credibility spent by every paper that doesn't.
- Deployment plausibility — EuroSys values systems that could run outside the lab; a purely synthetic setting needs an explicit bridge to practice.
A round from the author's seat
Between the paper gate and notification (roughly fourteen weeks in the 2027 spring round: May 14 → August 21), the author-visible surface is nearly silent. What happens behind it, in the standard HotCRP shape:
- Bidding and assignment off the registered topics and conflicts.
- First-round reviews; possibly a cut before additional reviews are commissioned on papers still alive.
- Rebuttal or author-reviewer interaction if the round runs one (待核实 in the round's HotCRP announcements).
- Online PC discussion converging each paper into one of the three bins, with revision-condition lists drafted for the middle bin.
- Notification, reviews, and — for the middle bin — the condition list.
The author-controllable inputs are all front-loaded: the registered abstract (bidding quality), the conflicts (assignment sanity), and the paper itself. Mid-round, the only lever is the response phase, if any.
Conduct boundaries
- No reviewer contact outside the platform, no identity fishing, no parallel submission of the same work to another archival venue.
- Public talks and preprints during review are governed by the round's anonymity wording — 待核实 before scheduling a seminar on the submitted work under its submission title.
Reading your reviews structurally
For each review, extract:
score-driver: the sentence that explains the score (rarely the summary)
fixability: bounded experiment/rewrite -> revision-compatible
identity-level objection -> reject-compatible
round-awareness: does the reviewer propose revision conditions?
Then ask: across reviewers, is there a coherent, enumerable condition list?
yes -> argue toward the revision bin in the rebuttal (if the round has one)
no -> maximize the accept case on the strongest review's termsOutput format
[Round position] spring / fall, and days to its next gate
[Outcome forecast] accept / revision / reject, with the driving signal
[Condition-list coherence] <enumerable fixes or identity-level objections>
[Ban exposure] <date this paper may legally return if rejected>
[待核实] <this round's rebuttal window, review counts, PC-meeting form>© 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 EuroSys-Skills/skills/eurosys-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Eurosys 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 |
|---|---|---|---|---|---|---|
| Eurosys Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Decidealirezarezvani/claude-skills | 28k | — | ~871 | Automated safety check: Pass | MIT | |
| Papers Skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Deepseek Reasonruvnet/ruflo | 74k | — | ~626 | Automated safety check: Notes | MIT | |
| Read arXiv Paperkarpathy/nanochat | 59k | 1 repos | ~494 | Automated safety check: Pass | MIT | |
| Hugging Face Paper Pageshuggingface/skills | 11k | 3 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Papers Skill
sickn33/agentic-awesome-skills
Skill for academic research workflows: search Semantic Scholar (200M+ papers), inspect citations, download arXiv PDFs, and extract PDF text.
Deepseek Reason
ruvnet/ruflo
Reasoning-mode completion against DeepSeek's deepseek-reasoner model (R1) via /v1/chat/completions.
Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
- Official
Hugging Face Paper Pages
huggingface/skills
Fetches Hugging Face paper pages as markdown and reads paper metadata through the papers API when you share a paper URL, an arXiv link or an arXiv ID.
Bgpt Paper Search
K-Dense-AI/scientific-agent-skills
Searches BGPT scientific papers by topic or DOI and retrieves claim-level evidence extracted from full text, including experiments, reported statistics, scope, limitations, and provenance.
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 Eurosys Review Process
What does Eurosys Review Process do?
A skill your agent uses when reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference, HotCRP double-blind reviewing, the accept/revise/reject…. Eurosys Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference, HotCRP double-blind reviewing, the accept/revise/reject outcome triple, the same-season resubmission ban after rejection, and community structures like the Shadow PC that shape who reviews.
When should I use Eurosys Review Process?
Eurosys Review Process fits situations like: reasoning about how EuroSys decides papers — the two independent yearly rounds feeding one April conference; hotCRP double-blind reviewing; the accept/revise/reject outcome triple; the same-season resubmission ban after rejection.
How do I install Eurosys Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-review-process -a claude-code`. Or copy the skill folder (EuroSys-Skills/skills/eurosys-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/eurosys-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Eurosys Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-review-process -a codex`. Or copy the skill folder (EuroSys-Skills/skills/eurosys-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/eurosys-review-process in your project. Codex loads it when a task matches its description.
Can I use Eurosys 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 eurosys-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/eurosys-review-process, .gemini/skills/eurosys-review-process, .github/skills/eurosys-review-process and .opencode/skills/eurosys-review-process in your project.
What does Eurosys Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Eurosys Review Process is instructions for the agent only.
Does Eurosys 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 Eurosys 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 Eurosys Review Process use?
Eurosys 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 Eurosys Review Process use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Eurosys Review Process?
Skills that share tags, products or a category with Eurosys Review Process: Decide (alirezarezvani/claude-skills, 28k stars), Papers Skill (sickn33/agentic-awesome-skills, 47k stars), Deepseek Reason (ruvnet/ruflo, 74k stars) and Read arXiv Paper (karpathy/nanochat, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eurosys 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.