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, and final-week submission sequencing.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aistats-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Submission audit
- Blocking risks
- Desk-reject and triage table
- Final-week sequence for a theory-plus-experiments paper
- Format anchors
- Output format
What does the aistats-submission skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aistats-submission --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.