本文へ移動
cccskills
無料GitHub で公開

aistats-writing-style

Use when revising an AISTATS paper for concise AI-statistics framing, theorem-and-experiment clarity, 8-page two-column compression, double-blind wording, reproducibility clarity, statistically careful claims, and assumption-labeling discipline that survives statistician reviewers.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

AISTATS Writing Style

Use this when revising the main paper. AISTATS papers need compact statements of why a statistical or ML contribution matters and enough detail for technical validation.

Revision rules

  • Put the AI/statistics contribution in the first page: problem, gap, method or theorem, evidence, and why existing methods are insufficient.
  • Make assumptions explicit. AISTATS reviewers are sensitive to hidden distributional, asymptotic, optimization, or data-generating assumptions.
  • Pair every major claim with either proof structure, simulation design, empirical table, or reproducibility detail.
  • Use the 8-page body for core logic; move long derivations, extra simulations, and extended ablations to the appendix without making the main paper unintelligible.
  • Avoid overclaiming empirical wins when differences are small or variance is unreported.
  • Maintain double-blind style in self-citations, prior code references, acknowledgements, funding, and artifact descriptions.

Theorem-presentation discipline

  • Number assumptions and cite them by label inside every theorem statement; AISTATS readers audit assumption flows the way software reviewers audit imports.
  • Give each major theorem a proof sketch in the body; the appendix proof supports the sketch but never replaces it.
  • Keep problem-dependent constants visible or explicitly deferred; silently absorbing dimension or condition numbers into O-notation is a standing statistician complaint.
  • Define notation once in one location — two-column pages punish redundant redefinition.
  • Phrase remarks after theorems as interpretation, not as extra unproved claims; AISTATS reviewers treat every declarative sentence near a theorem as something they may verify.
  • When a result is conjectured or only empirically supported, label it so; mixing proved and observed statements in one paragraph is a credibility leak at this venue.

Sentence-level rewrites

Draft patternAISTATS-safe rewrite
"Our method significantly outperforms...""reduces mean error by X (SE Y) over Z seeded runs"
"Under mild conditions...""Under Assumptions 1-3 (boundedness, ...)"
"It is easy to see that...""By Lemma 2 and the triangle inequality..."
"Achieves state-of-the-art..."Claim scoped to the regimes actually tested

Vignette: compressing into eight two-column pages

A draft with three theorems, six figures, and a sprawling related-work section: keep all theorem statements, one sketch each, and the two decision-critical figures (the rate plot and the coverage plot); compress related work into contribution contrasts; move secondary lemmas and four figures to the appendix with explicit forward references. The test of a good cut: a reviewer should reconstruct the whole argument without ever opening the supplement.

Output format

[Writing diagnosis] clear / under-justified / overclaimed / overloaded
[First-page fix] <new framing>
[Claim discipline] <claim -> proof/experiment/limitation>
[Compression cuts] <move/delete/merge>
[Anonymity edits] <phrases to rewrite>

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

brycewang-stanford のスキルをすべて見る

このスキルの問題を報告する