Use when revising an AAAI manuscript for broad-AI-audience fit, a first-page contribution statement legible to non-specialist Phase-1 reviewers, two-column readability, concise novelty claims, reproducibility-checklist alignment, hedged limitations and ethics, and policy-aware framing of AI-system and capability claims.
Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.
读取 https://funcoding.ai/skills/brycewang-stanford/awesome-journal-skills/aaai-writing-style/install.md ，按里面的步骤帮我安装这个 Skill。
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.
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 |
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.
[AAAI fit sentence] <one sentence>
[Contribution type] method / theory / system / benchmark / dataset / evaluation / social impact
[First-page fixes] <problem, method, evidence, limitation>
[Checklist alignment] pass / needs revision
[Overclaim risks] <claims to narrow or evidence to add>
anthropics/skills180kUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Docs & office
anthropics/skills180kAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.
Docs & office
anthropics/skills180kGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Docs & office
anthropics/skills180kUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Docs & office
anthropics/skills180kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.
Docs & office
anthropics/skills180kCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Docs & office