Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
A skill your agent uses when preparing the final version of an accepted CVPR paper, covering de-anonymization, the dataset-release-by-camera-ready obligation, CVF open access versus the IEEE Xplore…
Install Cvpr Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cvpr-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/CVPR-Skills/skills/cvpr-camera-ready .claude/skills/cvpr-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 "cvpr-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-camera-ready into .claude/skills/cvpr-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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/CVPR-Skills/skills/cvpr-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 cvpr-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cvpr-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/CVPR-Skills/skills/cvpr-camera-ready .agents/skills/cvpr-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 "cvpr-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-camera-ready into .agents/skills/cvpr-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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 cvpr-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cvpr-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/CVPR-Skills/skills/cvpr-camera-ready .cursor/skills/cvpr-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 "cvpr-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-camera-ready into .cursor/skills/cvpr-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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 CVPR-Skills/skills/cvpr-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 cvpr-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cvpr-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/CVPR-Skills/skills/cvpr-camera-ready .gemini/skills/cvpr-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 "cvpr-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-camera-ready into .gemini/skills/cvpr-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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 cvpr-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 cvpr-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/CVPR-Skills/skills/cvpr-camera-ready .github/skills/cvpr-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 "cvpr-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-camera-ready into .github/skills/cvpr-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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 cvpr-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 cvpr-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/CVPR-Skills/skills/cvpr-camera-ready .opencode/skills/cvpr-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 "cvpr-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-camera-ready into .opencode/skills/cvpr-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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
cvpr-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 782 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing the final version of an accepted CVPR paper, covering de-anonymization, the dataset-release-by-camera-ready obligation, CVF open access versus the IEEE Xplore…
- Works in 5 steps: Restore authors, affiliations, and… → Write real acknowledgements (grants,… → Convert third-person self-citations back… → …
- Preparing the final version of an accepted CVPR paper
- SKILL.md covers Where the paper actually ends up, De-anonymization without…, The dataset clause has a… and Oral, highlight, or poster:…, plus 4 more sections
- Calls curl and python3
What it does
Cvpr Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing the final version of an accepted CVPR paper, covering de-anonymization, the dataset-release-by-camera-ready obligation, CVF open access versus the IEEE Xplore version of record, oral/highlight/poster preparation at conference scale, and arXiv/preprint synchronization after acceptance.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Academic paper search. It works with arXiv. 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 the final version of an accepted CVPR paper
- Covering de-anonymization
- The dataset-release-by-camera-ready obligation
- CVF open access versus the IEEE Xplore version of record
Example prompts
- “/cvpr-camera-ready”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Restore authors, affiliations, and emails in the final class-file mode.
- Write real acknowledgements (grants, compute donors) — banned during review, expected
- Convert third-person self-citations back where the prose became misleading ("[12]
- Replace every "anonymous supplementary" pointer with live URLs: code repo, project
- Rebuild and re-read — de-anonymization routinely reflows line breaks and can push a
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
Shell commands in SKILL.md call:
curlpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
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
Cvpr Camera Ready loads about 1.6k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 782 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). 782 words, ~1,650 tokens.
Download SKILL.mdSave it as
.claude/skills/cvpr-camera-ready/SKILL.md (or your agent's skills folder).- name
- cvpr-camera-ready
- description
- Use when preparing the final version of an accepted CVPR paper, covering de-anonymization, the dataset-release-by-camera-ready obligation, CVF open access versus the IEEE Xplore version of record, oral/highlight/poster preparation at conference scale, and arXiv/preprint synchronization after acceptance.
CVPR Camera-Ready
Use this after a CVPR acceptance (decisions landed February 20 in the 2026 cycle, conference in early June). The verified 2026 publication pipeline is described below; the mechanical camera-ready details for any given year — exact deadline, page allowance, IEEE forms — were not fetchable at check time and are 待核实: read the instructions email and the current Author Guidelines before building the final PDF.
Where the paper actually ends up
Accepted CVPR papers are published twice, and the two copies serve different audiences:
- CVF open access (
openaccess.thecvf.com): free to everyone, posted around the conference; the file is the accepted version apart from a watermark. This is the copy the field reads and the one bibliography tools usually find first. - IEEE Xplore: the version of record, under IEEE Computer Society co-sponsorship. Institutional reporting and some citation databases key off this one.
There is no author-side publication fee; costs ride on registration. Consequence for you: the PDF you upload at camera-ready is the artifact of record in both channels — there is no copy-editing pass to catch your mistakes.
De-anonymization without breakage
Reversing double-blind is edit work, not a switch:
- Restore authors, affiliations, and emails in the final class-file mode.
- Write real acknowledgements (grants, compute donors) — banned during review, expected now.
- Convert third-person self-citations back where the prose became misleading ("[12] showed" → "we showed in [12]" only where it clarifies lineage).
- Replace every "anonymous supplementary" pointer with live URLs: code repo, project page, dataset host. Links were banned at submission; the camera-ready is where they belong.
- Rebuild and re-read — de-anonymization routinely reflows line breaks and can push a tight page over whatever the final-version limit is that year.
The dataset clause has a deadline
Verified 2026 policy: if the paper claims a dataset release as a scientific contribution, the dataset must be publicly available no later than the camera-ready deadline. "Available upon request" or a landing page with a form does not meet the bar you promised reviewers. Licensing, hosting bandwidth, and consent/PII scrubbing all have to be finished on the paper's schedule, not the lab's.
# Release-readiness probe, run from a machine outside your institution
curl -sIL https://<dataset-host>/<archive> | grep -Ei 'HTTP|content-length'
sha256sum downloaded_archive.tar.gz # matches the checksum printed in the repo?
python3 - <<'EOF'
import json; m = json.load(open("meta/license.json"))
assert m["license"] and m["contact"], "license/contact missing from release metadata"
EOFOral, highlight, or poster: what changes
In 2026 the program split acceptances into tiers (program trackers reported 141 orals in four parallel tracks and 578 highlights among 4,090 acceptances — cross-check the official program before quoting). What each tier means for preparation:
| Outcome | Extra deliverables | Preparation reality |
|---|---|---|
| Oral | Talk + poster | A few minutes on a big stage; rehearse to time, design slides for the back row |
| Highlight | Poster, flagged in the program | Extra foot traffic; the poster must carry the paper alone |
| Poster | Poster | Thousands of attendees walk the halls; a legible headline result beats density |
| Award candidate | Talk logistics vary | Committee re-reads the paper — camera-ready polish matters twice |
Every tier presents at a venue with five-digit attendance (about 12,200 registrants in 2026), so print deadlines, poster-size specs, and the video/teaser uploads requested by the virtual platform belong on the same checklist as the PDF.
Show full SKILL.md (289 more words)Show less
Final-PDF quality assurance
The version of record gets no editorial pass, so run your own. Faults found in published CVPR PDFs year after year, all preventable in an afternoon:
- Rebuttal-promised changes never applied — diff the rebuttal's commitments ("we will cite [Foo]", "we will clarify the protocol") against the final text, item by item.
- Reviewer-visible numbers silently changed. If a table improved after acceptance (bug fix, longer training), say so in a footnote; unexplained deltas between the reviewed and published versions are the stuff of integrity threads.
- Camera-ready line numbers left on, draft watermarks, or
\usepackage{review}-mode artifacts from the author kit. - Broken cross-references from late figure surgery (
Fig. ??), and citations still pointing to arXiv versions of papers that have since been published (fix percvpr-related-work). - Author metadata: the OpenReview record, the PDF author block, and the form you file with the publisher must agree on names, order, and affiliations — mismatches propagate to IEEE Xplore and are painful to correct later.
Synchronizing the public record
After acceptance, converge the copies: update the arXiv version to match the camera-ready (arXiv posting was already legal during review), point the repo README at the CVF page once it exists, and use one canonical BibTeX everywhere — mixed arXiv/proceedings citations fragment your citation count for years. Keep the media embargo in mind in reverse: it lifted at acceptance, so coordinated publicity is now allowed.
Reverify each cycle (all 待核实 for the current year)
- Camera-ready deadline, final page allowance, and whether an extra page is granted.
- Whether the final template differs from the submission template (line numbers off, copyright block on).
- IEEE copyright/e-forms and PDF validation requirements.
- Registration-per-paper and in-person presentation obligations.
- Poster dimensions, talk lengths, and virtual-platform upload list.
Output format
[Camera-ready status] on-track / blocked
[Version-of-record checks] deanonymized · acknowledgements · live links · page fit
[Dataset clause] not-claimed / released-and-probed / BLOCKED: <gap>
[Tier prep] oral/highlight/poster deliverables and dates
[Public sync] arXiv updated · repo pointed · canonical BibTeX chosen
[待核实 items] <forms, deadline, page allowance for this year>© 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 CVPR-Skills/skills/cvpr-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cvpr 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 |
|---|---|---|---|---|---|---|
| Cvpr Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Read arXiv Paperkarpathy/nanochat | 59k | 1 repos | ~494 | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Openalex Databaseneflibata-feng/MyArxiv-Agent | 126 | 12 repos | ~3k | Automated safety check: Pass | Custom licence | |
| Citation ManagementK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.9k | Automated safety check: Notes | MIT | |
| Citation Managementneflibata-feng/MyArxiv-Agent | 126 | 19 repos | ~8.1k | Automated safety check: Notes | MIT |
Similar skills
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
Citation Management
K-Dense-AI/claude-scientific-writer
Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.
Citation Management
neflibata-feng/MyArxiv-Agent
Comprehensive citation management for academic research. An agent skill from neflibata-feng/MyArxiv-Agent.
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
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…
Related
Works with
Categories
Questions about Cvpr Camera Ready
What does Cvpr Camera Ready do?
A skill your agent uses when preparing the final version of an accepted CVPR paper, covering de-anonymization, the dataset-release-by-camera-ready obligation, CVF open access versus the IEEE Xplore…. Cvpr Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing the final version of an accepted CVPR paper, covering de-anonymization, the dataset-release-by-camera-ready obligation, CVF open access versus the IEEE Xplore version of record, oral/highlight/poster preparation at conference scale, and arXiv/preprint synchronization after acceptance.
When should I use Cvpr Camera Ready?
Cvpr Camera Ready fits situations like: preparing the final version of an accepted CVPR paper; covering de-anonymization; the dataset-release-by-camera-ready obligation; CVF open access versus the IEEE Xplore version of record.
How do I install Cvpr Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-camera-ready -a claude-code`. Or copy the skill folder (CVPR-Skills/skills/cvpr-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cvpr-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Cvpr Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-camera-ready -a codex`. Or copy the skill folder (CVPR-Skills/skills/cvpr-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cvpr-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Cvpr 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 cvpr-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/cvpr-camera-ready, .gemini/skills/cvpr-camera-ready, .github/skills/cvpr-camera-ready and .opencode/skills/cvpr-camera-ready in your project.
What does Cvpr Camera Ready need to run?
Going by SKILL.md and its folder, Cvpr Camera Ready needs the command-line tools its instructions call (curl and python3). Our summary lists: Python 3.
Does Cvpr Camera Ready access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Cvpr 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 Cvpr Camera Ready use?
Cvpr 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 Cvpr Camera Ready use?
About 1.6k tokens (SKILL.md is roughly 6.6k 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 Cvpr Camera Ready?
Skills that share tags, products or a category with Cvpr Camera Ready: Read arXiv Paper (karpathy/nanochat, 59k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Openalex Database (neflibata-feng/MyArxiv-Agent, 126 stars) and Citation Management (K-Dense-AI/claude-scientific-writer, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cvpr 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.