OmniRoute Model Catalog
diegosouzapw/OmniRoute
Looks up which AI models an OmniRoute gateway can reach, creates or updates model aliases and tests whether individual models respond.
A skill your agent uses when modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions, the 2026 reviewer-duty enforcement that desk-rejects authors…
MITAuto-check passed
Install Eccv Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eccv-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eccv-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/ECCV-Skills/skills/eccv-review-process .claude/skills/eccv-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 "eccv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECCV-Skills/skills/eccv-review-process into .claude/skills/eccv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eccv-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/ECCV-Skills/skills/eccv-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 eccv-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eccv-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/ECCV-Skills/skills/eccv-review-process .agents/skills/eccv-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 "eccv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECCV-Skills/skills/eccv-review-process into .agents/skills/eccv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eccv-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 eccv-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eccv-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/ECCV-Skills/skills/eccv-review-process .cursor/skills/eccv-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 "eccv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECCV-Skills/skills/eccv-review-process into .cursor/skills/eccv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eccv-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 ECCV-Skills/skills/eccv-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 eccv-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eccv-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/ECCV-Skills/skills/eccv-review-process .gemini/skills/eccv-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 "eccv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECCV-Skills/skills/eccv-review-process into .gemini/skills/eccv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eccv-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 eccv-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 eccv-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/ECCV-Skills/skills/eccv-review-process .github/skills/eccv-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 "eccv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECCV-Skills/skills/eccv-review-process into .github/skills/eccv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eccv-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 eccv-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 eccv-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/ECCV-Skills/skills/eccv-review-process .opencode/skills/eccv-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 "eccv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECCV-Skills/skills/eccv-review-process into .opencode/skills/eccv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eccv-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
eccv-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 415 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions, the 2026 reviewer-duty enforcement that desk-rejects authors…
- Modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions
- SKILL.md covers The 2026 pipeline, The 2026 enforcement regime, Who is reading and Reading the decision mechanics, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The 2026 reviewer-duty enforcement that desk-rejects authors of late
What it does
Eccv Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions, the 2026 reviewer-duty enforcement that desk-rejects authors of late or LLM-written reviews, rebuttal-to-AC-discussion dynamics, and what the ECVA-run, Springer-published structure means for outcomes.
Its SKILL.md is about 1.1k 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
- Modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions
- The 2026 reviewer-duty enforcement that desk-rejects authors of late
- LLM-written reviews
- Rebuttal-to-AC-discussion dynamics
Example prompts
- “/eccv-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
Eccv Review Process loads about 1.1k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 415 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). 415 words, ~1,057 tokens.
Download SKILL.mdSave it as
.claude/skills/eccv-review-process/SKILL.md (or your agent's skills folder).- name
- eccv-review-process
- description
- Use when modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions, the 2026 reviewer-duty enforcement that desk-rejects authors of late or LLM-written reviews, rebuttal-to-AC-discussion dynamics, and what the ECVA-run, Springer-published structure means for outcomes.
ECCV Review Process
Use this to reason about what happens to an ECCV paper between upload and decision. ECCV is run by the European Computer Vision Association (ECVA) with per-edition program chairs; there is no standing editorial board, and process rules are rewritten every two years — the 2026 mechanics below are verified anchors (2026-07-08), not permanent law.
The 2026 pipeline
| Stage | 2026 dates | What actually happens |
|---|---|---|
| Registration → submission | Feb 26 → Mar 5 | OpenReview record created; late profile fixes until Mar 2 |
| Review period | Mar 13 → Jun 17 | ACs assign; reviewers work on OpenReview |
| Reviews to authors | May 2 | Typically three reviews with ratings |
| Rebuttal | due May 11; to reviewers May 12 | One page, two-column, references included |
| AC discussion → decision | May–Jun; decisions Jun 17 | AC synthesizes; borderline fates decided here |
| Camera-ready | Jun 30 AoE (extended) | Springer LNCS pipeline takes over |
The 2026 enforcement regime
The distinctive 2026 process fact: review quality was enforced against authors. All authors were expected to be willing to review if asked, and:
- A reviewer missing the review deadline faced desk rejection of all papers they co-authored.
- A review judged "highly irresponsible" — explicitly including LLM policy violations — triggered the same, at PC discretion.
- The LLM policy (aligned with CVPR 2026) barred using LLMs to write reviews or share substantial paper content, while allowing background research and short grammar checks; reviews were screened for violations.
Strategic consequence: your paper's risk surface includes every co-author's reviewing inbox. Track assignments like deadlines.
Show full SKILL.md (173 more words)Show less
Who is reading
- Panels are internationally mixed with a strong European base; expect one in-niche reviewer and two adjacent-niche reviewers rather than three specialists.
- Adjacent-niche reviewers anchor on the benchmark table and the qualitative figures; the in-niche reviewer checks novelty against the last CVPR/ICCV cycle. Write and rebut for both audiences.
- ECCV's biennial cadence means reviewers compare against two years of
intervening literature, including papers published after your development
froze — expect and preempt "how does this compare to [March-adjacent
arXiv]?" via the concurrent-work conventions in
eccv-related-work.
Reading the decision mechanics
Signals that the AC discussion, not the raw scores, decides you:
- score spread >= 2 points between reviewers
- one review is short + negative (candidate for AC down-weighting)
- rebuttal directly falsified a factual claim in a review
Actions that move an AC:
- rebuttal blocks quotable into a meta-review
- reviewer-requested evidence that already existed in the submission
Actions that do not:
- appeals to effort, novelty-by-assertion, or venue prestige of prior workAfter the decision
- Accept: the Springer/ECVA machine starts (
eccv-camera-ready); open access appears ~4 weeks pre-conference on ecva.net. - Reject: the biennial gap makes the reroute decision urgent — reviews arrive in June, and CVPR's November deadline is the natural next stop. Convert each review point into a revision ticket while context is fresh.
- Award structure exists (ECVA's Koenderink Prize honors a ten-year-old ECCV
paper each edition) but plays no role in decisions; ignore it during
review, use it for taste calibration in
eccv-topic-selection.
Output format
[Stage] pre-submission / in-review / rebuttal / discussion / decided
[Panel model] <in-niche vs adjacent reviewer count, score spread>
[Enforcement exposure] <co-author reviewing assignments + status>
[AC leverage points] <what the meta-review can quote>
[Next-stage move] <one action with its date anchor>© 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 ECCV-Skills/skills/eccv-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Eccv 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 |
|---|---|---|---|---|---|---|
| Eccv Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| OmniRoute Model Catalogdiegosouzapw/OmniRoute | 74k | — | ~589 | Automated safety check: Pass | MIT | |
| Model Bank Metadatalobehub/lobehub | 83k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Harness Threat Modelruvnet/ruflo | 74k | — | ~363 | Automated safety check: Notes | MIT | |
| OmniRoute Model Catalog CLIdiegosouzapw/OmniRoute | 74k | — | ~554 | Automated safety check: Pass | MIT | |
| Model Usageopenclaw/openclaw | 392k | 1 repos | ~637 | Automated safety check: Pass | MIT |
Similar skills
Model Bank Metadata
lobehub/lobehub
Fills and maintains the knowledgeCutoff, family and generation fields on model cards in LobeHub's model bank, from a single new model up to repo-wide backfills.
Harness Threat Model
ruvnet/ruflo
Enterprise-review-grade threat model from harness threat-model <path.
OmniRoute Model Catalog CLI
diegosouzapw/OmniRoute
Lists and manages AI models from the OmniRoute command line: browse a provider's catalog, search it, and add, edit, remove or test-add models.
Model Usage
openclaw/openclaw
Summarize CodexBar local cost logs by model for Codex or Claude, including current or full breakdowns.
Threat Modeling
sickn33/agentic-awesome-skills
Conduct threat modeling using STRIDE methodology. An agent skill from sickn33/agentic-awesome-skills.
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 Eccv Review Process
What does Eccv Review Process do?
A skill your agent uses when modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions, the 2026 reviewer-duty enforcement that desk-rejects authors…. Eccv Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions, the 2026 reviewer-duty enforcement that desk-rejects authors of late or LLM-written reviews, rebuttal-to-AC-discussion dynamics, and what the ECVA-run, Springer-published structure means for outcomes.
When should I use Eccv Review Process?
Eccv Review Process fits situations like: modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions; the 2026 reviewer-duty enforcement that desk-rejects authors of late; LLM-written reviews; rebuttal-to-AC-discussion dynamics.
How do I install Eccv Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eccv-review-process -a claude-code`. Or copy the skill folder (ECCV-Skills/skills/eccv-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/eccv-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Eccv Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eccv-review-process -a codex`. Or copy the skill folder (ECCV-Skills/skills/eccv-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/eccv-review-process in your project. Codex loads it when a task matches its description.
Can I use Eccv 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 eccv-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/eccv-review-process, .gemini/skills/eccv-review-process, .github/skills/eccv-review-process and .opencode/skills/eccv-review-process in your project.
What does Eccv Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Eccv Review Process is instructions for the agent only.
Does Eccv 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 Eccv 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 Eccv Review Process use?
Eccv 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 Eccv Review Process use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 Eccv Review Process?
Skills that share tags, products or a category with Eccv Review Process: OmniRoute Model Catalog (diegosouzapw/OmniRoute, 74k stars), Model Bank Metadata (lobehub/lobehub, 83k stars), Harness Threat Model (ruvnet/ruflo, 74k stars) and OmniRoute Model Catalog CLI (diegosouzapw/OmniRoute, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eccv Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.