Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
A skill your agent uses when auditing an IEEE VIS full-paper submission for PCS readiness, covering the abstract-then-paper two-deadline structure under the VGTC society, the IEEE VGTC/TVCG 9+2 page…
Install Vis Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-submission --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-submission .claude/skills/vis-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-submission into .claude/skills/vis-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-submission --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-submission .agents/skills/vis-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-submission into .agents/skills/vis-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-submission --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-submission .cursor/skills/vis-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-submission into .cursor/skills/vis-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-submission --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-submission .gemini/skills/vis-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-submission into .gemini/skills/vis-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/vis-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-submission into .github/skills/vis-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-submission", 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-submission -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-submission --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-submission .opencode/skills/vis-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-submission into .opencode/skills/vis-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 822 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an IEEE VIS full-paper submission for PCS readiness, covering the abstract-then-paper two-deadline structure under the VGTC society, the IEEE VGTC/TVCG 9+2 page…
- Works in 6 steps: Freeze the paper's argument early; the… → Submit the abstract with final authors,… → Build and anonymize the supplemental… → …
- Auditing an IEEE VIS full-paper submission for PCS readiness
- SKILL.md covers The two-deadline structure…, PCS mechanics, Format and page budget and Author-optional double-blind…, plus 5 more sections
- Calls pdftotext
What it does
Vis Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an IEEE VIS full-paper submission for PCS readiness, covering the abstract-then-paper two-deadline structure under the VGTC society, the IEEE VGTC/TVCG 9+2 page budget, author-optional double-blind anonymization, the supplemental-material one-week window, and desk-reject triage before the AoE cutoff for a paper that will publish in IEEE TVCG.
Its SKILL.md is about 1.7k 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 Documents & Office. 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
- Auditing an IEEE VIS full-paper submission for PCS readiness
- Covering the abstract-then-paper two-deadline structure under the VGTC society
- The IEEE VGTC/TVCG 9+2 page budget
- Author-optional double-blind anonymization
Example prompts
- “/vis-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Freeze the paper's argument early; the abstract you register must match the final paper.
- Submit the abstract with final authors, primary area, and keywords before the abstract cutoff.
- Build and anonymize the supplemental package (video, code, data) for its own later deadline.
- Run the mechanical anonymity checks on the final PDF and final supplemental archive.
- Confirm PCS society/conference/track selection and every conflict a day early.
- Re-download the uploaded PDF and view it cold to confirm it is the file you meant.
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
Shell commands in SKILL.md call:
pdftotext
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 Submission loads about 1.7k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 822 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). 822 words, ~1,735 tokens.
Download SKILL.mdSave it as
.claude/skills/vis-submission/SKILL.md (or your agent's skills folder).- name
- vis-submission
- description
- Use when auditing an IEEE VIS full-paper submission for PCS readiness, covering the abstract-then-paper two-deadline structure under the VGTC society, the IEEE VGTC/TVCG 9+2 page budget, author-optional double-blind anonymization, the supplemental-material one-week window, and desk-reject triage before the AoE cutoff for a paper that will publish in IEEE TVCG.
VIS Submission
Run this audit before uploading to the Precision Conference System (PCS). IEEE VIS full papers
are published as journal articles in IEEE TVCG, so the submission is judged at a journal bar
even though it also earns a conference slot. Every number below was read from the IEEE VIS 2026
Call for Full Papers and Paper Submission Guidelines on 2026-07-09 via search renderings of the
ieeevis.org URLs (see resources/official-source-map.md); treat them as a one-cycle snapshot and
reopen the live call first.
The two-deadline structure (abstract, then paper)
VIS separates the abstract deadline from the full-paper deadline, and both are AoE:
- Abstract (VIS 2026: 21 March 2026) locks title, abstract, authors, and area/keyword choices. The author list must be final at this point — you cannot add authors after it. The abstract also drives area routing and reviewer bidding.
- Full paper (VIS 2026: 31 March 2026) uploads the PDF. After this, title, abstract, and the main PDF are frozen.
- Supplemental material (VIS 2026: 7 April 2026) has its own later window — a one-week extension introduced so authors can finish and properly anonymize videos, data, and code after the paper is in. Do not treat it as extra time for the paper itself.
Register the abstract with the real title and area, not a placeholder — misrouting to the wrong of the six areas puts your paper in front of the wrong Area Paper Chair and reviewer pool.
PCS mechanics
In PCS, at the top of the Submissions tab select society VGTC, conference VIS 2026, track VIS 2026 Full Papers. Getting the society/track wrong files your paper against a sibling VGTC venue (VR, ISMAR) or the wrong track. Fill conflicts, the primary area, and keywords carefully — they determine your reviewers.
Format and page budget
- IEEE VGTC / TVCG-conference template, unmodified. This is the VGTC document class (LaTeX
template at
github.com/ieee-vgtc/vis-latex-submission-template; a Typst port exists) — notacmart, and not a generic two-column IEEEtran habit carried from another IEEE venue. - Page budget (verify per cycle): up to 9 pages of content plus up to 2 pages that contain only references and acknowledgements — the "9+2" budget. Figures, tables, and text all count toward the 9; nothing decision-critical can hide in the reference pages.
- Margins, font, and columns are fixed by the template; recover space by editorial compression, not by shrinking the template.
Author-optional double-blind sweep
VIS runs author-optional double-blind review: anonymizing is not strictly required, but for most paper types it is good scientific practice and strongly recommended — and once you opt in, the anonymization must be clean. Because visualization papers lean on systems, demos, videos, and open-source releases, the leak surface is wide:
# Mechanical pass on the submission PDF and any supplemental archive
pdfinfo paper.pdf | grep -Ei 'author|creator|producer'
pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|osf\.io|youtu|acknowledg|grant|our (tool|system|lab)' | head
grep -rniE 'university|@[a-z0-9.]+\.edu|lab name|project url' supplemental/ | headThe VIS-specific leaks: a system named after your lab, a demo screenshot showing a username or an institutional URL, a supplemental video with a spoken affiliation or a visible desktop, a live GitHub/OSF link that discloses authorship, and a teaser figure watermarked with a project site. Re-host code, data, and video behind an anonymizing location before upload if you are submitting double-blind.
Show full SKILL.md (322 more words)Show less
Open practices at submission time
- If your contribution is a technique, system, study, or dataset, prepare the open materials now (anonymized for review): code, data, stimuli, analysis scripts, and a supplemental video.
- Preregistration, if your study used it, should be cited (anonymously) — it strengthens an empirical claim and is surfaced again in the Open Practices form at camera-ready.
- Cache anything you cannot regenerate (model outputs, crowd-study responses) before the deadline.
Desk-risk triage
| Finding at audit time | Severity | Real fix |
|---|---|---|
| Content over 9 pages | Desk-reject-grade | Cut or move to supplemental; the 2 reference pages do not absorb body text |
| Template altered (margins, shrunk font, wrong class) | Named desk-reject ground | Recompile with the clean VGTC template; recover space editorially |
| Author added after the abstract deadline | Not permitted | Nothing fixes this post-abstract; finalize authorship before 21 March-equivalent |
| Identity leak in a double-blind PDF, video, or repo link | Anonymity violation | Re-anonymize and re-host; scrub PDF and video metadata |
| Supplemental video unplayable / wrong codec | Reviewers cannot assess it | Re-encode to the required format before the supplemental deadline |
| Same work under review at another venue | Dual-submission exposure | Withdraw one; verify the current concurrent-submission wording |
Final-week order of operations
- Freeze the paper's argument early; the abstract you register must match the final paper.
- Submit the abstract with final authors, primary area, and keywords before the abstract cutoff.
- Build and anonymize the supplemental package (video, code, data) for its own later deadline.
- Run the mechanical anonymity checks on the final PDF and final supplemental archive.
- Confirm PCS society/conference/track selection and every conflict a day early.
- Re-download the uploaded PDF and view it cold to confirm it is the file you meant.
Reverify each cycle
- The abstract/paper/supplemental dates and the second-round timeline.
- The page budget and which VGTC/TVCG template revision is required.
- Whether double-blind is optional or mandatory this year, and the anonymization guidance.
- Dual-submission wording and any generative-AI disclosure rule — all cycle-volatile.
Output format
[VIS submission status] ready / blocked / needs work
[Abstract] title/authors/area/keywords locked by the abstract deadline? yes/no
[PCS] society VGTC / VIS 2026 / Full Papers track selected? conflicts complete?
[Format] pages used (content/refs), VGTC template compliance
[Anonymity] double-blind? clean / leaks: <where, incl. video/repo>
[Open materials] code/data/video prepared and anonymized? yes/no
[Fix queue] <ordered, with owners and dates before the AoE cutoff>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vis Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Markdown Article FormatterJimLiu/baoyu-skills | 27k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Word Document Reader and WriterHKUDS/DeepTutor | 41k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
Crossposting
wasp-lang/wasp
Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.
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 Submission
What does Vis Submission do?
A skill your agent uses when auditing an IEEE VIS full-paper submission for PCS readiness, covering the abstract-then-paper two-deadline structure under the VGTC society, the IEEE VGTC/TVCG 9+2 page…. Vis Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an IEEE VIS full-paper submission for PCS readiness, covering the abstract-then-paper two-deadline structure under the VGTC society, the IEEE VGTC/TVCG 9+2 page budget, author-optional double-blind anonymization, the supplemental-material one-week window, and desk-reject triage before the AoE cutoff for a paper that will publish in IEEE TVCG.
When should I use Vis Submission?
Vis Submission fits situations like: auditing an IEEE VIS full-paper submission for PCS readiness; covering the abstract-then-paper two-deadline structure under the VGTC society; the IEEE VGTC/TVCG 9+2 page budget; author-optional double-blind anonymization.
How do I install Vis Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-submission -a claude-code`. Or copy the skill folder (VIS-Skills/skills/vis-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vis-submission in your project. Claude Code loads it when a task matches its description.
How do I install Vis Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-submission -a codex`. Or copy the skill folder (VIS-Skills/skills/vis-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vis-submission in your project. Codex loads it when a task matches its description.
Can I use Vis Submission 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-submission -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-submission, .gemini/skills/vis-submission, .github/skills/vis-submission and .opencode/skills/vis-submission in your project.
What does Vis Submission need to run?
Going by SKILL.md and its folder, Vis Submission needs the command-line tools its instructions call (pdftotext).
Does Vis Submission 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 Submission 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 Submission use?
Vis Submission 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 Submission use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 Submission?
Skills that share tags, products or a category with Vis Submission: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vis Submission?
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.