/aistats-related-work
Use when positioning an AISTATS submission against AI, machine-learning, statistics, and uncertainty literature, including arXiv preprints, workshop versions, concurrent submissions, prior conference versions, PMLR archival status, and the two-community citation coverage that
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aistats-related-work --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/aistats-related-work
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when positioning an AISTATS submission against AI, machine-learning, statistics, and uncertainty literature, including arXiv preprints, workshop versions, concurrent submissions, prior conference versions, PMLR archival status, and the two-community citation coverage that
SKILL.md
aistats-related-work.SKILL.mdname: aistats-related-work
description: Use when positioning an AISTATS submission against AI, machine-learning, statistics, and uncertainty literature, including arXiv preprints, workshop versions, concurrent submissions, prior conference versions, PMLR archival status, and the two-community citation coverage that AISTATS reviewers expect.
AISTATS Related Work
Use this to audit novelty and eligibility. Reopen the current CFP for dual-submission, anonymity, and prior-publication rules before advising authors.
Positioning checks
- Separate statistical novelty from engineering improvement: new estimator, bound,
inference procedure, optimization analysis, uncertainty method, or empirical insight.
- Compare to both ML conference work and statistics literature; AISTATS reviewers often
expect both communities to be represented.
- Treat PMLR, journal, and formal conference proceedings as archival unless current rules say
otherwise.
- Cite arXiv and workshop versions in a way that preserves double-blind review. Do not point
reviewers to identity-revealing pages.
- Explain overlap with any concurrent or prior version, and do not submit duplicate archival
work.
- Use related work to sharpen what is new: assumption weakening, finite-sample behavior,
computational efficiency, uncertainty calibration, robustness, or empirical regime.
Two-community coverage table
| Literature lane | Typical sources | What AISTATS reviewers check | |---|---|---| | ML conferences | NeurIPS, ICML, ICLR, UAI, COLT, prior AISTATS volumes in PMLR | Whether the nearest ML method is compared or explicitly distinguished | | Statistics journals | Annals of Statistics, JMLR, JASA, Biometrika, EJS | Whether classical estimators and known rates are acknowledged | | Applied statistical fields | Econometrics, biostatistics, epidemiology | Whether identification and inference assumptions follow standard usage |
A bibliography citing only ML venues tells a statistician reviewer that known statistical results may be getting rediscovered — a recognizable AISTATS reject pattern that no amount of benchmark strength repairs.
Positioning vignette
Imagine the paper proposes a variance-reduced off-policy evaluation estimator with an asymptotic normality result. Its nearest neighbors: a NeurIPS estimator with no inference guarantee, a JASA semiparametric efficiency bound, and a prior AISTATS paper with a slower rate. The novelty sentence should name all three contrasts — inference where the ML line had none, computational tractability where the statistics line stayed abstract, and a sharper rate than the direct predecessor.
Concurrent-work judgment calls
- Independently concurrent arXiv work: cite neutrally, state the technical difference, and
avoid priority claims that reviewers cannot verify.
- Your own workshop version: typically non-archival and citable, but verify against the
current CFP wording and keep the citation phrased so double-blind review survives.
- When in doubt about archival status of a venue, declare the overlap in the submission form
rather than gambling on a chair's interpretation.
Output format
[Eligibility] clear / needs declaration / risky
[Closest literatures] <ML/statistics/application>
[Nearest 3 works] <work -> distinction>
[Archival-overlap risk] <none/issues>
[Novelty sentence] <AISTATS-ready contribution contrast>
Read more
name: aistats-related-work description: Use when positioning an AISTATS submission against AI, machine-learning, statistics, and uncertainty literature, including arXiv preprints, workshop versions, concurrent submissions, prior conference versions, PMLR archival status, and the two-community citation coverage that AISTATS reviewers expect.
AISTATS Related Work
Use this to audit novelty and eligibility. Reopen the current CFP for dual-submission, anonymity, and prior-publication rules before advising authors.
Positioning checks
- Separate statistical novelty from engineering improvement: new estimator, bound,
inference procedure, optimization analysis, uncertainty method, or empirical insight.
- Compare to both ML conference work and statistics literature; AISTATS reviewers often
expect both communities to be represented.
- Treat PMLR, journal, and formal conference proceedings as archival unless current rules say
otherwise.
- Cite arXiv and workshop versions in a way that preserves double-blind review. Do not point
reviewers to identity-revealing pages.
- Explain overlap with any concurrent or prior version, and do not submit duplicate archival
work.
- Use related work to sharpen what is new: assumption weakening, finite-sample behavior,
computational efficiency, uncertainty calibration, robustness, or empirical regime.
Two-community coverage table
| Literature lane | Typical sources | What AISTATS reviewers check | |---|---|---| | ML conferences | NeurIPS, ICML, ICLR, UAI, COLT, prior AISTATS volumes in PMLR | Whether the nearest ML method is compared or explicitly distinguished | | Statistics journals | Annals of Statistics, JMLR, JASA, Biometrika, EJS | Whether classical estimators and known rates are acknowledged | | Applied statistical fields | Econometrics, biostatistics, epidemiology | Whether identification and inference assumptions follow standard usage |
A bibliography citing only ML venues tells a statistician reviewer that known statistical results may be getting rediscovered — a recognizable AISTATS reject pattern that no amount of benchmark strength repairs.
Positioning vignette
Imagine the paper proposes a variance-reduced off-policy evaluation estimator with an asymptotic normality result. Its nearest neighbors: a NeurIPS estimator with no inference guarantee, a JASA semiparametric efficiency bound, and a prior AISTATS paper with a slower rate. The novelty sentence should name all three contrasts — inference where the ML line had none, computational tractability where the statistics line stayed abstract, and a sharper rate than the direct predecessor.
Concurrent-work judgment calls
- Independently concurrent arXiv work: cite neutrally, state the technical difference, and
avoid priority claims that reviewers cannot verify.
- Your own workshop version: typically non-archival and citable, but verify against the
current CFP wording and keep the citation phrased so double-blind review survives.
- When in doubt about archival status of a venue, declare the overlap in the submission form
rather than gambling on a chair's interpretation.
Output format
[Eligibility] clear / needs declaration / risky [Closest literatures] <ML/statistics/application> [Nearest 3 works] <work -> distinction> [Archival-overlap risk] <none/issues> [Novelty sentence] <AISTATS-ready contribution contrast>
Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证
Other skills on awesome-journal-skills.
- /aaai-artifact-evaluation
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
Open skill - /aaai-author-response
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round
Open skill - /aaai-camera-ready
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and
Open skill - /aaai-experiments
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and
Open skill - /aaai-related-work
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a
Open skill - /aaai-reproducibility
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that
Open skill

