/aistats-topic-selection
Use when deciding whether a project is a strong AISTATS fit, comparing AISTATS with NeurIPS, ICML, ICLR, UAI, COLT, JMLR, statistics journals, or application venues, identifying the statistical primitive of the contribution, and sharpening the AI-statistics framing before
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aistats-topic-selection --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-topic-selection
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when deciding whether a project is a strong AISTATS fit, comparing AISTATS with NeurIPS, ICML, ICLR, UAI, COLT, JMLR, statistics journals, or application venues, identifying the statistical primitive of the contribution, and sharpening the AI-statistics framing before
SKILL.md
aistats-topic-selection.SKILL.mdname: aistats-topic-selection
description: Use when deciding whether a project is a strong AISTATS fit, comparing AISTATS with NeurIPS, ICML, ICLR, UAI, COLT, JMLR, statistics journals, or application venues, identifying the statistical primitive of the contribution, and sharpening the AI-statistics framing before writing begins.
AISTATS Topic Selection
Use this before writing. AISTATS is strongest for work at the intersection of artificial intelligence, machine learning, and statistics, especially when statistical reasoning is not merely an evaluation detail.
Fit test
- Prefer AISTATS when the contribution advances statistical foundations, inference,
uncertainty, causal or probabilistic modeling, learning theory, optimization, or empirical methodology with clear AI/ML relevance.
- Route to ICML, NeurIPS, or ICLR if the main contribution is broad ML systems, representation
learning, scaling, or deep learning practice with limited statistical novelty.
- Route to UAI if the contribution is primarily uncertainty, probabilistic graphical models,
causality, decision making under uncertainty, or Bayesian reasoning.
- Route to COLT if the contribution is mainly formal learning theory and the empirical story
is secondary.
- Route to a statistics journal when the work needs journal-length exposition, extensive
proofs, or a statistics audience more than an AI conference audience.
- Check early whether the result can be made convincing in an 8-page submission body.
Fit signal table
| Signal in the project | AISTATS reading | |---|---| | Consistency, minimax rate, regret, or coverage result paired with experiments | Core fit — the house genre | | Bayesian, causal, kernel, or high-dimensional methodology with guarantees | Core fit | | Deep architecture with strong benchmarks but thin theory | Better served at NeurIPS, ICML, or ICLR | | Pure theory with no plausible experiment | COLT or a statistics journal | | Probabilistic reasoning without a learning angle | UAI or a statistics venue |
Vignette: where a debiased estimator goes
A project delivers a debiased lasso variant with valid confidence intervals in high dimensions and simulations confirming coverage. AISTATS reading: strong fit — an inference guarantee plus validating experiments is exactly what this venue rewards. Strip the inference theory and keep only prediction benchmarks, and the same project belongs at a general ML venue; grow it into journal-length asymptotic refinements, and Annals of Statistics or JMLR becomes the better home.
Sharpening moves before committing
- Name the statistical primitive: estimator, test, bound, posterior, or identification
result. If no primitive exists, the AISTATS framing does not exist either.
- Verify the proof load fits the format: the appendix may be long, but the 8-page body must
carry the argument's spine on its own.
- Confirm the experiments can be designed to test the theory rather than merely accompany it;
decoration-only benchmarks are a quiet fit failure here.
- Topic emphasis drifts between cycles; scan the current CFP subject-area list before final
routing.
Output format
[Fit] strong AISTATS / possible AISTATS / better elsewhere
[Best venue] AISTATS / NeurIPS / ICML / ICLR / UAI / COLT / journal / other
[Contribution sentence] <one sentence>
[Top rejection risk] <novelty/statistics/evidence/clarity/scope>
[Next action] <theory, experiment, framing, or venue switch>
Read more
name: aistats-topic-selection description: Use when deciding whether a project is a strong AISTATS fit, comparing AISTATS with NeurIPS, ICML, ICLR, UAI, COLT, JMLR, statistics journals, or application venues, identifying the statistical primitive of the contribution, and sharpening the AI-statistics framing before writing begins.
AISTATS Topic Selection
Use this before writing. AISTATS is strongest for work at the intersection of artificial intelligence, machine learning, and statistics, especially when statistical reasoning is not merely an evaluation detail.
Fit test
- Prefer AISTATS when the contribution advances statistical foundations, inference,
uncertainty, causal or probabilistic modeling, learning theory, optimization, or empirical methodology with clear AI/ML relevance.
- Route to ICML, NeurIPS, or ICLR if the main contribution is broad ML systems, representation
learning, scaling, or deep learning practice with limited statistical novelty.
- Route to UAI if the contribution is primarily uncertainty, probabilistic graphical models,
causality, decision making under uncertainty, or Bayesian reasoning.
- Route to COLT if the contribution is mainly formal learning theory and the empirical story
is secondary.
- Route to a statistics journal when the work needs journal-length exposition, extensive
proofs, or a statistics audience more than an AI conference audience.
- Check early whether the result can be made convincing in an 8-page submission body.
Fit signal table
| Signal in the project | AISTATS reading | |---|---| | Consistency, minimax rate, regret, or coverage result paired with experiments | Core fit — the house genre | | Bayesian, causal, kernel, or high-dimensional methodology with guarantees | Core fit | | Deep architecture with strong benchmarks but thin theory | Better served at NeurIPS, ICML, or ICLR | | Pure theory with no plausible experiment | COLT or a statistics journal | | Probabilistic reasoning without a learning angle | UAI or a statistics venue |
Vignette: where a debiased estimator goes
A project delivers a debiased lasso variant with valid confidence intervals in high dimensions and simulations confirming coverage. AISTATS reading: strong fit — an inference guarantee plus validating experiments is exactly what this venue rewards. Strip the inference theory and keep only prediction benchmarks, and the same project belongs at a general ML venue; grow it into journal-length asymptotic refinements, and Annals of Statistics or JMLR becomes the better home.
Sharpening moves before committing
- Name the statistical primitive: estimator, test, bound, posterior, or identification
result. If no primitive exists, the AISTATS framing does not exist either.
- Verify the proof load fits the format: the appendix may be long, but the 8-page body must
carry the argument's spine on its own.
- Confirm the experiments can be designed to test the theory rather than merely accompany it;
decoration-only benchmarks are a quiet fit failure here.
- Topic emphasis drifts between cycles; scan the current CFP subject-area list before final
routing.
Output format
[Fit] strong AISTATS / possible AISTATS / better elsewhere [Best venue] AISTATS / NeurIPS / ICML / ICLR / UAI / COLT / journal / other [Contribution sentence] <one sentence> [Top rejection risk] <novelty/statistics/evidence/clarity/scope> [Next action] <theory, experiment, framing, or venue switch>
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

