cav-camera-ready
Use when preparing an accepted CAV (Computer Aided Verification) paper for its Springer LNCS open-access camera-ready, covering de-anonymization for the previously double-blind categories, the LNCS llncs template and Springer metadata (ORCID, author order, running heads), the copyright/open-access forms, integrating reviewer-required changes without scope creep, permanentizing artifact links, and the AEC badge handoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-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.
# CAV Camera Ready Use this after acceptance. CAV papers are published **open access as Springer LNCS chapters**, so the camera-ready is a Springer production step with its own metadata and rights forms. Reopen the current LNCS author instructions, the decision email, and the artifact-track page before advising. ## Camera-ready audit - **De-anonymize (Regular and Application papers):** restore the author block, affiliations, acknowledgements, funding, and the real tool/solver and repository names that double-blind review forced you to hide. (Tool and Industrial papers were never anonymized.) - **Apply the final LNCS format:** the `llncs` document class, within the category page allowance and any camera-ready extension the acceptance letter grants, with correct running heads and the Springer copyright line. - **Complete Springer LNCS metadata:** title/abstract, author order and ORCIDs, corresponding author, affiliations, and keywords — entered in the Springer system and matching the PDF exactly. Metadata errors are harder to fix after the volume is published than formatting ones. - **Integrate reviewer-required changes** faithfully — the scoping edits and added clarifications the re
- Camera-ready audit
- De-anonymization sweep (anonymized categories)
- LNCS production checks
- Worked example: integrating a rebuttal commitment
- Artifact-badge handoff
- Hedged logistics
- Output format
What does the cav-camera-ready skill do?
Use when preparing an accepted CAV (Computer Aided Verification) paper for its Springer LNCS open-access camera-ready, covering de-anonymization for the previously double-blind categories, the LNCS llncs template and Springer metadata (ORCID, author order, running heads), the copyright/open-access forms, integrating reviewer-required changes without scope creep, permanentizing artifact links, and the AEC badge handoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-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.