aaai-artifact-evaluati…
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without…
Use when preparing the ASE (IEEE/ACM Automated Software Engineering) camera-ready after acceptance or a successful revision, covering systematic de-anonymization, the extra content page, the mandatory Data Availability finalization, the correct IEEE/ACM template and metadata,
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-camera-ready --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ase-camera-readyContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when preparing the ASE (IEEE/ACM Automated Software Engineering) camera-ready after acceptance or a successful revision, covering systematic de-anonymization, the extra content page, the mandatory Data Availability finalization, the correct IEEE/ACM template and metadata,
name: ase-camera-ready description: Use when preparing the ASE (IEEE/ACM Automated Software Engineering) camera-ready after acceptance or a successful revision, covering systematic de-anonymization, the extra content page, the mandatory Data Availability finalization, the correct IEEE/ACM template and metadata, permanentized artifact links, and dual IEEE-Xplore/ACM-DL production checks.
Deliver the final version after an Accept or a met Revision. ASE camera-ready has three jobs that trip authors up: **de-anonymize systematically**, **spend the extra content page well**, and pass **dual production checks** — because the paper is indexed in **both IEEE Xplore and the ACM Digital Library**, the metadata and template must satisfy the sponsoring publisher's pipeline. Every requirement below is a one-cycle snapshot; reopen the current camera-ready instructions first.
Reverse every anonymization introduced for double-anonymous review — and only those:
[Authors] real names, affiliations, ORCID, and corresponding-author info restored. [Tool] real tool name restored consistently throughout (it was anonymized at submission). [Repository] Data Availability link points to the real, permanent archive (not the anon service). [Self-cites] third-person self-citations relaxed to normal form where appropriate. [Acks] funding, grants, and collaborators added (absent from the anonymized submission). [Metadata] PDF author/producer fields set correctly; no residual "Anonymous".
Do a final `pdfinfo` / `pdftotext` pass to confirm no leftover "Anonymous" and no *new* leak (a funding line that should not be there, a wrong affiliation).
Accepted ASE papers are typically allowed **one additional content page** for revisions. Use it to **incorporate review feedback** — the new baseline, the requested ablation, the clarified construct, the strengthened threats — not to pad. If you received a Revision, the extra page is where the criteria you met become visible in the final paper.
Heritage before submitting camera-ready if you have not already.
`review`/`anonymous` options for the final class options the instructions specify). Because ASE is dual IEEE/ACM sponsored, the required template and the rights/metadata step can differ per edition; **confirm which publisher's pipeline this edition uses** and follow that kit.
the paper.
feeds both IEEE Xplore and the ACM DL records; mismatches cause production delays.
(e.g., an IEEE PDF eXpress-style or ACM validation step, per the edition's instructions).
proceedings surfaces (see `ase-artifact-evaluation`).
[De-anon] authors/affiliations/tool/repo/acks restored; no leftover "Anonymous"; no new leak [Extra page] review feedback incorporated (not padding); met revision criteria visible [Data Avail] permanent DOI archive, resolves, after Conclusions, within budget [Template] correct edition template/class options; rights block pasted [Metadata] title/authors/abstract/keywords/CCS accurate for IEEE Xplore + ACM DL [Production] fonts embedded; figures render; passes the publisher's PDF checker [Badge] artifact badge reflected if earned; DOI matches Data Availability
[Camera-ready status] ready / blocked [De-anonymization] complete? residual "Anonymous" or new leak? [Extra page] feedback incorporated / revision criteria visible? [Data Availability] permanent DOI resolves, within budget? [Template + rights] correct template, rights block, accurate metadata for both proceedings? [Fix queue] <ordered, before the camera-ready deadline>
Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without…
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,…
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance,…
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human…
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across…
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting,…