Manim Video Production
browser-use/video-use
Produces math and technical explainer videos with Manim Community Edition: concept animations, equation derivations, algorithm walkthroughs and data stories.
A skill your agent uses when reasoning about how an IEEE VIS full-paper submission is evaluated, covering the two-phase review that mirrors IEEE TVCG, the primary/secondary/external (and 2026…
MITAuto-check passed
Install Vis Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-review-process --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-review-process .claude/skills/vis-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-review-process into .claude/skills/vis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-review-process --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-review-process .agents/skills/vis-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-review-process into .agents/skills/vis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-review-process --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-review-process .cursor/skills/vis-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-review-process into .cursor/skills/vis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-review-process --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-review-process .gemini/skills/vis-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-review-process into .gemini/skills/vis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/vis-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-review-process into .github/skills/vis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/vis-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-review-process into .opencode/skills/vis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 838 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how an IEEE VIS full-paper submission is evaluated, covering the two-phase review that mirrors IEEE TVCG, the primary/secondary/external (and 2026…
- Reasoning about how an IEEE VIS full-paper submission is evaluated
- SKILL.md covers Process model, The two-phase structure (the…, Reading a first-round decision and How VIS differs from its…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the two-phase review that mirrors IEEE TVCG
What it does
Vis Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an IEEE VIS full-paper submission is evaluated, covering the two-phase review that mirrors IEEE TVCG, the primary/secondary/external (and 2026 student) reviewer roles, the six-area routing through Area Paper Chairs, the conditional-accept second round, and how VIS's journal-integrated process differs from a single accept/reject conference and from CHI/CVPR.
Its SKILL.md is about 1.9k 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
- Reasoning about how an IEEE VIS full-paper submission is evaluated
- Covering the two-phase review that mirrors IEEE TVCG
- The primary/secondary/external (and 2026 student) reviewer roles
- The six-area routing through Area Paper Chairs
Example prompts
- “/vis-review-process”
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 Review Process loads about 1.9k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 838 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). 838 words, ~1,893 tokens.
Download SKILL.mdSave it as
.claude/skills/vis-review-process/SKILL.md (or your agent's skills folder).- name
- vis-review-process
- description
- Use when reasoning about how an IEEE VIS full-paper submission is evaluated, covering the two-phase review that mirrors IEEE TVCG, the primary/secondary/external (and 2026 student) reviewer roles, the six-area routing through Area Paper Chairs, the conditional-accept second round, and how VIS's journal-integrated process differs from a single accept/reject conference and from CHI/CVPR.
VIS Review Process
Model the pipeline before interpreting any single review. IEEE VIS's process is journal-style because VIS full papers are IEEE TVCG articles, so a first-round outcome is rarely a plain accept or reject — the pivotal decision is a conditional accept that sends the paper into a real second round. The most consequential mental shift for authors arriving from a one-shot conference is that VIS gives repairable papers a genuine revise-and-review cycle within the same edition.
Process model
- Submission and review run on PCS under the VGTC society, with author-optional double-blind anonymity following the IEEE TVCG process.
- Each paper is routed by its primary area to one of the six areas and handled by that area's Area Paper Chairs; Overall Paper Chairs keep decisions consistent across areas.
- Each paper gets at least three reviewers: a primary and a secondary (both program committee members) plus at least one external expert. VIS 2026 adds an optional student reviewer the primary may invite — a fourth, developmental voice, not a replacement.
- Reviewers weigh scientific quality and novelty, potential impact, whether the evidence supports the claims, appropriateness of methodology, and the soundness of the research process. Approved reviews are published only if the authors opt in at camera-ready and every reviewer on the paper also consents — they then appear as supplemental material in an OSF repository, not in IEEE Xplore. One dissenting reviewer is enough to keep them unpublished, and the chairs have no mechanism to override that.
The two-phase structure (the defining VIS mechanic)
Phase 1: submission -> reviews -> reviewer discussion -> first-round decision
decisions: Accept | Conditional Accept (revise) | Reject
Phase 2 (only for Conditional Accept): revised paper + summary of changes ->
re-review by the SAME reviewers against the required changes ->
final Accept / RejectA conditional accept is not a soft accept — the second round is real, and only papers that actually make the required changes are accepted. Treat it like a journal major-revision with a hard window.
Reading a first-round decision
| Decision | What it means | Author move |
|---|---|---|
| Accept | Contribution and evidence hold; minor polish only | Camera-ready + open materials; do not reopen scope |
| Conditional Accept | Repairable gaps: a missing study, an unclear encoding rationale, a needed baseline or condition | Treat as a journal R&R: make or explicitly justify declining every required change, evidenced |
| Reject | Structural: wrong contribution shape, unconvincing evaluation, thin novelty | Reframe or reroute (a sibling venue or TVCG journal track), do not lightly resubmit unchanged |
The strategic reading: design the first submission so its weakest point is revisable in the second round (a study you can add, an ablation you can run, a design rationale you can articulate) rather than structural (an evaluation you cannot redo in the revision window). The process rewards papers whose gaps are fixable.
How VIS differs from its siblings
- vs. CHI: CHI is a mandatory-anonymous, ACM-proceedings HCI venue with its own rebuttal +
revise-and-resubmit; VIS publishes in the TVCG journal, routes by six visualization areas
through Area Paper Chairs, and makes double-blind optional. Never assume a shared template
(
acmartvs VGTC) or calendar. - vs. CVPR: CVPR is a single-decision, high-volume vision conference with a fixed rebuttal and no in-cycle revision round; VIS's conditional-accept second round and journal publication are the opposite model. A CVPR-style "one rebuttal, then final" mental model will mis-time your VIS revision effort.
- vs. pre-2021 VIS: VIS once ran three separate conferences (SciVis, InfoVis, VAST) with separate committees. Since 2021 there is one call, one review process, and the six-area model. Do not carry a track-specific assumption from an older edition.
Show full SKILL.md (291 more words)Show less
Who reads you
Expect a primary, a secondary, and an external reviewer matched to your area, possibly plus a student reviewer. Visualization reviewers check whether the visual encoding and interaction are justified by task, whether the evaluation matches the contribution type (a technique needs different evidence than a design study or a perceptual experiment), and often open the supplemental video and code. Vague design rationale or an evaluation mismatched to the claim gets caught, not skimmed.
Where author leverage actually exists
[Before submission] primary-area + keyword choice -> Area Chair + reviewer pool (largest lever)
[First-round reviews] factual corrections, clarifying misreadings, pointing to evidence already present
[Conditional accept] the strongest lever: a revised paper + summary-of-changes re-read by the
same reviewers against the required changes
[After reject] no appeal; reroute to a sibling venue or the TVCG journal trackA response moves borderline papers when it corrects a misreading or supplies a study/analysis a reviewer said was missing; it does not move papers by arguing taste. In the second round, a required change that is neither made nor explicitly justified as declined is what turns a conditional accept into a rejection.
Reading a review packet
Weight reviews before answering. A review from the primary carries the most process weight and frames the discussion; the external often supplies the deepest domain check. A review that cites your figure and section numbers was read closely and will be re-read in the second round — its author is your likely advocate if the revision delivers. Answer each reviewer on the axis they raised (encoding rationale, evaluation, novelty, reproducibility), and treat the list of required changes as the scored contract for phase two.
Misreadings to avoid
- Treating a conditional accept as a guaranteed accept — the second read is real; budget the revision window like a deadline.
- Treating the response as a debate — the reviewer discussion decides; your revised paper, not your prose, carries the argument.
- Assuming a CVPR-style single rebuttal — VIS's revision round is a full re-review, not a one-shot reply.
- Projecting a pre-unification track model — one area-routed process, not three conferences.
Output format
[Process stage] pre-submission / awaiting reviews / conditional accept / second round / accepted
[Decision category] accept / conditional accept / reject, with the criterion driving it
[Area routing] primary area + Area Chair; reviewer roles (primary/secondary/external/student)
[Criterion map] each review point -> novelty | impact | evidence | methodology | encoding rationale | reproducibility
[Leverage plan] the next-stage action that can actually change the outcome
[Forbidden moves] identity leak (if double-blind) / unsupported new claims© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vis Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Manim Video Productionbrowser-use/video-use | 29k | 6 repos | ~3k | Automated safety check: Pass | MIT | |
| Logseq Review Workflow Evallogseq/logseq | 45k | — | ~1k | Automated safety check: Pass | AGPL-3.0 | |
| Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill | 2.5k | 2 repos | ~3.2k | Automated safety check: Pass | None | |
| DeepTutor CLIHKUDS/DeepTutor | 41k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Obsidian CLIAtmosphere/atmosphere | 3.8k | 13 repos | ~795 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Logseq Review Workflow Eval
logseq/logseq
Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…
Baoyu URL To Markdown
sdyckjq-lab/llm-wiki-skill
Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.
DeepTutor CLI
HKUDS/DeepTutor
Teaches the agent to set up and run DeepTutor from the command line: chat and capabilities, knowledge bases, partners, memory, sessions, notebooks and the server or Web app.
Obsidian CLI
Atmosphere/atmosphere
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.
AI Engineering Placement Quiz
rohitg00/ai-engineering-from-scratch
Runs a 10-question quiz across five areas to place a learner in the AI Engineering from Scratch curriculum, so they skip what they already know.
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 Review Process
What does Vis Review Process do?
A skill your agent uses when reasoning about how an IEEE VIS full-paper submission is evaluated, covering the two-phase review that mirrors IEEE TVCG, the primary/secondary/external (and 2026…. Vis Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an IEEE VIS full-paper submission is evaluated, covering the two-phase review that mirrors IEEE TVCG, the primary/secondary/external (and 2026 student) reviewer roles, the six-area routing through Area Paper Chairs, the conditional-accept second round, and how VIS's journal-integrated process differs from a single accept/reject conference and from CHI/CVPR.
When should I use Vis Review Process?
Vis Review Process fits situations like: reasoning about how an IEEE VIS full-paper submission is evaluated; covering the two-phase review that mirrors IEEE TVCG; the primary/secondary/external (and 2026 student) reviewer roles; the six-area routing through Area Paper Chairs.
How do I install Vis Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-review-process -a claude-code`. Or copy the skill folder (VIS-Skills/skills/vis-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vis-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Vis Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-review-process -a codex`. Or copy the skill folder (VIS-Skills/skills/vis-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vis-review-process in your project. Codex loads it when a task matches its description.
Can I use Vis Review Process 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-review-process -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-review-process, .gemini/skills/vis-review-process, .github/skills/vis-review-process and .opencode/skills/vis-review-process in your project.
What does Vis Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Vis Review Process is instructions for the agent only.
Does Vis Review Process 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 Review Process 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 Review Process use?
Vis Review Process 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 Review Process use?
About 1.9k tokens (SKILL.md is roughly 7.6k 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 Review Process?
Skills that share tags, products or a category with Vis Review Process: Manim Video Production (browser-use/video-use, 29k stars), Logseq Review Workflow Eval (logseq/logseq, 45k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars) and DeepTutor CLI (HKUDS/DeepTutor, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vis Review Process?
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.