Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
A skill your agent uses when positioning an IEEE VIS submission against the visualization literature across TVCG, the six VIS areas, EuroVis/CGF, PacificVis, and adjacent HCI/graphics venues…
Install Vis Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-related-work .claude/skills/vis-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 "vis-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-related-work into .claude/skills/vis-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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/VIS-Skills/skills/vis-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 vis-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-related-work .agents/skills/vis-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 "vis-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-related-work into .agents/skills/vis-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-related-work .cursor/skills/vis-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 "vis-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-related-work into .cursor/skills/vis-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 VIS-Skills/skills/vis-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 vis-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-related-work .gemini/skills/vis-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 "vis-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-related-work into .gemini/skills/vis-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-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 vis-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/VIS-Skills/skills/vis-related-work .github/skills/vis-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 "vis-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-related-work into .github/skills/vis-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-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 vis-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/VIS-Skills/skills/vis-related-work .opencode/skills/vis-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 "vis-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-related-work into .opencode/skills/vis-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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
vis-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 482 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning an IEEE VIS submission against the visualization literature across TVCG, the six VIS areas, EuroVis/CGF, PacificVis, and adjacent HCI/graphics venues…
- Positioning an IEEE VIS submission against the visualization literature across TVCG
- SKILL.md covers Positioning checks, Visualization 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 six VIS areas
What it does
Vis Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an IEEE VIS submission against the visualization literature across TVCG, the six VIS areas, EuroVis/CGF, PacificVis, and adjacent HCI/graphics venues, writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind when opted in, and handling concurrent, preprint, and prior-version overlap for a TVCG journal article.
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.
It sits in Research & Science, covering Literature review, Citation management and Academic paper search. 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 an IEEE VIS submission against the visualization literature across TVCG
- The six VIS areas
- Adjacent HCI/graphics venues
- Writing delta-first contrast rather than a citation catalog
Example prompts
- “/vis-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
Vis Related Work loads about 1.2k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 482 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). 482 words, ~1,206 tokens.
Download SKILL.mdSave it as
.claude/skills/vis-related-work/SKILL.md (or your agent's skills folder).- name
- vis-related-work
- description
- Use when positioning an IEEE VIS submission against the visualization literature across TVCG, the six VIS areas, EuroVis/CGF, PacificVis, and adjacent HCI/graphics venues, writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind when opted in, and handling concurrent, preprint, and prior-version overlap for a TVCG journal article.
VIS Related Work
Use this to audit novelty and positioning. IEEE VIS reviewers are close to the visualization literature and expect to see where your paper sits relative to the nearest prior work — stated as a delta, not a list. Because VIS full papers are TVCG articles, the novelty bar is a journal bar. Reopen the current call for dual-submission, anonymity, and prior-publication rules before advising authors.
Positioning checks
- Separate the visualization novelty from the engineering. What is new: a visual encoding, an interaction technique, a system integrating known parts in a newly effective way, an empirical finding about perception or use, or a model/methodology?
- Cover the visualization lanes. VIS reviewers expect TVCG/VIS prior work in your area, the European (EuroVis / Computer Graphics Forum) and Pacific (PacificVis) literature, and the adjacent HCI/graphics venues when you borrow from them (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 — not a summary. Position, don't catalog.
- Preserve double-blind (if opted in). Cite your own prior work in the third person and never link reviewers to an identity-revealing preprint, repository, demo, or homepage.
- Declare overlap with any prior short-paper, poster, or workshop version, or a concurrent submission; do not re-submit archival work as new.
Visualization literature lanes
| Lane | Typical venues | What VIS reviewers check |
|---|---|---|
| Core VIS by area | IEEE VIS / TVCG (your primary area of the six) | Whether the nearest technique/study/system in your area is compared or distinguished |
| European visualization | EuroVis, Computer Graphics Forum (CGF) | Whether closely related European work is credited |
| Pacific / regional | PacificVis, and regional venues | Whether adjacent regional contributions are engaged |
| Adjacent HCI | CHI, UIST | Whether interaction/usability predecessors are cited to origin |
| Adjacent graphics/analysis | SIGGRAPH, KDD/ML when relevant | Whether borrowed rendering or analytics methods are cited to their real source |
A bibliography that cites only your own narrow topic tells a reviewer the delta may be smaller than claimed; one that reaches the sibling areas, EuroVis, and the adjacent venues signals command of the field.
Show full SKILL.md (134 more words)Show less
Delta-first positioning vignette
Suppose the paper proposes a new set-visualization technique. Its nearest neighbors: a matrix-based set technique (dense but hard to read at scale), an Euler-diagram approach (intuitive but not scalable), and an aggregation-based tabular technique (scalable but less expressive for individual elements). The novelty sentence should name all three contrasts — readability where the matrix failed, scale where the Euler diagram failed, and expressiveness where the tabular technique traded it away — rather than summarizing each.
Concurrent and prior-version judgment calls
[Concurrent arXiv work] cite neutrally, state the technical difference, avoid unverifiable
priority claims; keep the citation double-blind if opted in
[Your short paper/poster] usually non-archival and citable, but confirm against the current call
and phrase so anonymity survives
[Prior workshop version] declare the overlap and state what the full paper adds beyond it
[Archival status unclear] declare the overlap in the submission form rather than guessing a
chair's interpretationEligibility red flags
- Substantial text or figure overlap with a published paper by the same authors (self-plagiarism).
- A "new" system that re-reports a prior technique's results without a new contribution.
- Citations exclusively to non-visualization venues, signaling the paper may be a visitor from HCI/ML/graphics rerouted without reframing for a visualization audience.
Output format
[Eligibility] clear / needs declaration / risky
[Lanes covered] <core-VIS-area / EuroVis-CGF / PacificVis / adjacent-HCI / adjacent-graphics>
[Nearest 3 works] <work -> one-line delta>
[Archival-overlap risk] <none / declare: what>
[Novelty sentence] <VIS-ready contribution contrast against the nearest prior work>© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vis 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 |
|---|---|---|---|---|---|---|
| Vis Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Preprint Search on bioRxivLigphiDonk/Oh-my--paper | 739 | 12 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Systematic Literature Review Builderbytedance/deer-flow | 84k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Paper Research on arXivXiaomiMiMo/MiMo-Code | 14k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Literature Review AgentAr9av/PaperOrchestra | 679 | 1 repos | ~5.2k | Automated safety check: Pass | Custom licence |
Similar skills
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.
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.
Paper Research on arXiv
XiaomiMiMo/MiMo-Code
Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.
Literature Review Agent
Ar9av/PaperOrchestra
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.
Autonomous Research
federicodeponte/opendraft
An 18-agent pipeline that turns one topic line into a drafted research paper, literature review, or thesis chapter.
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 Vis Related Work
What does Vis Related Work do?
A skill your agent uses when positioning an IEEE VIS submission against the visualization literature across TVCG, the six VIS areas, EuroVis/CGF, PacificVis, and adjacent HCI/graphics venues…. Vis Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an IEEE VIS submission against the visualization literature across TVCG, the six VIS areas, EuroVis/CGF, PacificVis, and adjacent HCI/graphics venues, writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind when opted in, and handling concurrent, preprint, and prior-version overlap for a TVCG journal article.
When should I use Vis Related Work?
Vis Related Work fits situations like: positioning an IEEE VIS submission against the visualization literature across TVCG; the six VIS areas; adjacent HCI/graphics venues; writing delta-first contrast rather than a citation catalog.
How do I install Vis Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-related-work -a claude-code`. Or copy the skill folder (VIS-Skills/skills/vis-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vis-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Vis Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-related-work -a codex`. Or copy the skill folder (VIS-Skills/skills/vis-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vis-related-work in your project. Codex loads it when a task matches its description.
Can I use Vis 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 vis-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/vis-related-work, .gemini/skills/vis-related-work, .github/skills/vis-related-work and .opencode/skills/vis-related-work in your project.
What does Vis Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Vis Related Work is instructions for the agent only.
Does Vis 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 Vis 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 Vis Related Work use?
Vis 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 Vis Related Work 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 Vis Related Work?
Skills that share tags, products or a category with Vis Related Work: Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Preprint Search on bioRxiv (LigphiDonk/Oh-my--paper, 739 stars), Systematic Literature Review Builder (bytedance/deer-flow, 84k stars) and Paper Research on arXiv (XiaomiMiMo/MiMo-Code, 14k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vis 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.