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 ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class, de-anonymizing, completing LIPIcs metadata (ACM…
MITAuto-check passed
Install Itcs Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-camera-ready .claude/skills/itcs-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 "itcs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-camera-ready into .claude/skills/itcs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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/ITCS-Skills/skills/itcs-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 itcs-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-camera-ready .agents/skills/itcs-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 "itcs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-camera-ready into .agents/skills/itcs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-camera-ready .cursor/skills/itcs-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 "itcs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-camera-ready into .cursor/skills/itcs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 ITCS-Skills/skills/itcs-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 itcs-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-camera-ready .gemini/skills/itcs-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 "itcs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-camera-ready into .gemini/skills/itcs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-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 itcs-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/ITCS-Skills/skills/itcs-camera-ready .github/skills/itcs-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 "itcs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-camera-ready into .github/skills/itcs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-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 itcs-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/ITCS-Skills/skills/itcs-camera-ready .opencode/skills/itcs-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 "itcs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-camera-ready into .opencode/skills/itcs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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
itcs-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 519 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 ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class, de-anonymizing, completing LIPIcs metadata (ACM…
- Preparing an accepted ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class
- SKILL.md covers Switch to the LIPIcs class, De-anonymize completely, Complete the LIPIcs metadata and Fold in reviewer-noted fixes, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Completing LIPIcs metadata (ACM CCS
What it does
Itcs Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class, de-anonymizing, completing LIPIcs metadata (ACM CCS, keywords, funding), folding in reviewer-noted fixes, and passing the Schloss Dagstuhl production checks.
Its SKILL.md is about 1.4k 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 ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class
- Completing LIPIcs metadata (ACM CCS
- Folding in reviewer-noted fixes
- Passing the Schloss Dagstuhl production checks
Example prompts
- “/itcs-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
Itcs Camera Ready loads about 1.4k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 519 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). 519 words, ~1,351 tokens.
Download SKILL.mdSave it as
.claude/skills/itcs-camera-ready/SKILL.md (or your agent's skills folder).- name
- itcs-camera-ready
- description
- Use when preparing an accepted ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class, de-anonymizing, completing LIPIcs metadata (ACM CCS, keywords, funding), folding in reviewer-noted fixes, and passing the Schloss Dagstuhl production checks.
ITCS Camera-Ready
On acceptance, an ITCS paper becomes an open-access LIPIcs article (Schloss Dagstuhl),
Creative-Commons-licensed, with no article-processing charge. The camera-ready is a distinct
production process from submission: it uses the lipics-v2021 document class (not the free
single-column submission format), requires LIPIcs-specific metadata, and is checked by the
Dagstuhl editorial office. This skill runs that pass. Confirm the exact deadline and any
ITCS-specific page limit on the current call — the camera-ready page limit is 待核实 as of
2026-07-09 (see ../../resources/official-source-map.md).
Switch to the LIPIcs class
- Use
lipics-v2021(the current LIPIcs LaTeX class from Dagstuhl). Do not submit the submission-time single-column format as camera-ready; the class controls layout, the DROPS metadata, and the license block. - Re-fit content to the LIPIcs style. The class changes spacing and float handling; check that theorem environments, the appendix, and any figures still render cleanly.
- Respect the LIPIcs page-limit convention (a main-text limit with the bibliography excluded, and typically a small "+1 page" allowance granted on acceptance). The exact ITCS number is cycle-specific — 待核实; read the camera-ready instructions.
De-anonymize completely
The submission was lightweight double-blind; the camera-ready is fully attributed:
- Restore author names, affiliations, ORCIDs, and emails in the LIPIcs author blocks.
- Restore acknowledgements and funding lines you removed for anonymity — LIPIcs has a dedicated funding field; list grants and agencies there.
- Convert third-person self-references back to natural form where appropriate, and make sure no "[Author, YEAR]" placeholder from the blinding survives.
Complete the LIPIcs metadata
LIPIcs/DROPS requires structured metadata beyond the PDF body:
- ACM 2012 CCS concepts — pick the Computing Classification System categories that match the
paper; the class provides the
\ccsdescmacro. - Keywords — a short, specific list for indexing.
- Author ORCIDs for every author (LIPIcs strongly encourages these).
- Funding — per-author funding statements in the LIPIcs funding field.
- Related-version links — declare the arXiv/ECCC/ePrint full version as a "Related Version" (e.g., "Full Version") so the open record is linked from the published article.
- Category / acknowledgements / license blocks as the class template specifies.
Show full SKILL.md (193 more words)Show less
Fold in reviewer-noted fixes
Even without a rebuttal or revision round, the reviews often flag concrete corrections. The camera-ready is where they land:
- Correct any misstated claim, add a missing citation, clarify a definition, or repair a proof gap the reviews identified.
- Use the (generous) LIPIcs length to add the clarification rather than cut — but keep the
first-pages merits window clean (see
itcs-writing-style). - Ensure the camera-ready and the public full version stay in sync after these edits (see
itcs-reproducibility).
Dagstuhl production checks
- Compile with the exact
lipics-v2021class and required packages; the DROPS pipeline is strict about a clean build and correct metadata macros. - Fonts embedded, PDF/A-friendly, no external font issues — the editorial office will bounce a non-compliant PDF.
- Bibliography complete and consistently formatted; DOIs where available.
- Author agreement / license signed for the LIPIcs Creative-Commons publication.
- Register at least one author to present at the conference; ITCS is a present-in-person venue.
Camera-ready checklist
[Class] lipics-v2021 used; content re-fit; page-limit convention met (exact # 待核实)
[De-anonymize] names, affiliations, ORCIDs, emails, acknowledgements, funding restored
[Metadata] ACM CCS, keywords, ORCIDs, funding, Related-Version (arXiv/ECCC/ePrint) all set
[Fixes] reviewer-noted corrections folded in; merits window still clean
[Sync] camera-ready and public full version agree
[Production] clean lipics-v2021 build, fonts embedded, license signed, bib complete
[Presentation] a presenting author registeredReverify each cycle
- The camera-ready deadline and the current LIPIcs class version.
- The exact ITCS page-limit number and any "+1 page" allowance (待核实).
- The required metadata fields (CCS version, ORCID policy, funding format) on the DROPS/LIPIcs author instructions.
Output format
[ITCS camera-ready status] ready / needs work
[Class] lipics-v2021 building cleanly? page-limit convention met? yes/no
[De-anonymized] all author/affiliation/funding fields restored? yes/no
[Metadata] CCS + keywords + ORCIDs + funding + Related-Version complete? yes/no
[Fixes+sync] reviewer corrections in; full version consistent? yes/no
[Fix queue] <ordered, with the production 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 ITCS-Skills/skills/itcs-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Itcs 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 |
|---|---|---|---|---|---|---|
| Itcs Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | 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 | |
| Public Relationscoreyhaines31/marketingskills | 54k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Release PreparationCherryHQ/cherry-studio | 52k | — | ~4.3k | Automated safety check: Pass | AGPL-3.0 | |
| Public Relationssickn33/agentic-awesome-skills | 47k | 1 repos | ~1.8k | Automated safety check: Pass | MIT |
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.
Public Relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).
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.
Public Relations
sickn33/agentic-awesome-skills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).
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.
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 Itcs Camera Ready
What does Itcs Camera Ready do?
A skill your agent uses when preparing an accepted ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class, de-anonymizing, completing LIPIcs metadata (ACM…. Itcs Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class, de-anonymizing, completing LIPIcs metadata (ACM CCS, keywords, funding), folding in reviewer-noted fixes, and passing the Schloss Dagstuhl production checks.
When should I use Itcs Camera Ready?
Itcs Camera Ready fits situations like: preparing an accepted ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class; completing LIPIcs metadata (ACM CCS; folding in reviewer-noted fixes; passing the Schloss Dagstuhl production checks.
How do I install Itcs Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-camera-ready -a claude-code`. Or copy the skill folder (ITCS-Skills/skills/itcs-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/itcs-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Itcs Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-camera-ready -a codex`. Or copy the skill folder (ITCS-Skills/skills/itcs-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/itcs-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Itcs 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 itcs-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/itcs-camera-ready, .gemini/skills/itcs-camera-ready, .github/skills/itcs-camera-ready and .opencode/skills/itcs-camera-ready in your project.
What does Itcs Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Itcs Camera Ready is instructions for the agent only.
Does Itcs 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 Itcs 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 Itcs Camera Ready use?
Itcs 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 Itcs Camera Ready use?
About 1.4k tokens (SKILL.md is roughly 5.4k 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 Itcs Camera Ready?
Skills that share tags, products or a category with Itcs Camera Ready: Audit Preparation (sickn33/agentic-awesome-skills, 47k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Public Relations (coreyhaines31/marketingskills, 54k stars) and Release Preparation (CherryHQ/cherry-studio, 52k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Itcs Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.