본문으로 건너뛰기
cccskills
무료GitHub에 공개

aaai-submission

Use when auditing an AAAI main technical track submission for OpenReview readiness, double-blind anonymity, page limits, reproducibility checklist, supplementary material, author limits, multiple-submission policy, and AAAI AI-use policy compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md6.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

AAAI Submission

Use this for an AAAI main technical track submission audit. Reopen the current conference page, Author Kit, CFP, submission instructions, review process page, supplementary-material page, and author policies before giving deadline-ready advice.

Submission audit

  • Confirm the target track: Main Track, AI for Social Impact, AI Alignment, or another AAAI program. Track-specific rules can differ.
  • Verify OpenReview account/profile readiness, conflicts, author list, subject areas, and submission metadata before the abstract and paper deadlines.
  • Check the current AAAI author kit. AAAI-27 submissions use AAAI two-column camera-ready style and US Letter PDF, with a main PDF of at most 9 pages whose pages 8-9 are references only — 7 pages of non-reference content. Any ethical statement counts inside those 7 pages.
  • Confirm double-blind compliance in the PDF, file names, references to prior work, supplement, code/data, and metadata. Omit acknowledgments in the review version.
  • Upload the reproducibility checklist in its own submission field, not inside the paper PDF — AAAI-27 moved it out of the document, and a checklist buried after the references is now a missing checklist.
  • Enforce the author submission limit and author-change rules. AAAI-27 limits each author to 10 combined main-technical-track submissions (the AI Alignment and AI for Social Impact special tracks are excluded from that count), allows no author additions after submission, and permits modifications only until the full-paper deadline.
  • Check multiple-submission compliance. An AAAI submission under review cannot simultaneously be under review at another archival venue, and AAAI-27 names the patterns it treats as violations: cosmetic re-submission, "thin slicing" one contribution across papers, splitting results by method/dataset/domain, and obfuscated or "alternative universe" duplicates. Papers sharing authors may be assessed together for novelty.
  • Apply the current AAAI AI-use policy: editing/polishing author-written text may be allowed, but LLM-generated manuscript text, AI authorship, and AI-generated citations are policy risks.

Blocking risks

  • Over-limit technical content or malformed PDF.
  • Missing reproducibility checklist.
  • Identity leakage in paper, supplement, links, code, data, or prior-work citations.
  • Author added after the allowed window.
  • Concurrent archival submission.
  • Web pointers to mutable supplementary material.
  • Policy-violating LLM-generated text, hallucinated references, or plagiarism.

Summary-reject screen

AAAI's large reviewer pool and high volume mean a desk-level or Phase-1 cut is the most likely way to lose, so screen for the mechanical failures first.

CheckFast-fail triggerWhere it bites
Page limittechnical content over the capdesk return
Anonymityauthor name in PDF, code, or metadatapolicy reject
Checklistmissing or contradictoryPhase-1 distrust
Dual submissionconcurrent archival venueethics reject

Pre-deadline evidence packet

Build a single review-version packet before the abstract deadline, then refresh it before final submission. The packet is not a substitute for the official instructions; it is a way to make the submission audit reproducible and to keep late fixes from creating new policy problems.

Packet itemWhat to captureFailure it prevents
Policy snapshotcurrent conference page, Author Kit, submission instructions, supplementary-material rules, and AI-use policy checked datesapplying a closed cycle's facts to the open one
PDF proofpage count, paper size, style file, checklist placement, font/figure warnings, and metadata scrub resultdesk return for formatting or anonymity
Author ledgerOpenReview profiles, conflicts, subject areas, author-limit count, and author-list freeze statusprofile conflict, over-limit author, late author change
Supplement ledgerevery appendix, multimedia, code/data ZIP, README, license note, and anonymous link policy decisionmutable web pointer or identity leak
Ethics ledgerdual-submission status, human-subjects/data constraints, AI-use disclosure, plagiarism/citation checkpolicy reject after submission

For each item, record the evidence path and the person who can fix it. If a rule is uncertain, mark it as "requires current chair/author-kit confirmation" instead of guessing.

Anonymity sweep order

Run anonymity checks in a fixed order so fixes do not reintroduce leaks:

  1. PDF text: names, affiliations, acknowledgments, grants, self-identifying project names, and obvious self-citations.
  2. PDF metadata: title, author, producer, comments, embedded attachments, and file name.
  3. References: prior work phrased as "our previous" or "submitted to" when blind citation would be required.
  4. Supplement: ZIP names, directory names, notebooks, comments, plots, data paths, license files, and executable logs.
  5. External references: GitHub, project pages, anonymous archives, videos, demos, or issue trackers.
  6. OpenReview metadata: author list, conflicts, subject areas, institutional hints in abstract or keywords.

The output should separate "must fix before submission" from "acceptable but document why." Do not rely on a single manual skim; use PDF metadata tools, archive listing, and text search when available.

Worked vignette

A robotics-learning team has 7 strong technical pages but left an acknowledgments line and a GitHub URL with their lab name in the supplement. The audit flags anonymity as the highest summary-reject risk: the fix order is strip the acknowledgment, replace the link with an anonymous archive, scrub ZIP metadata, then re-export and re-run the anonymity sweep before the paper deadline.

Output format

[AAAI readiness] Ready / Needs fixes / Not ready
[Track] Main / AI for Social Impact / AI Alignment / other
[Blocking checks] <page/anonymity/checklist/supplement/author-limit/dual-submission/AI-policy>
[Highest summary-reject risk] <one issue>
[Fix order] <ordered fixes before submission>

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.3천2026년 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.3천2026년 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.3천2026년 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.3천2026년 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.3천2026년 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.3천2026년 9월 27일 업데이트

brycewang-stanford의 스킬 모두 보기

이 스킬의 문제 신고