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 IEEE VIS paper for its IEEE TVCG camera-ready, covering de-anonymization, the VGTC/TVCG template and journal metadata (DOI, ORCID, IEEE…
MITAuto-check passed
Install Vis Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-camera-ready .claude/skills/vis-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 "vis-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-camera-ready into .claude/skills/vis-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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/VIS-Skills/skills/vis-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 vis-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-camera-ready .agents/skills/vis-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 "vis-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-camera-ready into .agents/skills/vis-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-camera-ready .cursor/skills/vis-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 "vis-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-camera-ready into .cursor/skills/vis-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 VIS-Skills/skills/vis-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 vis-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-camera-ready .gemini/skills/vis-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 "vis-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-camera-ready into .gemini/skills/vis-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-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 vis-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/VIS-Skills/skills/vis-camera-ready .github/skills/vis-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 "vis-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-camera-ready into .github/skills/vis-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-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 vis-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/VIS-Skills/skills/vis-camera-ready .opencode/skills/vis-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 "vis-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-camera-ready into .opencode/skills/vis-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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
vis-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 481 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 IEEE VIS paper for its IEEE TVCG camera-ready, covering de-anonymization, the VGTC/TVCG template and journal metadata (DOI, ORCID, IEEE…
- Preparing an accepted IEEE VIS paper for its IEEE TVCG camera-ready
- SKILL.md covers Camera-ready audit, De-anonymization sweep, TVCG 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
What it does
Vis Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted IEEE VIS paper for its IEEE TVCG camera-ready, covering de-anonymization, the VGTC/TVCG template and journal metadata (DOI, ORCID, IEEE keywords/index terms), integrating the second-round required changes without scope creep, permanentizing open-materials links, the Open Practices disclosure form, and the Graphics Replicability Stamp 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 IEEE VIS paper for its IEEE TVCG camera-ready
- Covering de-anonymization
- The VGTC/TVCG template and journal metadata (DOI
- IEEE keywords/index terms)
Example prompts
- “/vis-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
Vis Camera Ready loads about 1.3k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 481 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). 481 words, ~1,284 tokens.
Download SKILL.mdSave it as
.claude/skills/vis-camera-ready/SKILL.md (or your agent's skills folder).- name
- vis-camera-ready
- description
- Use when preparing an accepted IEEE VIS paper for its IEEE TVCG camera-ready, covering de-anonymization, the VGTC/TVCG template and journal metadata (DOI, ORCID, IEEE keywords/index terms), integrating the second-round required changes without scope creep, permanentizing open-materials links, the Open Practices disclosure form, and the Graphics Replicability Stamp handoff.
VIS Camera Ready
Use this after acceptance. IEEE VIS full papers are published as IEEE TVCG journal articles, so the camera-ready is a journal production step, not just a formatting pass. Reopen the current TVCG author instructions, the "Final Information for Paper Authors" page, and the Open Practices form before advising.
Camera-ready audit
- De-anonymize completely (if you submitted double-blind): restore the author block, affiliations, ORCIDs, acknowledgements, funding, and the real system, tool, and repository names the anonymization hid.
- Apply the final format: the VGTC / TVCG-conference template within the page budget (9 pages of content + up to 2 reference/acknowledgement pages), with the camera-ready allowances the acceptance letter states.
- Complete TVCG journal metadata: title/abstract, author order, ORCIDs, IEEE keywords / index terms, and the DOI-bearing citation once assigned. Journal metadata errors are harder to fix after publication than conference ones.
- Integrate the second-round required changes faithfully — without strengthening claims beyond what the reviewers evaluated.
- Permanentize open materials: replace every anonymized code/data/video link with a public, licensed, archival location (OSF, Zenodo, a tagged release), and make the paper point at it.
- Complete the Open Practices form (preprint, preregistration, open data/code, supplemental disclosures) that accepted authors fill in at camera-ready.
- Confirm presentation obligations; at least one author presents at the conference.
De-anonymization sweep
| Anonymized at submission | Restore at camera-ready | Watch for |
|---|---|---|
| Author block, affiliations, ORCID | Full, correctly ordered | Wrong author order breaks the DOI citation |
| System / technique name | Real name throughout text, figures, video, repo | A leftover placeholder name in a caption or the video |
| Acknowledgements, funding | Restored | Grant numbers required by funders |
| Self-citations (third person) | Natural first-person where it aids clarity | Over-correcting and double-citing |
| Supplemental video | Re-render with real title/affiliation slate | The anonymized voice-over or blurred logo surviving |
| Code/data link | Public archival DOI (OSF/Zenodo) | The old anonymized URL surviving in a footnote |
Show full SKILL.md (183 more words)Show less
TVCG production checks
[Template] VGTC / TVCG-conference template, current revision; no manual margin/font edits
[Metadata] title, abstract, authors+ORCID, IEEE keywords/index terms entered and matching PDF
[References] complete, consistent; DOIs where available; within the 2-page reference allowance
[Figures] vector where possible; readable in print and grayscale; CVD-safe palettes; captions self-contained
[Rights] IEEE copyright/eCF form completed; correct rights statement on the first page
[Links] every open-materials and video link resolves from a logged-out browser
[Video] supplemental video re-rendered, de-anonymized, correct codec/lengthWorked example: integrating a second-round required change
The reviewers required adding the perceptual pilot and rewriting the encoding rationale. Camera-ready move: place the pilot's result with its effect size and CI in the evaluation section, revise §4 so each visual channel is tied to a task, restore the real system name in the figures and the video, and point the open-materials statement at the now-public OSF archive — without expanding the claim the reviewers accepted.
Replicability-Stamp and Open Practices handoff
The camera-ready and the Graphics Replicability Stamp review are separate tracks. Do not wait for the stamp result to finalize the paper, but do make the paper's open-materials statement consistent with what you are submitting to GRSI, and complete the Open Practices disclosures honestly. The stamp is earned by an independent volunteer reproducing your code/data, so the public archive must be the exact, runnable version the paper describes.
Hedged logistics
- Page allowances, metadata fields, the IEEE rights-form mechanics, and exact camera-ready dates change each cycle; confirm against the decision email and current TVCG instructions rather than a prior year.
Output format
[Camera-ready status] ready / needs fixes / blocked
[De-anonymization] author block / system name / acks / links / video restored? yes/no
[TVCG metadata] ORCID / IEEE keywords / rights form complete? yes/no
[Required-change map] <second-round change -> final edit, no scope creep>
[Open practices] anonymized links replaced by archival DOI? disclosure form done? 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 VIS-Skills/skills/vis-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vis 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 |
|---|---|---|---|---|---|---|
| Vis Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | 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 | 52k | — | ~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 Vis Camera Ready
What does Vis Camera Ready do?
A skill your agent uses when preparing an accepted IEEE VIS paper for its IEEE TVCG camera-ready, covering de-anonymization, the VGTC/TVCG template and journal metadata (DOI, ORCID, IEEE…. Vis Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted IEEE VIS paper for its IEEE TVCG camera-ready, covering de-anonymization, the VGTC/TVCG template and journal metadata (DOI, ORCID, IEEE keywords/index terms), integrating the second-round required changes without scope creep, permanentizing open-materials links, the Open Practices disclosure form, and the Graphics Replicability Stamp handoff.
When should I use Vis Camera Ready?
Vis Camera Ready fits situations like: preparing an accepted IEEE VIS paper for its IEEE TVCG camera-ready; covering de-anonymization; the VGTC/TVCG template and journal metadata (DOI; IEEE keywords/index terms).
How do I install Vis Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-camera-ready -a claude-code`. Or copy the skill folder (VIS-Skills/skills/vis-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vis-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Vis Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-camera-ready -a codex`. Or copy the skill folder (VIS-Skills/skills/vis-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vis-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Vis 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 vis-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/vis-camera-ready, .gemini/skills/vis-camera-ready, .github/skills/vis-camera-ready and .opencode/skills/vis-camera-ready in your project.
What does Vis Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Vis Camera Ready is instructions for the agent only.
Does Vis 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 Vis 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 Vis Camera Ready use?
Vis 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 Vis Camera Ready use?
About 1.3k tokens (SKILL.md is roughly 5.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 Vis Camera Ready?
Skills that share tags, products or a category with Vis Camera Ready: Audit Preparation (sickn33/agentic-awesome-skills, 47k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Release Preparation (CherryHQ/cherry-studio, 52k 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 Vis 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.