/ase-camera-ready
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.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ase-camera-ready
Context 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,
SKILL.md
ase-camera-ready.SKILL.mdname: 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.
ASE Camera-Ready
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.
Systematic de-anonymization
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).
Spend the extra content page
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.
Finalize the Data Availability Statement
- The statement moves from an **anonymized** link to the **permanent, DOI-archived** location.
- Confirm the archive is public and the DOI resolves; deposit in Zenodo / figshare / Software
Heritage before submitting camera-ready if you have not already.
- Keep it after the Conclusions and within the (now +1) page budget.
Template and metadata (IEEE/ACM dual)
- Use the **mandated camera-ready template** — for ASE 2026 the ACM `acmart` (switch out the
`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.
- Complete the **rights/copyright** step (the e-rights form) and paste the correct rights block into
the paper.
- Fill **indexing metadata** (title, authors, abstract, CCS concepts / keywords) accurately — this
feeds both IEEE Xplore and the ACM DL records; mismatches cause production delays.
- Embed all fonts; check figures render and that the PDF passes the publisher's automated checker
(e.g., an IEEE PDF eXpress-style or ACM validation step, per the edition's instructions).
If your paper earned an artifact badge
- Ensure the **badge** is reflected per the instructions so it appears on the front page in both
proceedings surfaces (see `ase-artifact-evaluation`).
- The badged artifact's DOI should match the Data Availability Statement.
Camera-ready checklist
[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
Output format
[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>
Read more
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.
ASE Camera-Ready
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.
Systematic de-anonymization
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).
Spend the extra content page
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.
Finalize the Data Availability Statement
- The statement moves from an **anonymized** link to the **permanent, DOI-archived** location.
- Confirm the archive is public and the DOI resolves; deposit in Zenodo / figshare / Software
Heritage before submitting camera-ready if you have not already.
- Keep it after the Conclusions and within the (now +1) page budget.
Template and metadata (IEEE/ACM dual)
- Use the **mandated camera-ready template** — for ASE 2026 the ACM `acmart` (switch out the
`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.
- Complete the **rights/copyright** step (the e-rights form) and paste the correct rights block into
the paper.
- Fill **indexing metadata** (title, authors, abstract, CCS concepts / keywords) accurately — this
feeds both IEEE Xplore and the ACM DL records; mismatches cause production delays.
- Embed all fonts; check figures render and that the PDF passes the publisher's automated checker
(e.g., an IEEE PDF eXpress-style or ACM validation step, per the edition's instructions).
If your paper earned an artifact badge
- Ensure the **badge** is reflected per the instructions so it appears on the front page in both
proceedings surfaces (see `ase-artifact-evaluation`).
- The badged artifact's DOI should match the Data Availability Statement.
Camera-ready checklist
[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
Output format
[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 一览 · ⚡ 如何使用 · 🧪 自动实证
Other skills on awesome-journal-skills.
- /aaai-artifact-evaluation
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.
Open skill - /aaai-author-response
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
Open skill - /aaai-camera-ready
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
Open skill - /aaai-experiments
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
Open skill - /aaai-related-work
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
Open skill - /aaai-reproducibility
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
Open skill

