Convert
remotion-dev/remotion
Start the local @remotion/convert app and open it in the Codex browser.
A skill your agent uses when converting an accepted ICSE research-track paper into its final published form, covering the extra camera-ready page, de-anonymization order, finalizing the Data…
MITAuto-check passed
Install Icse Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-camera-ready .claude/skills/icse-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 "icse-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-camera-ready into .claude/skills/icse-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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/ICSE-Skills/skills/icse-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 icse-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-camera-ready .agents/skills/icse-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 "icse-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-camera-ready into .agents/skills/icse-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-camera-ready .cursor/skills/icse-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 "icse-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-camera-ready into .cursor/skills/icse-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 ICSE-Skills/skills/icse-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 icse-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-camera-ready .gemini/skills/icse-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 "icse-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-camera-ready into .gemini/skills/icse-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-camera-ready .github/skills/icse-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 "icse-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-camera-ready into .github/skills/icse-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-camera-ready .opencode/skills/icse-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 "icse-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-camera-ready into .opencode/skills/icse-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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
icse-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 684 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting an accepted ICSE research-track paper into its final published form, covering the extra camera-ready page, de-anonymization order, finalizing the Data…
- Works in 3 steps: Changes promised in the author response… → The threats-to-validity or study-design… → Restored per-subject detail that…
- Converting an accepted ICSE research-track paper into its final published form
- SKILL.md covers What actually changes, De-anonymization order, Production-quality gate and Consistency with the accepted…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Icse Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an accepted ICSE research-track paper into its final published form, covering the extra camera-ready page, de-anonymization order, finalizing the Data Availability section with archival DOIs, IEEE-template production checks, and conference-presentation obligations to verify.
Its SKILL.md is about 1.5k 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
- Converting an accepted ICSE research-track paper into its final published form
- Covering the extra camera-ready page
- De-anonymization order
- Finalizing the Data Availability section with archival DOIs
Example prompts
- “/icse-camera-ready”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Changes promised in the author response or Major Revision ledger that were
- The threats-to-validity or study-design detail that reviews called thin.
- Restored per-subject detail that summarize-and-point compression removed.
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 (its code samples are bash).
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
Icse Camera Ready loads about 1.5k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 684 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). 684 words, ~1,523 tokens.
Download SKILL.mdSave it as
.claude/skills/icse-camera-ready/SKILL.md (or your agent's skills folder).- name
- icse-camera-ready
- description
- Use when converting an accepted ICSE research-track paper into its final published form, covering the extra camera-ready page, de-anonymization order, finalizing the Data Availability section with archival DOIs, IEEE-template production checks, and conference-presentation obligations to verify.
ICSE Camera-Ready
Acceptance converts the paper from an argument into a permanent record — ICSE proceedings live in the ACM Digital Library and IEEE Xplore, and the camera-ready is the version every future reader, replicator, and artifact evaluator holds against your claims. The window is short and lands amid artifact-evaluation prep, so run it as a checklist, not a rewrite.
What actually changes
The 2027 call (read 2026-07-08) grants accepted papers one extra page of main text for the camera-ready — 11 + 2 instead of 10 + 2. Spend it where review friction was, in this order of value:
- Changes promised in the author response or Major Revision ledger that were squeezed by space — reviewers who see their request honored in the final version include your artifact evaluators and future citers.
- The threats-to-validity or study-design detail that reviews called thin.
- Restored per-subject detail that summarize-and-point compression removed.
Do not spend it on a new contribution: the paper was accepted for what it evidenced, and content that never faced review is a correctness risk with your name permanently on it.
De-anonymization order
Reverse the double-anonymous transformations systematically — grep, don't recall:
# Residual-anonymity sweep on the camera-ready sources
grep -rn "anonym\|blinded\|double-blind\|under review" *.tex # stale phrases
grep -rn "anonymous.4open\|anonymized-link\|REDACTED" *.tex # placeholder URLs
grep -n "our prior work\|the authors of \[" *.tex # third-person self-cites to naturalize
pdfinfo camera-ready.pdf | grep -Ei 'author|title' # metadata now SHOULD carry authorsRestore: the author block with affiliations, emails, and ORCIDs;
acknowledgments and funding with grant numbers; self-citations rephrased into
natural first person where it improves clarity; and — most consequentially —
the availability statement's links, from anonymized mirrors to the
permanent DOI-issuing archive (icse-artifact-evaluation covers minting it).
A camera-ready that still points at a review-time anonymous mirror will
outlive the mirror.
Production-quality gate
| Check | Detail |
|---|---|
| Template | Current IEEE conference class, unmodified; production vendors reject tampering the PC tolerated |
| Metadata block | Copyright/DOI stamps per the acceptance instructions; correct year and conference string |
| Author records | Name spellings, affiliations, ORCIDs consistent with the submission system — indexing errors are near-impossible to fix post-publication |
| Fonts and figures | Fonts embedded, figures vector where possible, colorblind-legible; print-grayscale still distinguishable |
| References | Every entry re-verified against dblp/DL records; camera-ready is the last chance to fix a wrong venue or year |
| Availability statement | DOI links live; artifact contents match final table/figure numbering |
| Title/abstract sync | Final title and abstract match the submission system's metadata fields exactly |
Consistency with the accepted version
Chairs expect the camera-ready to be the accepted paper plus the required changes — not a quiet second revision. Keep a change log from accepted PDF to camera-ready; if a real error surfaced after acceptance (a bug in an analysis script, a corrected number), fix it and flag it to the track chairs rather than hoping nobody diffs. Silent number changes discovered later are an integrity problem; disclosed corrections are routine science.
Show full SKILL.md (257 more words)Show less
Obligations around the paper — verify, don't assume
Several items were not published for the 2027 cycle at check time and are 待核实 on the live pages once acceptance emails go out:
- Camera-ready deadline and the exact submission system/vendor instructions.
- Registration requirements tied to publication (one author registering at a qualifying rate is the common conference pattern — confirm ICSE 2027's wording before budgeting).
- Presentation format and whether remote presentation exists; plan for in-person in Dublin (Apr 25 – May 1, 2027; core days Apr 28–30).
- Page-purchase options beyond the granted extra page.
- Video, poster, or preprint requirements attached to the final submission.
Book Dublin logistics early regardless: late-April conference housing in a capital city is its own deadline.
The December–January squeeze
For Major-Revision papers the final decision (December 18 in the 2027 cycle) lands directly against the artifact-evaluation window (early January in recent cycles) and, soon after, camera-ready production. Sequence deliberately: freeze the artifact container first (it feeds the badge deadline), then finalize the availability statement's DOI (the camera-ready needs it), then spend the extra page — because page-11 content that cites package paths must cite the final package. Groups that treat these as three independent deadlines do the DOI work twice.
Publication-week hygiene
Post the accepted-version preprint per the copyright terms you signed (arXiv or institutional repository — the open-science culture expects it), update the artifact's citation file with the final DOI, and make the paper's page, package, and preprint agree on one canonical title and author order. Future citation graphs are built from whichever version spreads first.
Output format
[Extra page] spent on: <review-friction items>; new-contribution check: none added
[De-anonymization] sweep results; availability links now DOI-permanent
[Production gate] table above -> pass/fail per row
[Change log] accepted -> camera-ready diffs; disclosed items
[Obligations] deadline / registration / presentation — verified or 待核实 with owner© 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 ICSE-Skills/skills/icse-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icse 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 |
|---|---|---|---|---|---|---|
| Icse Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Convertremotion-dev/remotion | 63k | — | ~247 | Automated safety check: Pass | Custom licence | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Acceptance Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~943 | Automated safety check: Pass | MIT | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 | |
| Word to Markdown Convertergithub/awesome-copilot | 40k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
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.
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
- Official
Word to Markdown Converter
github/awesome-copilot
Converts Word .docx files to Markdown with a bundled script before analysis, extracting embedded images and handling whole folders alongside the PDF and Excel converters.
Change, Accept or Leave Framework
kangarooking/cangjie-skill
Helps someone stuck ruminating over an unchangeable situation decide whether to change it, accept it, or leave it, drawn from a chapter of Navalism-style writing.
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 Icse Camera Ready
What does Icse Camera Ready do?
A skill your agent uses when converting an accepted ICSE research-track paper into its final published form, covering the extra camera-ready page, de-anonymization order, finalizing the Data…. Icse Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an accepted ICSE research-track paper into its final published form, covering the extra camera-ready page, de-anonymization order, finalizing the Data Availability section with archival DOIs, IEEE-template production checks, and conference-presentation obligations to verify.
When should I use Icse Camera Ready?
Icse Camera Ready fits situations like: converting an accepted ICSE research-track paper into its final published form; covering the extra camera-ready page; de-anonymization order; finalizing the Data Availability section with archival DOIs.
How do I install Icse Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-camera-ready -a claude-code`. Or copy the skill folder (ICSE-Skills/skills/icse-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icse-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Icse Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-camera-ready -a codex`. Or copy the skill folder (ICSE-Skills/skills/icse-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icse-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Icse 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 icse-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/icse-camera-ready, .gemini/skills/icse-camera-ready, .github/skills/icse-camera-ready and .opencode/skills/icse-camera-ready in your project.
What does Icse Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Icse Camera Ready is instructions for the agent only.
Does Icse 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 Icse 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 Icse Camera Ready use?
Icse 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 Icse Camera Ready use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Icse Camera Ready?
Skills that share tags, products or a category with Icse Camera Ready: Convert (remotion-dev/remotion, 63k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars) and Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icse Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.