Ito Compute
affaan-m/ECC
Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, revoke device credentials, and run explicitly gated node qualification through the separately…
A skill your agent uses when deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact, covering the LNCS page limits, the rule that reviewers…
MITAuto-check passed
Install Cav Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-supplementary --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/CAV-Skills/skills/cav-supplementary .claude/skills/cav-supplementary && 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 "cav-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-supplementary into .claude/skills/cav-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-supplementary", 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/CAV-Skills/skills/cav-supplementaryType 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 cav-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-supplementary --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/CAV-Skills/skills/cav-supplementary .agents/skills/cav-supplementary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cav-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-supplementary into .agents/skills/cav-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-supplementary", 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 cav-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-supplementary --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/CAV-Skills/skills/cav-supplementary .cursor/skills/cav-supplementary && 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 "cav-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-supplementary into .cursor/skills/cav-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-supplementary", 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 CAV-Skills/skills/cav-supplementary--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 cav-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-supplementary --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/CAV-Skills/skills/cav-supplementary .gemini/skills/cav-supplementary && 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 "cav-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-supplementary into .gemini/skills/cav-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-supplementary", 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 cav-supplementaryInstalls 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 cav-supplementary -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/CAV-Skills/skills/cav-supplementary .github/skills/cav-supplementary && 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 "cav-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-supplementary into .github/skills/cav-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-supplementary", 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 cav-supplementary -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 cav-supplementary --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/CAV-Skills/skills/cav-supplementary .opencode/skills/cav-supplementary && 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 "cav-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-supplementary into .opencode/skills/cav-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-supplementary", 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
cav-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.2k 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 deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact, covering the LNCS page limits, the rule that reviewers…
- Deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact
- SKILL.md covers What goes where, The page-limit discipline, Double-anonymous supplementary… and Appendix architecture, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the LNCS page limits
What it does
Cav Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact, covering the LNCS page limits, the rule that reviewers are not obliged to read the appendix so decision-critical content stays in the body, where full proofs and benchmark tables live, and double-anonymous supplementary material for the anonymized categories.
Its SKILL.md is about 1.2k 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
- Deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact
- Covering the LNCS page limits
- The rule that reviewers are not obliged to read the appendix so decision-critical content stays in the body
- Where full proofs and benchmark tables live
Example prompts
- “/cav-supplementary”
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
Cav Supplementary loads about 1.2k tokens when it runs. Until then it costs about 100 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,199 tokens.
Download SKILL.mdSave it as
.claude/skills/cav-supplementary/SKILL.md (or your agent's skills folder).- name
- cav-supplementary
- description
- Use when deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact, covering the LNCS page limits, the rule that reviewers are not obliged to read the appendix so decision-critical content stays in the body, where full proofs and benchmark tables live, and double-anonymous supplementary material for the anonymized categories.
CAV Supplementary
Use this when assembling CAV supplementary material. The governing rule is strict and specific to CAV's format: a clearly marked appendix is allowed, but reviewers are not obliged to read it. So the paper must be judgeable from the body alone — anything a reviewer must see to accept lives inside the page limit, and the appendix and artifact only support it.
What goes where
| Content | Body (within the page limit) | Appendix / artifact |
|---|---|---|
| The problem, the technique, the main theorem | Yes | — |
| Proof idea / sketch of the main result | Yes | Full formal proof |
| Supporting lemmas | Statement + role | Full proofs |
| Headline benchmark comparison + resource limits | Yes | Full per-instance tables |
| Soundness/differential-check result | The result + method | The raw logs and witnesses |
| Benchmark set + selection | Summary + revision | The full instance list, fetch scripts |
| Tool build/run instructions | A pointer | README + scripts (artifact) |
| Proof certificates / witnesses | A pointer | The certificates + a checker (artifact) |
If a reviewer would need to open the appendix or artifact to know whether the theorem holds or the comparison is fair, the paper is mis-partitioned — move that content into the body.
The page-limit discipline
CAV's LNCS limits (Regular 18 pages; Short Tool / Application / Industrial 10 pages) exclude references and appendices, but the appendix is optional-to-read. Consequences:
- Keep the main theorem's proof idea and the headline benchmark result with its resource limits in the body — they are decision-critical.
- Move full formal proofs, per-instance benchmark tables, and extra property classes to the appendix or artifact with explicit forward references.
- Do not use the appendix to smuggle in a result that would not fit — an argument that only closes with unread material reads as unreviewable, and the stage-1 filter is unforgiving.
Show full SKILL.md (205 more words)Show less
Double-anonymous supplementary rules (Regular and Application papers)
[No identity] no authors, affiliations, acknowledgements, grants, cluster paths, or repo owners in
the appendix or the review-time artifact; anonymize the tool/solver name
[Anonymized links] the artifact link points at an anonymizing host, not a personal repo or tool site
[Clean archive] no .git history, .DS_Store, credentials, caches, or large irrelevant files
[Opens clean] verify the archive unpacks and the README orients a reviewer in minutes on a fresh
machine (the AEC smoke test mirrors this)Tool and Industrial papers are not anonymized, so their supplementary material may name the tool — but should still be clean and self-orienting.
Appendix architecture
- Order appendix sections to mirror the paper: main-theorem proof first, then lemma proofs, then full benchmark tables, then extra experiments — reviewers navigate by the claim, not by page number.
- Keep each appendix section referenced from the body at least once; orphaned material is invisible under discretionary reading.
- Confirm on the current CFP that appendices are inside the same PDF (not a separate upload) and that they do not count against the limit — this is the CAV norm but re-verify.
Vignette: splitting a technique-plus-tool paper
A Regular Paper with one main soundness theorem, three lemmas, and a large benchmark study: the body keeps the problem, the technique, the main theorem with its proof idea, the lemma statements, and the headline cactus/scatter comparison with the resource limits and the soundness cross-check; the appendix holds the full proofs; the artifact holds the pinned benchmark set, the per-instance logs, the seeds, the proof witnesses with a checker, and the reproduction scripts. Nothing decision-critical lives only in unread material, because the stage-1 reviewers judge from the body.
Output format
[Supplement status] ready / needs fixes / not ready
[Partition check] anything decision-critical outside the body? <none / move: what>
[Page limit] body within the category limit? appendix marked and referenced? yes/no
[Anonymity] appendix + review artifact clean of identity (Regular/Application)? passed/issues
[Body dependency] <what a reviewer can decide without opening the appendix/artifact>© 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 CAV-Skills/skills/cav-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cav Supplementary 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 |
|---|---|---|---|---|---|---|
| Cav Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Ito Computeaffaan-m/ECC | 276k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Senior Computer Visiondavila7/claude-code-templates | 33k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Senior Computer Visionalirezarezvani/claude-skills | 28k | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| GCP Computesickn33/agentic-awesome-skills | 47k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Computer UseQwenLM/qwen-code | 28k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Senior Computer Vision
davila7/claude-code-templates
World-class computer vision skill for image/video processing, object detection, segmentation, and visual AI systems.
Senior Computer Vision
alirezarezvani/claude-skills
Computer vision engineering skill for object detection, image segmentation, and visual AI systems.
GCP Compute
sickn33/agentic-awesome-skills
Manage Compute Engine instances and instance templates. An agent skill from sickn33/agentic-awesome-skills.
Computer Use
QwenLM/qwen-code
Control local desktop applications through Computer Use for tasks that require reading or operating app UI.
International Conference On Computer Aided Verification
franklee16/academic-research-skills
A skill your agent uses when targeting International Conference on Computer Aided Verification (CAV) or deciding whether a computer-science manuscript fits this venue.
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 Cav Supplementary
What does Cav Supplementary do?
A skill your agent uses when deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact, covering the LNCS page limits, the rule that reviewers…. Cav Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact, covering the LNCS page limits, the rule that reviewers are not obliged to read the appendix so decision-critical content stays in the body, where full proofs and benchmark tables live, and double-anonymous supplementary material for the anonymized categories.
When should I use Cav Supplementary?
Cav Supplementary fits situations like: deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact; covering the LNCS page limits; the rule that reviewers are not obliged to read the appendix so decision-critical content stays in the body; where full proofs and benchmark tables live.
How do I install Cav Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-supplementary -a claude-code`. Or copy the skill folder (CAV-Skills/skills/cav-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cav-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Cav Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-supplementary -a codex`. Or copy the skill folder (CAV-Skills/skills/cav-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cav-supplementary in your project. Codex loads it when a task matches its description.
Can I use Cav Supplementary 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 cav-supplementary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cav-supplementary, .gemini/skills/cav-supplementary, .github/skills/cav-supplementary and .opencode/skills/cav-supplementary in your project.
What does Cav Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Cav Supplementary is instructions for the agent only.
Does Cav Supplementary 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 Cav Supplementary 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 Cav Supplementary use?
Cav Supplementary 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 Cav Supplementary use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Cav Supplementary?
Skills that share tags, products or a category with Cav Supplementary: Ito Compute (affaan-m/ECC, 276k stars), Senior Computer Vision (davila7/claude-code-templates, 33k stars), Senior Computer Vision (alirezarezvani/claude-skills, 28k stars) and GCP Compute (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 Cav Supplementary?
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.