Skip to content
cccskills
FreePublished on GitHub

aistats-supplementary

Use when preparing AISTATS supplementary material, appendices, proof details, code/data archives, simulation scripts, additional tables, and anonymized artifacts under deadline, size, anonymity, and reviewer-discretion constraints, including how to split a theory-plus-experiments paper between body and supplement.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

AISTATS Supplementary

Use this when assembling AISTATS supplementary material. The supplement can support the paper, but the main submission must remain understandable without it.

Supplement structure

  • Put theorem proofs, derivations, extra ablations, simulation details, dataset documentation, and robustness tables in a clean appendix or supplementary manuscript.
  • Put executable assets in a separate archive when current OpenReview forms allow it.
  • Respect the current supplementary deadline. AISTATS 2026 placed supplementary-material submission after the paper deadline but before review.
  • Keep all supplementary files double-blind: no authors, institutions, acknowledgements, private paths, repository owners, grants, or identifying metadata.
  • Do not use the supplement to hide essential motivation, core method description, main theorem statements, or primary empirical results.
  • Verify archives open on a clean machine and contain no credentials, cache directories, large irrelevant files, or hidden OS metadata.

Appendix architecture for proofs

  • Order appendix sections to mirror main-text theorem order; statistician reviewers navigate by theorem number, not by page.
  • Restate each theorem before its proof so the appendix reads standalone without flipping back to the two-column body.
  • Standard partition: notation and assumptions, main proofs, auxiliary lemmas, additional simulations, then real-data details.
  • Keep one proof-sketch paragraph per major theorem in the body itself; an AISTATS submission whose entire argument lives in the supplement reads as unreviewable within the page limit.
  • Cross-reference every appendix table and lemma from the body at least once; orphaned supplement material is invisible to reviewers and wasted under reviewer discretion.
  • If the cycle allows appendices inside the main PDF after the references, confirm against the current instructions whether that or a separate file upload is expected.

What gets opened first

Supplement itemInspection likelihoodPractical implication
Proof of the headline theoremHighPolish it to main-text standard
Extra ablation and robustness tablesMediumReference each one from the body
Code archiveVariable, reviewer discretionThe README must orient a reader in one minute
Raw experiment logsLowInclude for completeness, never rely on them

Vignette: splitting an optimization paper

A submission proving a convergence guarantee for a stochastic mirror-descent variant, plus benchmark plots: the body keeps the theorem, the key lemma, the proof roadmap, and two decision-critical figures; the appendix holds full proofs and step-size sensitivity grids; the archive carries the seeded experiment runner. Nothing decision-critical lives only in the archive, because archive inspection at AISTATS is discretionary.

Output format

[Supplement status] Ready / Needs fixes / Not ready
[Files] <appendix/proofs/code/data/logs>
[Deadline] <current supplement deadline and source>
[Anonymity checks] <passed/issues>
[Main-paper dependency] <what breaks if supplement is ignored>

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 before SPC/AC discussion.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 final public artifact release.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 reproducibility-checklist alignment for Phase-1 survival.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 related-work section legible to non-specialist reviewers.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

See all skills by brycewang-stanford

Report a problem with this skill