Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
A skill your agent uses when preparing an accepted IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle, integrating the meta-review, the IEEE electronic…
MITAuto-check passed
Install Iros Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-camera-ready .claude/skills/iros-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 "iros-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-camera-ready into .claude/skills/iros-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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/IROS-Skills/skills/iros-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 iros-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-camera-ready .agents/skills/iros-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 "iros-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-camera-ready into .agents/skills/iros-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 iros-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-camera-ready .cursor/skills/iros-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 "iros-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-camera-ready into .cursor/skills/iros-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 IROS-Skills/skills/iros-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 iros-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-camera-ready .gemini/skills/iros-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 "iros-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-camera-ready into .gemini/skills/iros-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 iros-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 iros-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/IROS-Skills/skills/iros-camera-ready .github/skills/iros-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 "iros-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-camera-ready into .github/skills/iros-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 iros-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 iros-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/IROS-Skills/skills/iros-camera-ready .opencode/skills/iros-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 "iros-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-camera-ready into .opencode/skills/iros-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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
iros-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~983 tokens
- SKILL.md length
- 390 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 IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle, integrating the meta-review, the IEEE electronic…
- Preparing an accepted IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle
- SKILL.md covers Camera-ready audit, De-anonymization sweep, Common camera-ready reflow… and Worked example: integrating a…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Integrating the meta-review
What it does
Iros Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle, integrating the meta-review, the IEEE electronic copyright form (eCF), the July final-paper deadline, registration and in-person presentation, and the public artifact release anonymity had blocked.
Its SKILL.md is about 980 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 IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle
- Integrating the meta-review
- The IEEE electronic copyright form (eCF)
- The July final-paper deadline
Example prompts
- “/iros-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
Iros Camera Ready loads about 983 tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 390 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). 390 words, ~983 tokens.
Download SKILL.mdSave it as
.claude/skills/iros-camera-ready/SKILL.md (or your agent's skills folder).- name
- iros-camera-ready
- description
- Use when preparing an accepted IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle, integrating the meta-review, the IEEE electronic copyright form (eCF), the July final-paper deadline, registration and in-person presentation, and the public artifact release anonymity had blocked.
IROS Camera Ready
Use this after acceptance. Reopen the current IROS final-submission instructions, the IEEE PDF-eXpress and copyright pages, the registration page, and the presentation policy before advising authors. For the 2026 cycle the camera-ready (final paper) deadline was July 10, 2026, close behind the June 16 notification — a short turnaround, so plan it as part of submission, not an afterthought.
Camera-ready audit
- Convert the anonymous submission to the public version: restore the author block, affiliations, acknowledgements, funding, and any code/data links stripped for double-anonymous review.
- Apply the current final-page rules and confirm whether references and any content still fit the budget once the author block and acknowledgements are added back.
- Integrate the meta-review's requested changes without expanding the contribution beyond what was reviewed.
- Run the paper through IEEE PDF-eXpress (or the cycle's equivalent) for Xplore compliance, and file the IEEE electronic copyright form (eCF) — publication in Xplore is gated on it.
- Prepare the public artifact release now that anonymity no longer applies: repository, logs, configs, datasets, and a citable archive; test every link from a logged-out browser.
- Confirm registration and in-person presentation obligations; at least one author typically must register and present.
De-anonymization sweep
- Restore the author list exactly as entered in PaperPlaza metadata; a mismatch between the metadata and the camera-ready authorship creates a real dispute vector on the Xplore record.
- Rewrite third-person self-citations ("the XYZ rover [9]") back into natural first-person form where it improves clarity.
- Replace anonymized figure and video footage with the real, identified versions if you kept scenery blurred for review — and re-check that nothing embarrassing was left cropped.
- Swap anonymized code mirrors for the public, licensed repository.
Show full SKILL.md (116 more words)Show less
Common camera-ready reflow surprises
| Change at camera-ready | Effect | Fix |
|---|---|---|
| Author block + affiliations added | Content reflows; a tight paper may overrun | Trim or budget for it before the flip |
| Acknowledgements/funding restored | Extra lines near the end of the paper | Compress a nearby paragraph |
| Real (unblurred) figures swapped in | Sizes/DPI differ from anonymized placeholders | Re-check figure placement and legibility |
| Public links added | Dead or identity-wrong links | Test each from a logged-out browser |
Worked example: integrating a meta-review fix
The meta-review asked that failure cases be reported. Camera-ready move: add the failure-taxonomy table you already logged, one sentence interpreting it, and a pointer from the results discussion — without strengthening any success claim the reviewers did not evaluate.
Camera-ready gate (do not submit until all true):
[ ] author block + acknowledgements restored; page budget still met
[ ] meta-review asks integrated, no scope inflation
[ ] IEEE eCF filed; PDF-eXpress compliant
[ ] public artifact + links tested logged-out
[ ] registration done; presenter assigned
[ ] final/updated video meets the current specOutput format
[Camera-ready status] Ready / Needs fixes / Blocked
[Final package] <PDF / eCF / metadata / artifact / video>
[Policy checks] <page budget / authors / registration / presentation>
[Meta-review map] <ask -> final edit>
[Remaining owner] <person -> task, before the July deadline>© 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 IROS-Skills/skills/iros-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iros 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 |
|---|---|---|---|---|---|---|
| Iros Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~983 | 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 | |
| Release PreparationCherryHQ/cherry-studio | 53k | — | ~4.3k | Automated safety check: Pass | AGPL-3.0 | |
| 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 |
Similar skills
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.
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.
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.
Prepare Paperclip PR
paperclipai/paperclip
Prepare a Paperclip branch for PR with commits, template body, and checks.
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 Iros Camera Ready
What does Iros Camera Ready do?
A skill your agent uses when preparing an accepted IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle, integrating the meta-review, the IEEE electronic…. Iros Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle, integrating the meta-review, the IEEE electronic copyright form (eCF), the July final-paper deadline, registration and in-person presentation, and the public artifact release anonymity had blocked.
When should I use Iros Camera Ready?
Iros Camera Ready fits situations like: preparing an accepted IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle; integrating the meta-review; the IEEE electronic copyright form (eCF); the July final-paper deadline.
How do I install Iros Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-camera-ready -a claude-code`. Or copy the skill folder (IROS-Skills/skills/iros-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iros-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Iros Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-camera-ready -a codex`. Or copy the skill folder (IROS-Skills/skills/iros-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iros-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Iros 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 iros-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/iros-camera-ready, .gemini/skills/iros-camera-ready, .github/skills/iros-camera-ready and .opencode/skills/iros-camera-ready in your project.
What does Iros Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Iros Camera Ready is instructions for the agent only.
Does Iros 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 Iros 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 Iros Camera Ready use?
Iros 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 Iros Camera Ready use?
About 983 tokens (SKILL.md is roughly 3.9k 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 Iros Camera Ready?
Skills that share tags, products or a category with Iros Camera Ready: Audit Preparation (sickn33/agentic-awesome-skills, 47k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Release Preparation (CherryHQ/cherry-studio, 53k stars) and Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iros 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.