Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
A skill your agent uses when drafting IEEE VIS author responses across the two-phase review, covering the first-round reviewer discussion, and — distinctively — the conditional-accept second-round…
MITAuto-check passed
Install Vis Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-author-response --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-author-response .claude/skills/vis-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-author-response into .claude/skills/vis-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-author-response", 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-author-responseType 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-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-author-response --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-author-response .agents/skills/vis-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-author-response into .agents/skills/vis-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-author-response", 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-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-author-response --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-author-response .cursor/skills/vis-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-author-response into .cursor/skills/vis-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-author-response", 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-author-response--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-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-author-response --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-author-response .gemini/skills/vis-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-author-response into .gemini/skills/vis-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-author-response", 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-author-responseInstalls 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-author-response -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-author-response .github/skills/vis-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-author-response into .github/skills/vis-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-author-response", 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-author-response -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-author-response --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-author-response .opencode/skills/vis-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-author-response into .opencode/skills/vis-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-author-response", 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-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 557 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting IEEE VIS author responses across the two-phase review, covering the first-round reviewer discussion, and — distinctively — the conditional-accept second-round…
- Drafting IEEE VIS author responses across the two-phase review
- SKILL.md covers Triage (both turns), Turn 1 — the first-round…, Turn 2 — the… and Reviewer pushback patterns…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the first-round reviewer discussion
What it does
Vis Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting IEEE VIS author responses across the two-phase review, covering the first-round reviewer discussion, and — distinctively — the conditional-accept second-round revision with its summary-of-changes that maps every required change to a concrete edit and is re-read by the same primary, secondary, and external reviewers under the IEEE TVCG process.
Its SKILL.md is about 1.4k 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
- Drafting IEEE VIS author responses across the two-phase review
- Covering the first-round reviewer discussion
- External reviewers under the IEEE TVCG process
Example prompts
- “/vis-author-response”
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 Author Response loads about 1.4k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 557 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). 557 words, ~1,376 tokens.
Download SKILL.mdSave it as
.claude/skills/vis-author-response/SKILL.md (or your agent's skills folder).- name
- vis-author-response
- description
- Use when drafting IEEE VIS author responses across the two-phase review, covering the first-round reviewer discussion, and — distinctively — the conditional-accept second-round revision with its summary-of-changes that maps every required change to a concrete edit and is re-read by the same primary, secondary, and external reviewers under the IEEE TVCG process.
VIS Author Response
Use this after IEEE VIS reviews are released. VIS has two distinct speaking turns, and conflating them is a common mistake: a first-round engagement with the reviewer discussion, and — if you receive a conditional accept — a full second-round revision with a summary of changes accompanying a revised paper that the original reviewers re-read against the required changes. This is a journal-style revise-and-review, not a one-shot CVPR rebuttal.
Triage (both turns)
- Answer what affects the decision: novelty, impact, whether the evidence supports the claims, methodology, encoding/interaction rationale, and reproducibility.
- Use evidence that already exists or that the revision will concretely add — never a vague promise to "consider" a study.
- Correct factual misreadings first; a reviewer who misread a figure or a task is often persuadable.
- If you submitted double-blind, keep every word anonymous through the first round — do not name your system, lab, grant, or a public repository even to strengthen a point.
Turn 1 — the first-round engagement
VIS's first phase includes a reviewer discussion. Your first-round comments (where the cycle allows author input before the decision) should be short and decision-focused: concede what is true, correct what is misread, and point to exactly where the answer already lives in the paper or the supplemental video/code. Do not smuggle in new results the reviewers cannot verify. The goal is to move the paper from "reject" toward "conditional accept" by removing correctable misunderstandings.
Turn 2 — the conditional-accept revision (the distinctive VIS move)
A conditional accept comes with a list of required changes. The revision is judged on whether you met them. The summary of changes is a change ledger: for every required change, either make it and show where, or justify declining it with a reason.
[R1.1] Required change (quoted briefly)
-> Action: DONE | added the within-subjects study (§6.2), Fig. 7, effect sizes + CIs
-> Where: §6.2, Fig. 7; supplemental/analysis/study2.ipynb
[R2.1] Required change
-> Action: DONE | rewrote the encoding-rationale (§4.1) to tie each channel to a task
-> Where: §4.1, Table 2
[R1.2] Required change
-> Action: JUSTIFIED DECLINE | the requested 3D condition contradicts the task's
occlusion constraint; added a scoping sentence + threat instead (§8)
[R3.1] Required change
-> Action: PARTIAL | added the perceptual pilot; the full longitudinal deployment is
out of scope for the revision window and is noted as future work (§9)The rule that turns a conditional accept into an acceptance: no silent omissions. A required change that is neither made nor explicitly justified as declined is what the second read punishes.
Show full SKILL.md (239 more words)Show less
Reviewer pushback patterns (visualization-specific)
| Pushback | What it signals | VIS-ready response |
|---|---|---|
| "Why this encoding rather than a standard chart?" | Design-rationale gap | Add a task-to-channel justification; compare against the conventional baseline |
| "The evaluation does not match the contribution" | Method mismatch | Add the evidence the contribution type needs (study for a claim about people; benchmark for a technique) |
| "Is this better than [existing tool/technique]?" | Novelty/delta doubt | Add the comparison or a scoped delta sentence naming what is new |
| "The user study is underpowered / confounded" | Conclusion-validity objection | Report power/effect sizes; add participants or bound the claim |
| "The system/results are not reproducible" | Open-practices gap | Release anonymized code/data; describe the reproduction path and target the Replicability Stamp |
| "Color/perception choices are not accessible" | Perceptual-validity concern | Justify the palette (CVD-safe, luminance); cite the perceptual basis |
Anonymity in the response (when submitted double-blind)
- Refer to your own prior work in the third person, as in the paper.
- Describe system/artifact changes without linking to an identity-revealing repository or demo; use the anonymized location until the paper is accepted.
- Do not thank a named collaborator or funder inside a first-round response.
Calibration
- Respond to the criterion the reviewer actually raised, not the one you would rather defend.
- The revised paper — not the summary of changes — carries the argument; the summary is a map from required change to edit.
- Length and format norms for both turns vary by cycle; confirm the current instructions and the second-round timeline before writing.
Output format
[Turn] first-round engagement / conditional-accept revision
[Priority issue] <reviewer concern>
[Decision dimension] novelty / impact / evidence / methodology / encoding rationale / reproducibility
[Change ledger] <required change -> DONE/PARTIAL/JUSTIFIED-DECLINE + where in paper/supplemental>
[Anonymity check] <if double-blind: no identity leak in the response: passed/issues>© 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-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vis Author Response 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 Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Icsme Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Fast Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Icassp Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
Icsme Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an IEEE ICSME author response during the double-anonymous author-response period, covering the early-decision cut that decides whether you respond at all…
Fast Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change…
Icassp Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already…
Ase Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting ASE (IEEE/ACM Automated Software Engineering) author responses, covering the double-anonymous rebuttal that must first survive the early-rejection gate and —…
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 Author Response
What does Vis Author Response do?
A skill your agent uses when drafting IEEE VIS author responses across the two-phase review, covering the first-round reviewer discussion, and — distinctively — the conditional-accept second-round…. Vis Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting IEEE VIS author responses across the two-phase review, covering the first-round reviewer discussion, and — distinctively — the conditional-accept second-round revision with its summary-of-changes that maps every required change to a concrete edit and is re-read by the same primary, secondary, and external reviewers under the IEEE TVCG process.
When should I use Vis Author Response?
Vis Author Response fits situations like: drafting IEEE VIS author responses across the two-phase review; covering the first-round reviewer discussion; external reviewers under the IEEE TVCG process.
How do I install Vis Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-author-response -a claude-code`. Or copy the skill folder (VIS-Skills/skills/vis-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vis-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Vis Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-author-response -a codex`. Or copy the skill folder (VIS-Skills/skills/vis-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vis-author-response in your project. Codex loads it when a task matches its description.
Can I use Vis Author Response 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-author-response -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-author-response, .gemini/skills/vis-author-response, .github/skills/vis-author-response and .opencode/skills/vis-author-response in your project.
What does Vis Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Vis Author Response is instructions for the agent only.
Does Vis Author Response 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 Author Response 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 Author Response use?
Vis Author Response 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 Author Response use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 Author Response?
Skills that share tags, products or a category with Vis Author Response: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars), Icsme Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Fast Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vis Author Response?
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.