Ito Compute
affaan-m/ECC
Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, revoke device credentials, and run explicitly gated node qualification through the separately…
A skill your agent uses 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…
MITAuto-check passed
Install Cav Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-camera-ready --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/CAV-Skills/skills/cav-camera-ready .claude/skills/cav-camera-ready && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cav-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-camera-ready into .claude/skills/cav-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-camera-ready", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-camera-readyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-camera-ready --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/CAV-Skills/skills/cav-camera-ready .agents/skills/cav-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cav-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-camera-ready into .agents/skills/cav-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-camera-ready", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-camera-ready --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/CAV-Skills/skills/cav-camera-ready .cursor/skills/cav-camera-ready && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cav-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-camera-ready into .cursor/skills/cav-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-camera-ready", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path CAV-Skills/skills/cav-camera-ready--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-camera-ready --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/CAV-Skills/skills/cav-camera-ready .gemini/skills/cav-camera-ready && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cav-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-camera-ready into .gemini/skills/cav-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-camera-ready", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-camera-readyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-camera-ready -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/CAV-Skills/skills/cav-camera-ready .github/skills/cav-camera-ready && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cav-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-camera-ready into .github/skills/cav-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-camera-ready", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-camera-ready -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-camera-ready --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/CAV-Skills/skills/cav-camera-ready .opencode/skills/cav-camera-ready && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cav-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-camera-ready into .opencode/skills/cav-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-camera-ready", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cav-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 497 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Preparing an accepted CAV (Computer Aided Verification) paper for its Springer LNCS open-access camera-ready
- SKILL.md covers Camera-ready audit, De-anonymization sweep…, LNCS production checks and Worked example: integrating a…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering de-anonymization for the previously double-blind categories
What it does
Cav Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- 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
- The copyright/open-access forms
Example prompts
- “/cav-camera-ready”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cav Camera Ready loads about 1.3k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 497 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 497 words, ~1,326 tokens.
Download SKILL.mdSave it as
.claude/skills/cav-camera-ready/SKILL.md (or your agent's skills folder).- name
- cav-camera-ready
- description
- 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.
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
llncsdocument 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 reviews and rebuttal committed to — without strengthening claims beyond what was evaluated.
- Permanentize the artifact/open-science links: replace any anonymized artifact link with a public, licensed, DOI-issuing archive, and make the paper's availability statement point at it.
- Complete the open-access / copyright forms: CAV proceedings are open access, so confirm the correct license and the open-access consent/rights form for the volume.
De-anonymization sweep (anonymized categories)
| Anonymized at submission | Restore at camera-ready | Watch for |
|---|---|---|
| Author block, affiliations, ORCID | Full, correctly ordered | Wrong author order breaks the LNCS citation and DOI metadata |
| Tool / solver / prover name | Real name throughout text, figures, artifact | A leftover anonymized name in a caption or a benchmark path |
| Acknowledgements, funding | Restored | Grant numbers required by funders |
| Self-citations (third person) | Natural first-person where it aids clarity | Over-correcting and double-citing |
| Artifact / repository link | Public archive DOI + tool homepage | The old anonymized URL surviving in a footnote |
Show full SKILL.md (190 more words)Show less
LNCS production checks
[Template] llncs document class, current revision; correct running heads; no manual margin edits
[Metadata] title, abstract, authors+ORCID, affiliations, corresponding author, keywords entered
in the Springer system and matching the PDF
[References] complete, consistent; DOIs where available; venue strings correct (do not misattribute
a TACAS/FMCAD paper to CAV)
[Figures] vector where possible; cactus/scatter plots readable in print; captions self-contained
[Rights] Springer open-access consent-to-publish / copyright form completed for the volume
[Links] every artifact and availability link resolves from a logged-out browserWorked example: integrating a rebuttal commitment
The reviews required scoping the generality claim to the supported theory and moving a lemma's full proof into the paper. Camera-ready move: narrow the claim sentence to the theory actually covered, promote the lemma proof from the appendix into the correctness section (space permitting) or keep it clearly in the appendix with a body pointer, restore the real tool name in the benchmark tables, and point the availability statement at the now-public DOI archive — without expanding the claim the PC accepted.
Artifact-badge handoff
The camera-ready and the AEC evaluation are separate deadlines, and the badge outcome may arrive after the camera-ready is due. Do not block the paper on the badge; but make the paper's availability statement consistent with the badges you are pursuing (Available at minimum; Functional/Reusable if granted), and add any badge acknowledgement only per the current LNCS/AEC instructions.
Hedged logistics
- Page allowances, metadata fields, the open-access rights mechanics, and exact camera-ready dates change each cycle; confirm against the decision email and current Springer LNCS instructions rather than a prior year (camera-ready date for 2026 is 待核实).
Output format
[Camera-ready status] ready / needs fixes / blocked
[De-anonymization] author block / tool name / acks / links restored (if applicable)? yes/no
[LNCS metadata] ORCID / author order / affiliations / keywords / rights form complete? yes/no
[Reviewer-change map] <required change -> final edit, no scope creep>
[Open science] anonymized links replaced by DOI archive? availability statement updated? yes/no
[Remaining owner] <person -> task>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in CAV-Skills/skills/cav-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cav Camera Ready next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cav Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Ito Computeaffaan-m/ECC | 276k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Senior Computer Visiondavila7/claude-code-templates | 32k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Senior Computer Visionalirezarezvani/claude-skills | 28k | 1 repos | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Senior Computer Vision
davila7/claude-code-templates
World-class computer vision skill for image/video processing, object detection, segmentation, and visual AI systems.
Senior Computer Vision
alirezarezvani/claude-skills
Computer vision engineering skill for object detection, image segmentation, and visual AI systems.
Release Preparation
CherryHQ/cherry-studio
Prepares a Cherry Studio release by resolving the version, collecting commits, writing bilingual release notes, updating version files and creating a release branch.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Cav Camera Ready
What does Cav Camera Ready do?
A skill your agent uses 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…. Cav Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Cav Camera Ready?
Cav Camera Ready fits situations like: 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; the copyright/open-access forms.
How do I install Cav Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-camera-ready -a claude-code`. Or copy the skill folder (CAV-Skills/skills/cav-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cav-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Cav Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-camera-ready -a codex`. Or copy the skill folder (CAV-Skills/skills/cav-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cav-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Cav Camera Ready in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cav-camera-ready, .gemini/skills/cav-camera-ready, .github/skills/cav-camera-ready and .opencode/skills/cav-camera-ready in your project.
What does Cav Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Cav Camera Ready is instructions for the agent only.
Does Cav Camera Ready access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cav Camera Ready safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cav Camera Ready use?
Cav Camera Ready is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cav Camera Ready use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cav Camera Ready?
Skills that share tags, products or a category with Cav Camera Ready: Ito Compute (affaan-m/ECC, 276k stars), Audit Preparation (sickn33/agentic-awesome-skills, 47k stars), QA Acceptance (paperclipai/paperclip, 99k stars) and Senior Computer Vision (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cav Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.