Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计异常

icml-reviewericml 审稿人

Agent Skill

icml-reviewer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,885

周安装

77

GitHub Stars

149

下载量

604
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:icml-reviewer(icml 审稿人)
来源仓库:https://github.com/sundial-org/skills
仓库路径:skills/icml-reviewer
安装命令:
npx skills add https://github.com/sundial-org/skills --skill icml-reviewer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sundial-org/skills --skill icml-reviewer

简介

用于快速查找、检索和筛选相关信息,支持关键词和场景驱动的内容定位。

  • 适合在学术或研究场景中提供候选结果,辅助决策参考。
  • 需结合具体任务目标设定检索策略,避免盲目扩大搜索范围。
  • 可通过 npx 命令从指定 GitHub 仓库安装并集成到宿主环境。
  • 使用前建议检查仓库更新频率和维护者信息,确保数据时效性。

SKILL.md

ICML Paper Reviewer

Enables rigorous review of ML research papers following official ICML guidelines.

Workflow

Step 1: Input Analysis & Mode Selection

Determine input type:

  • Complete paper: PDF/text with abstract, methodology, experiments, results → Full Review Mode
  • Incomplete document: Missing major sections, labeled draft/proposal, or user indicates early stage → Early-Stage Feedback Mode
  • Code repository: User points to folder/repo path → Repository Review Mode

For complete papers, extract: title, abstract, main claims, methodology, experiments, results. Identify paper type: theoretical, methodological, algorithmic, empirical, bridge paper, or application-driven.

For code repositories, first explore: read README, scan code structure, find experiment scripts/results, identify the research question and what's implemented.

Step 2: Prior Work Grounding (Critical - All Modes)

This step applies to ALL input types. Grounding in reality is essential for any meaningful feedback.

  1. Generate 3-5 search queries based on the research topic: benchmarks/baselines, same problem, related techniques
  2. Use WebSearch to find recent arXiv papers and published work
  3. Fetch abstracts of 5-10 most relevant papers
  4. Critically synthesize:

- What specific claims in this paper are already addressed by prior work? - What are the actual quantitative improvements over recent baselines? - Are claimed "novelties" actually novel given the literature? - What gaps truly exist vs. what the authors claim exists?

Critical mindset:

  • Your job is to verify claims against reality, not accept them at face value
  • Most papers overclaim—your review should ground their contributions in what the literature actually shows
  • Default to skepticism: Assume claims are overstated until proven otherwise by evidence
  • Authors have selection bias toward their own work; you represent the community's interests
  • Be the critical voice that ensures published work actually advances the field

Then proceed to mode-specific evaluation.


Full Review Mode (Complete Papers)

Step 3: Systematic Evaluation

Evaluate across 7 dimensions (see references/evaluation-criteria.md). Default to skepticism—require strong evidence to score highly.

DimensionKey Questions (Answer with Literature Evidence)
OriginalityIs this truly novel given recent work X, Y, Z? What specific aspects are incremental vs. novel?
ImportanceWhy does this problem matter? What's the real-world impact? Who will care?
Claims SupportDo experiments actually prove the claims? What alternative explanations exist?
Experimental SoundnessAre baselines from 2023+? Are comparisons fair? What's missing?
ClarityCan I reproduce this from the paper? Are claims precisely stated?
Community ValueWill this change how people work? Or just add noise?
Prior Work ContextAre comparisons accurate? What recent work (last 2 years) is missing?

Evaluation mindset:

  • Start from neutral and require evidence to move up or down
  • Compare every claim against what you found in the literature search
  • Most papers are incremental—high originality scores are rare
  • Weak baselines or missing comparisons are critical flaws, not minor issues

Step 4: Critical Cross-Check Against Literature

Before writing the review, explicitly verify:

  1. Baselines check: List baselines used in paper. List baselines from your literature search of adjacent papers. What's missing?
  2. Methodology check: How do 2-3 adjacent papers approach this problem? Does this paper follow similar methodology? If not, why not?
  3. Claims check: List main claims. For each, cite specific evidence from experiments or proofs. If insufficient, note it.
  4. Citations check: Which papers from your search are cited? Which are missing? Why?
  5. Novelty check: List claimed novelties. For each, cite specific prior work that does or doesn't do this.

