Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV, TACAS, FMCAD, VMCAI, POPL/PLDI, and the journals (FMSD, JAR…
Install Cav Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-related-work --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-related-work .claude/skills/cav-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-related-work into .claude/skills/cav-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-related-work --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-related-work .agents/skills/cav-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-related-work into .agents/skills/cav-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-related-work --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-related-work .cursor/skills/cav-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-related-work into .cursor/skills/cav-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-related-work --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-related-work .gemini/skills/cav-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-related-work into .gemini/skills/cav-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/cav-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-related-work into .github/skills/cav-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/cav-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-related-work into .opencode/skills/cav-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-related-work", 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-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 517 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV, TACAS, FMCAD, VMCAI, POPL/PLDI, and the journals (FMSD, JAR…
- Positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV
- SKILL.md covers Positioning checks, Verification literature lanes, Delta-first positioning vignette and Concurrent and prior-version…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The journals (FMSD
What it does
Cav Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV, TACAS, FMCAD, VMCAI, POPL/PLDI, and the journals (FMSD, JAR, TOCL, STTT), writing delta-first contrast rather than a citation catalog, crediting the right benchmark and tool lineages, keeping self-citations double-anonymous for the anonymized categories, and handling concurrent and prior-version overlap.
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.
It sits in Research & Science, covering Literature review, Citation management and Positioning and messaging. 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
- Positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV
- The journals (FMSD
- Writing delta-first contrast rather than a citation catalog
- Crediting the right benchmark and tool lineages
Example prompts
- “/cav-related-work”
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 Related Work loads about 1.3k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 517 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). 517 words, ~1,291 tokens.
Download SKILL.mdSave it as
.claude/skills/cav-related-work/SKILL.md (or your agent's skills folder).- name
- cav-related-work
- description
- Use when positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV, TACAS, FMCAD, VMCAI, POPL/PLDI, and the journals (FMSD, JAR, TOCL, STTT), writing delta-first contrast rather than a citation catalog, crediting the right benchmark and tool lineages, keeping self-citations double-anonymous for the anonymized categories, and handling concurrent and prior-version overlap.
CAV Related Work
Use this to audit novelty and eligibility. CAV reviewers are close to the verification literature and expect to see where your paper sits relative to the nearest prior technique or tool — stated as a delta, not a list. Reopen the current CFP for dual-submission, anonymity, and prior-publication rules before advising authors.
Positioning checks
- Separate the verification novelty from the engineering effort. What is new: an algorithm, a decision procedure, an abstraction, a soundness result, a tool capability, or a benchmark regime nobody had covered?
- Cover the verification lanes. CAV reviewers expect the flagship venues, the tool ecosystems, and the journals — not just the papers nearest your method (see the table). A bibliography missing the obvious sibling work reads as unaware.
- Write delta-first. Each closely related paper gets one sentence naming what it did and one naming what you do differently — a technical contrast (what their method cannot do that yours can), not a summary.
- Credit tool and benchmark lineages. If you extend or compare against a solver/model checker or use a standard benchmark set, cite the tool paper and the benchmark/competition to their real origin — and to the right venue (Z3 is TACAS, not CAV; see the exemplars guardrails).
- Preserve double-anonymity where required. For Regular and Application papers, cite your own prior work in the third person and never link reviewers to an identity-revealing preprint, repository, or tool homepage. (Tool and Industrial papers are not anonymized.)
- Declare overlap with any prior workshop/conference version or concurrent submission; do not re-submit archival work as new.
Show full SKILL.md (261 more words)Show less
Verification literature lanes
| Lane | Typical venues | What CAV reviewers check |
|---|---|---|
| Flagship verification | CAV, TACAS | Whether the nearest broad technique/tool is compared or distinguished |
| Hardware / design | FMCAD | Whether hardware-model-checking predecessors are credited |
| Model checking & abstract interpretation | VMCAI | Whether foundational analysis work is engaged |
| Reasoning & proof | IJCAR, LPAR, ITP, CADE | Whether the proof/solver lineage is cited to its origin |
| PL foundations | POPL, PLDI, OOPSLA | Whether borrowed semantics/analysis ideas are credited |
| Journals | FMSD, JAR, TOCL, STTT | Whether deeper journal-length treatments of the topic are engaged |
A bibliography that cites only your own subarea tells a reviewer the delta may be smaller than claimed; one that reaches the sibling flagships, the tool papers, and the journals signals command of the field.
Delta-first positioning vignette
Suppose the paper proposes a new interpolation-based invariant-synthesis technique. Its nearest neighbors: the foundational interpolation-and-model-checking line (technique, different property class), a TACAS tool that computes invariants by a different abstraction (tool, no interpolants), and a journal study of interpolant quality (analysis, no synthesis method). The novelty sentence should name all three contrasts — synthesis where the study offered only analysis, interpolant-based where the tool used a different abstraction, and a new property class beyond the foundational line — and cite each to its correct venue.
Concurrent and prior-version judgment calls
[Concurrent arXiv work] cite neutrally, state the technical difference, avoid unverifiable
priority claims; keep the citation anonymous for Regular/Application
[Your workshop version] often non-archival and citable, but confirm against the current CFP and
phrase so anonymity survives (anonymized categories)
[Prior tool-paper version] declare the overlap; state what the new paper adds beyond the tool release
[Archival status unclear] declare the overlap in the submission form rather than guessingEligibility red flags
- Substantial text overlap with a published paper by the same authors (self-plagiarism risk).
- A "new" evaluation that re-reports a prior benchmark run without a new technique or question.
- Attributing a technique/tool to the wrong venue (the TACAS/FMCAD/VMCAI-vs-CAV trap) — a reviewer who knows the lineage reads it as carelessness.
Output format
[Eligibility] clear / needs declaration / risky
[Lanes covered] <flagship / hardware / model-checking-AI / reasoning / PL / journals>
[Nearest 3 works] <work -> one-line technical delta -> correct venue cited?>
[Archival-overlap risk] <none / declare: what>
[Novelty sentence] <CAV-ready contribution contrast against the nearest prior technique/tool>© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cav Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
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
Categories
Questions about Cav Related Work
What does Cav Related Work do?
A skill your agent uses when positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV, TACAS, FMCAD, VMCAI, POPL/PLDI, and the journals (FMSD, JAR…. Cav Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV, TACAS, FMCAD, VMCAI, POPL/PLDI, and the journals (FMSD, JAR, TOCL, STTT), writing delta-first contrast rather than a citation catalog, crediting the right benchmark and tool lineages, keeping self-citations double-anonymous for the anonymized categories, and handling concurrent and prior-version overlap.
When should I use Cav Related Work?
Cav Related Work fits situations like: positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV; the journals (FMSD; writing delta-first contrast rather than a citation catalog; crediting the right benchmark and tool lineages.
How do I install Cav Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-related-work -a claude-code`. Or copy the skill folder (CAV-Skills/skills/cav-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cav-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Cav Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-related-work -a codex`. Or copy the skill folder (CAV-Skills/skills/cav-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cav-related-work in your project. Codex loads it when a task matches its description.
Can I use Cav Related Work 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-related-work -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-related-work, .gemini/skills/cav-related-work, .github/skills/cav-related-work and .opencode/skills/cav-related-work in your project.
What does Cav Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Cav Related Work is instructions for the agent only.
Does Cav Related Work 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 Related Work 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 Related Work use?
Cav Related Work 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 Related Work use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 Related Work?
Skills that share tags, products or a category with Cav Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cav Related Work?
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.