/aistats-submission
Use when auditing an AISTATS submission for OpenReview readiness, abstract/full-paper deadlines, the 8-page submission body, double-blind anonymity, supplementary material, reproducibility checklist, dual-submission policy, reviewer volunteer requirements, desk-reject triggers,
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aistats-submission --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-submission
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when auditing an AISTATS submission for OpenReview readiness, abstract/full-paper deadlines, the 8-page submission body, double-blind anonymity, supplementary material, reproducibility checklist, dual-submission policy, reviewer volunteer requirements, desk-reject triggers,
SKILL.md
aistats-submission.SKILL.mdname: aistats-submission
description: Use when auditing an AISTATS submission for OpenReview readiness, abstract/full-paper deadlines, the 8-page submission body, double-blind anonymity, supplementary material, reproducibility checklist, dual-submission policy, reviewer volunteer requirements, desk-reject triggers, and final-week submission sequencing.
AISTATS Submission
Use this for an AISTATS paper submission audit. Reopen the current Call for Papers, OpenReview group, style files, FAQ, and proceedings instructions before giving deadline-ready advice.
Submission audit
- Confirm the target is the main AISTATS conference, not a workshop or tutorial.
- Verify OpenReview profiles, conflicts, subject areas, title, abstract, author list, and
reviewer-volunteer obligations before the abstract and full-paper deadlines.
- Apply the current style file without spacing, margin, font, or bibliography hacks.
AISTATS 2026 used 8 pages of main text for submission, excluding references and appendices.
- Submit supplementary material by the current supplement deadline. In 2026 this was a
separate deadline after the main paper deadline, and supplementary uploads were optional but had to remain anonymous.
- Include or complete the reproducibility checklist if the current cycle requires it.
- Enforce double-blind anonymity in paper text, appendix, supplement, code/data, file names,
metadata, repository links, acknowledgements, grants, and self-citations.
- Check concurrent-submission rules and prior-publication status. Do not put the same work
under review at another archival venue when AISTATS forbids it.
Blocking risks
- Late abstract or full-paper upload.
- Overlength main text or modified style.
- Non-anonymized supplement, metadata, repository, or appendix.
- Missing reproducibility checklist or required OpenReview fields.
- Dual submission to another archival venue.
- Unclear statistical evidence, weak baselines, or missing uncertainty analysis.
Desk-reject and triage table
| Trigger | Severity at AISTATS | Repair window | |---|---|---| | Overlength main text | Desk reject | None after the deadline | | Style-file tampering | Desk reject or chair flag | None | | Identity leak in PDF or supplement | Desk reject | None | | Checklist contradicting the paper | Review-stage damage | Only before the deadline | | Theorem assumptions absent from the body | Review-stage damage | Fixable in the writing pass |
Final-week sequence for a theory-plus-experiments paper
1. Freeze theorem statements and renumber assumptions; reviewers cross-reference labels. 2. Regenerate every figure from seeded scripts so supplement and PDF cannot diverge. 3. Fill the checklist against what the paper actually contains, not what is planned. 4. Strip PDF metadata, notebook authorship fields, and repository owner strings. 5. Confirm the OpenReview abstract matches the PDF abstract word for word.
Format anchors
- AISTATS uses a two-column PMLR-style layout; display equations and algorithm blocks that
fit a one-column draft routinely overflow, so compress math early rather than on deadline night.
- The page counts cited above describe the 2026 cycle; treat every number as provisional and
recheck the current Call for Papers before relying on it.
Output format
[AISTATS readiness] Ready / Needs fixes / Not ready
[Blocking checks] <OpenReview/page/anonymity/supplement/reproducibility/dual-submission>
[Statistical-evidence risk] <one issue>
[Desk-reject risk] <one issue>
[Fix order] <ordered fixes before submission>
Read more
name: aistats-submission description: Use when auditing an AISTATS submission for OpenReview readiness, abstract/full-paper deadlines, the 8-page submission body, double-blind anonymity, supplementary material, reproducibility checklist, dual-submission policy, reviewer volunteer requirements, desk-reject triggers, and final-week submission sequencing.
AISTATS Submission
Use this for an AISTATS paper submission audit. Reopen the current Call for Papers, OpenReview group, style files, FAQ, and proceedings instructions before giving deadline-ready advice.
Submission audit
- Confirm the target is the main AISTATS conference, not a workshop or tutorial.
- Verify OpenReview profiles, conflicts, subject areas, title, abstract, author list, and
reviewer-volunteer obligations before the abstract and full-paper deadlines.
- Apply the current style file without spacing, margin, font, or bibliography hacks.
AISTATS 2026 used 8 pages of main text for submission, excluding references and appendices.
- Submit supplementary material by the current supplement deadline. In 2026 this was a
separate deadline after the main paper deadline, and supplementary uploads were optional but had to remain anonymous.
- Include or complete the reproducibility checklist if the current cycle requires it.
- Enforce double-blind anonymity in paper text, appendix, supplement, code/data, file names,
metadata, repository links, acknowledgements, grants, and self-citations.
- Check concurrent-submission rules and prior-publication status. Do not put the same work
under review at another archival venue when AISTATS forbids it.
Blocking risks
- Late abstract or full-paper upload.
- Overlength main text or modified style.
- Non-anonymized supplement, metadata, repository, or appendix.
- Missing reproducibility checklist or required OpenReview fields.
- Dual submission to another archival venue.
- Unclear statistical evidence, weak baselines, or missing uncertainty analysis.
Desk-reject and triage table
| Trigger | Severity at AISTATS | Repair window | |---|---|---| | Overlength main text | Desk reject | None after the deadline | | Style-file tampering | Desk reject or chair flag | None | | Identity leak in PDF or supplement | Desk reject | None | | Checklist contradicting the paper | Review-stage damage | Only before the deadline | | Theorem assumptions absent from the body | Review-stage damage | Fixable in the writing pass |
Final-week sequence for a theory-plus-experiments paper
1. Freeze theorem statements and renumber assumptions; reviewers cross-reference labels. 2. Regenerate every figure from seeded scripts so supplement and PDF cannot diverge. 3. Fill the checklist against what the paper actually contains, not what is planned. 4. Strip PDF metadata, notebook authorship fields, and repository owner strings. 5. Confirm the OpenReview abstract matches the PDF abstract word for word.
Format anchors
- AISTATS uses a two-column PMLR-style layout; display equations and algorithm blocks that
fit a one-column draft routinely overflow, so compress math early rather than on deadline night.
- The page counts cited above describe the 2026 cycle; treat every number as provisional and
recheck the current Call for Papers before relying on it.
Output format
[AISTATS readiness] Ready / Needs fixes / Not ready [Blocking checks] <OpenReview/page/anonymity/supplement/reproducibility/dual-submission> [Statistical-evidence risk] <one issue> [Desk-reject risk] <one issue> [Fix order] <ordered fixes before submission>
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

