Aria Hidden Body
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Do not use aria-hidden on the document body.
A skill your agent uses when deciding what belongs in an IEEE VIS paper body versus its supplemental materials, covering the VGTC/TVCG 9+2 page budget, the supplemental video that VIS reviewers…
MITAuto-check passed
Install Vis Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-supplementary .claude/skills/vis-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 "vis-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-supplementary into .claude/skills/vis-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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/VIS-Skills/skills/vis-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 vis-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-supplementary .agents/skills/vis-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 "vis-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-supplementary into .agents/skills/vis-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-supplementary .cursor/skills/vis-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 "vis-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-supplementary into .cursor/skills/vis-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 VIS-Skills/skills/vis-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 vis-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-supplementary .gemini/skills/vis-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 "vis-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-supplementary into .gemini/skills/vis-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-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 vis-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/VIS-Skills/skills/vis-supplementary .github/skills/vis-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 "vis-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-supplementary into .github/skills/vis-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-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 vis-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/VIS-Skills/skills/vis-supplementary .opencode/skills/vis-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 "vis-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-supplementary into .opencode/skills/vis-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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
vis-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 437 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 an IEEE VIS paper body versus its supplemental materials, covering the VGTC/TVCG 9+2 page budget, the supplemental video that VIS reviewers…
- Deciding what belongs in an IEEE VIS paper body versus its supplemental materials
- SKILL.md covers What goes where, The supplemental video (a…, The page-budget discipline and Double-blind supplemental…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the VGTC/TVCG 9+2 page budget
What it does
Vis Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in an IEEE VIS paper body versus its supplemental materials, covering the VGTC/TVCG 9+2 page budget, the supplemental video that VIS reviewers routinely watch, the one-week supplemental deadline extension, double-blind supplemental anonymization, and how to split a visualization paper between the reviewed pages and the archive.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Deciding what belongs in an IEEE VIS paper body versus its supplemental materials
- Covering the VGTC/TVCG 9+2 page budget
- The supplemental video that VIS reviewers routinely watch
- The one-week supplemental deadline extension
Example prompts
- “/vis-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
Vis Supplementary loads about 1.3k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 437 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). 437 words, ~1,283 tokens.
Download SKILL.mdSave it as
.claude/skills/vis-supplementary/SKILL.md (or your agent's skills folder).- name
- vis-supplementary
- description
- Use when deciding what belongs in an IEEE VIS paper body versus its supplemental materials, covering the VGTC/TVCG 9+2 page budget, the supplemental video that VIS reviewers routinely watch, the one-week supplemental deadline extension, double-blind supplemental anonymization, and how to split a visualization paper between the reviewed pages and the archive.
VIS Supplementary
Use this when assembling IEEE VIS supplemental material. The governing rule is strict: the paper must be judgeable from the reviewed pages alone. But VIS is unusual among conferences in how much its reviewers rely on the supplemental video and code to understand an interactive contribution — so the split is not "body carries everything, supplement is optional" but "body carries the decision, supplement makes the interaction and reproduction legible."
What goes where
| Content | Body (within 9-page budget) | Supplemental (archive/video) |
|---|---|---|
| The contribution and its claims | Yes | — |
| Core technique / system design / study design | Yes | Full parameter grids, extra configs |
| Headline results and the evaluation that backs them | Yes | Full result tables, secondary conditions |
| The encoding/interaction rationale | Yes | — |
| A static figure of the interface | Yes | The video showing the interaction in motion |
| Statistical tests behind a claim | The result + test named | The analysis notebook |
| Datasets, stimuli, raw study responses | Summary + selection criterion | The full data/stimuli |
| Reproduction instructions | A pointer | The README + build/run scripts |
If a reviewer would need to open the archive to know whether to accept, the paper is mis-partitioned — move that evidence into the body. But an interactive system that cannot be understood without seeing it move should ship a video; a static screenshot alone under-sells it.
The supplemental video (a VIS-specific expectation)
For technique and system papers, the video is often how reviewers judge whether an interaction actually works. Treat it as a first-class deliverable:
[Length] keep to the customary short length; lead with the contribution, not a long intro
[Content] show the real interaction on real data, at usable speed; caption what to watch
[Quality] legible resolution, readable text, no stutter; a required codec/container
[Anonymity] if double-blind, strip affiliation slates, voice-over names, visible usernames,
desktop clutter, and watermarked project URLs
[Deadline] VIS 2026 gives a one-week window AFTER the paper deadline for supplemental material —
use it to finish and anonymize the video, not to keep editing the paperShow full SKILL.md (200 more words)Show less
The page-budget discipline
VIS's VGTC/TVCG budget is 9 pages of content + up to 2 pages of references and acknowledgements. It counts figures and tables — and visualization papers are figure-heavy. Consequences:
- Keep the evaluation that decides acceptance and the encoding rationale in the body.
- Push full parameter tables, additional conditions, extra stimuli, and long apparatus details to the supplemental archive with explicit forward references.
- Do not use the supplement to smuggle in a result that would not fit — an argument that only closes with material outside the reviewed pages reads as unreviewable.
- Budget figure space deliberately: one well-designed teaser and the key result figures earn their space; a wall of thumbnails does not.
Double-blind supplemental rules (when you opt in)
[No identity] no authors, affiliations, acknowledgements, grants, cluster paths, lab names, or
repo owners anywhere in the archive, README, or video
[Anonymized links] the open-materials link points at an anonymizing host, not a personal repo/OSF
[Clean archive] no .git history, .DS_Store, credentials, caches, or huge irrelevant files
[Playable] verify the video plays in a standard player and the archive unzips and builds
from a one-minute README on a fresh machineVignette: splitting a system + study paper
A paper contributing an interactive analytics system plus a user study: the body keeps the design rationale, the system's key views, the headline study results with effect sizes, and the threats; the supplement holds the video demonstrating the interaction, the system's source with a build script, the study stimuli and anonymized responses, and the analysis notebook. Nothing decision-critical lives only in the archive, but the interaction is only fully legible via the video.
Output format
[Supplement status] ready / needs fixes / not ready
[Partition check] anything decision-critical outside the body? <none / move: what>
[Video] present and legible? shows real interaction? anonymized (if double-blind)? yes/no
[Page budget] body within 9 pages? refs within 2? figures earning their space? yes/no
[Anonymity] archive + video clean of identity + metadata? passed/issues
[Body dependency] <what a reviewer can decide without opening the archive>© 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-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vis 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 |
|---|---|---|---|---|---|---|
| Vis Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Aria Hidden Bodythedaviddias/Front-End-Checklist | 74k | — | ~444 | Automated safety check: Pass | MIT | |
| Meta In Bodythedaviddias/Front-End-Checklist | 74k | — | ~541 | Automated safety check: Pass | MIT | |
| Pull Request Title and Body Writeropeninterpreter/openinterpreter | 69k | 2 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Function Bodyonnx/onnx | 22k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Inline Visget-bb/bb | 4.2k | — | ~614 | Automated safety check: Pass | MIT |
Similar skills
Meta In Body
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing HTML document structure.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
Add Function Body
onnx/onnx
Add a function body definition to an ONNX operator, defining how it decomposes into simpler ops.
Inline Vis
get-bb/bb
Show a newly created or updated HTML demo, chart, or report, or Markdown plan, summary, or notes from the workspace or thread storage inline in BB chat with the inline-vis directive.
Icdm Supplementary
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when organizing supplementary and appendix material for an ICDM (IEEE International Conference on Data Mining) paper - deciding what belongs in the body, in an appendix that…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Vis Supplementary
What does Vis Supplementary do?
A skill your agent uses when deciding what belongs in an IEEE VIS paper body versus its supplemental materials, covering the VGTC/TVCG 9+2 page budget, the supplemental video that VIS reviewers…. Vis Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in an IEEE VIS paper body versus its supplemental materials, covering the VGTC/TVCG 9+2 page budget, the supplemental video that VIS reviewers routinely watch, the one-week supplemental deadline extension, double-blind supplemental anonymization, and how to split a visualization paper between the reviewed pages and the archive.
When should I use Vis Supplementary?
Vis Supplementary fits situations like: deciding what belongs in an IEEE VIS paper body versus its supplemental materials; covering the VGTC/TVCG 9+2 page budget; the supplemental video that VIS reviewers routinely watch; the one-week supplemental deadline extension.
How do I install Vis Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-supplementary -a claude-code`. Or copy the skill folder (VIS-Skills/skills/vis-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vis-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Vis Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-supplementary -a codex`. Or copy the skill folder (VIS-Skills/skills/vis-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vis-supplementary in your project. Codex loads it when a task matches its description.
Can I use Vis 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 vis-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/vis-supplementary, .gemini/skills/vis-supplementary, .github/skills/vis-supplementary and .opencode/skills/vis-supplementary in your project.
What does Vis Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Vis Supplementary is instructions for the agent only.
Does Vis 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 Vis 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 Vis Supplementary use?
Vis 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 Vis Supplementary use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vis Supplementary?
Skills that share tags, products or a category with Vis Supplementary: Aria Hidden Body (thedaviddias/Front-End-Checklist, 74k stars), Meta In Body (thedaviddias/Front-End-Checklist, 74k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Add Function Body (onnx/onnx, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vis 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.