This step is not optional. Your review must reference specific findings from your literature search.

Step 5: Generate Review

Follow the ICML review form (see references/review-template.md):

  1. Summary - Neutral, factual (should not be disputed by authors)
  2. Claims and Evidence - Are claims supported? Compare to what literature shows
  3. Relation to Prior Work - Proper context? Missing citations? List specific missing papers
  4. Strengths - Specific and substantive, compared to standards in adjacent work
  5. Weaknesses - Constructive, explain severity, cite specific literature for comparison
  6. Questions for Authors - Numbered, explain impact on evaluation
  7. Minor Issues - Typos, suggestions
  8. Overall Recommendation - 1-5 scale with justification grounded in literature comparison
  9. Confidence Score - 1-5 scale

Step 6: Quality Check

  • Verify all claims in review are substantiated
  • Ensure constructive tone
  • Check specificity of strengths/weaknesses
  • Confirm questions are actionable

Key Principles

Be Rigorous AND Constructive

Your primary duty is to the research community—publishing weak papers dilutes the literature.

  • Be honest: Don't inflate scores to be nice. If baselines are weak, say so clearly.
  • Be specific: Always cite which literature contradicts or supports claims.
  • Be fair: Criticism should be substantiated by evidence or literature.
  • Be actionable: Tell authors exactly what would fix the issues.

"Review the papers of others as you would wish your own to be reviewed"—with rigor, honesty, and specific feedback grounded in the literature.

Be Specific

Bad: "The experiments are weak" Good: "Experiments compare only against [X] from 2019, but recent baselines [Y] (2024) and [Z] (2024) should be included."

Fair Novelty Assessment

Originality may arise from: creative combinations, new domains, removing restrictive assumptions, novel datasets, new problem formulations.

But: Most claimed novelty is actually incremental. Verify against literature before accepting novelty claims.

Score Calibration

Use this reference frame:

  • 5s are rare: Reserve for papers that will clearly influence the field
  • 4s are uncommon: Solid papers with rigorous execution and clear contributions
  • 3s are common: Papers with merit but significant limitations
  • 2s are common: Incremental work or work with major methodological issues
  • 1s indicate fundamental problems: Wrong results, no contribution, or severe ethical issues

If you find yourself giving mostly 4s and 5s, you're likely being too generous. Re-calibrate against what the literature shows is standard.

Application-Driven Papers

For application-driven ML: methods should fit real-world constraints, non-standard datasets acceptable if documented, compare against domain baselines.

Rating Scales

Overall (1-5): Use the full range. Most papers should be 2-3.

  • 5 (Strong Accept): Significant contribution, will be influential, no major flaws
  • 4 (Accept): Solid contribution, rigorous execution, minor issues only
  • 3 (Weak Accept): Contribution exists but limited; or good idea with execution flaws
  • 2 (Weak Reject): Incremental contribution insufficient for venue; or significant methodological issues
  • 1 (Reject): Fundamental flaws, not ready, or no meaningful contribution

Red flags that should lower scores:

  • Baselines older than 2 years (unless explicitly justified)
  • Missing comparisons to obvious related work from literature search
  • Claims not directly supported by presented experiments
  • Novelty claims contradicted by prior work

Confidence (1-5): 5=Expert/certain, 4=Confident, 3=Fairly confident, 2=Uncertain, 1=Not in area


Early-Stage Feedback Mode

Use this mode for incomplete drafts, research proposals, or code repositories. Focus shifts from "accept/reject evaluation" to "constructive guidance on how to make this publishable."

After completing Steps 1-2 (input analysis and prior work grounding), proceed here.

Step 3: Generate Formative Feedback

Use the Early-Stage Feedback Template (see references/review-template.md). No numerical scores—focus on constructive guidance.

For code repositories, additionally address:

  • Code quality and organization
  • Experiment design and reproducibility
  • What's missing for a paper (baselines, ablations, analysis)

References

  • references/evaluation-criteria.md - Detailed criteria for each dimension
  • references/review-template.md - Full template with examples
  • references/common-issues.md - Common paper issues to identify

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.37%
按下载量换算208

Claude

29%
按下载量换算175

Cursor

17.97%
按下载量换算109

Gemini CLI

9.25%
按下载量换算56

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills