ecai-camera-ready
Use when preparing the ECAI camera-ready — de-anonymizing, fitting the final version into the page budget, and meeting the publisher's production requirements, which differ by regime: IOS Press FAIA (ecai.cls, open-access book volume, copyright/consent-to-publish forms) for a standalone ECAI, versus IJCAI's own open-access proceedings (ijcai.sty) for the joint IJCAI-ECAI 2026.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-camera-ready --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ECAI Camera-Ready The camera-ready turns an accepted paper into an archival, open-access publication. **The single biggest decision is which publisher regime the edition is in**, because it sets the template, the metadata, and the forms: - **Standalone ECAI** → published in **IOS Press FAIA** (Frontiers in Artificial Intelligence and Applications), an **open-access book series**. Template **`ecai.cls`**; a **consent-to-publish / copyright form** to IOS Press; the paper becomes a numbered chapter in a FAIA volume (ECAI 2024 = Vol. 392). - **IJCAI-ECAI 2026** → published in **IJCAI's own open-access, online-only proceedings**. Template **`ijcai.sty`**; IJCAI's license/consent process; the paper indexes under the IJCAI proceedings, not FAIA, this cycle. Confirm the regime, the exact production instructions, and every deadline on the current author kit before starting — the details below are a 2026-07-09 snapshot. ## De-anonymize systematically The reviewed PDF was double-blind; the camera-ready is not. Reverse every anonymization: - Restore **author names, affiliations, and ORCIDs** in the template's author block. - Restore **acknowledgements and funding** statements (removed for re
- De-anonymize systematically
- Fit the final version into the page budget
- Template and production checks
- Open-access specifics
- Registration and presentation gate
- Final checklist
- Reverify each cycle
Catch leftover anonymization scaffolding grep -nEi 'anonymous|anonymi|blinded|redacted|\[REDACTED\]|XX+|placeholder' paper.tex | head grep -nEi 'our prior work \[|removed for (review|blind)' paper.tex | head PDF production sanity (both regimes) pdffonts paper.pdf | grep -i 'Type 3' && echo "FAIL: Type 3 fonts present" pdfinfo paper.pdf | grep -Ei 'page size|pages' # confirm A4/Letter per the kit and page count
What does the ecai-camera-ready skill do?
Use when preparing the ECAI camera-ready — de-anonymizing, fitting the final version into the page budget, and meeting the publisher's production requirements, which differ by regime: IOS Press FAIA (ecai.cls, open-access book volume, copyright/consent-to-publish forms) for a standalone ECAI, versus IJCAI's own open-access proceedings (ijcai.sty) for the joint IJCAI-ECAI 2026.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-camera-ready --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.