--- name: AAAI Writing Style slug: aaai-writing-style category: Writing description: Helps revise AAAI manuscripts to be readable by a broad AI audience, with clear first-page contributions, two-column readability, and alignment with reproducibility and ethical guidelines. github: "https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/AAAI-Skills/skills/aaai-writing-style" language: Stata stars: 880 forks: 106 install: "git clone https://github.com/brycewang-stanford/Awesome-Journal-Skills" added: 2026-07-20T06:49:37.805Z last_synced: 2026-07-29T06:37:39.655Z canonical_url: "https://dirskills.com/skills/aaai-writing-style" --- # AAAI Writing Style Helps revise AAAI manuscripts to be readable by a broad AI audience, with clear first-page contributions, two-column readability, and alignment with reproducibility and ethical guidelines. **Install:** `git clone https://github.com/brycewang-stanford/Awesome-Journal-Skills` ## README # AAAI Writing Style Use this to make a technically sound draft readable to a broad AI program committee. AAAI rewards clear AI contribution, not only subfield-specific benchmark wins. ## AAAI framing - State the AI problem, the new capability or insight, and the evidence in the first page. - Make clear whether the contribution is method, theory, system, benchmark, dataset, evaluation, human-AI interaction, social impact, or alignment. - Explain why the result matters outside a single dataset or implementation. - Keep claims aligned with the reproducibility checklist and supplementary evidence. - Discuss limitations and ethical considerations when the method affects people, safety, privacy, fairness, security, or social impact. ## Two-column readability - Use figures and tables as decision aids, not decoration. - Keep notation lightweight and define it near first use. - Use compact related-work contrasts instead of long literature catalogues. - Make the Phase 1 summary easy: problem, method, evidence, limitation, checklist compliance. - Avoid unsupported "general intelligence", "human-level", or "safe" claims. ## Reading the paper as a Phase-1 reviewer A non-specialist on AAAI's broad committee gives the first page a few minutes and decides whether the paper is worth deeper reading. Write so that a planning or KR reviewer can summarize your learning contribution, and vice versa. Audit the opening against what that reader needs to extract fast. | First-page question | Reviewer extracts | Failure symptom | | --- | --- | --- | | What is the problem | one AI task statement | jargon with no anchor | | What is new | the single contribution | a list, no headline | | Why believe it | evidence in one line | "see Section 6" only | | What are the limits | scope and caveat | silence or overclaim | ## Phrasing fixes that survive AAAI review - Replace "we achieve state of the art" with the specific delta and the setting it holds in. - Replace bare "safe" or "human-level" with a measured, scoped statement the evidence supports. - Replace a long related-work catalogue with two or three sharp contrasts a non-specialist can follow. - Tie every strong claim back to a checklist answer so rigor and prose agree. ## Worked vignette A multi-agent paper opens with three paragraphs of game-theory notation before naming its contribution. A vision reviewer cannot find the AI claim and is likely to stop. The fix rewrites sentence one as the problem, sentence two as the new coordination mechanism, sentence three as the one-line evidence, and a final clause scoping the result to the studied setting, all on page one. ## Output format ```text [AAAI fit sentence] [Contribution type] method / theory / system / benchmark / dataset / evaluation / social impact [First-page fixes] [Checklist alignment] pass / needs revision [Overclaim risks] ```