Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Agent skill
Vis Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an IEEE VIS artifact for the Graphics Replicability Stamp Initiative (GRSI) / TVCG Replicability Stamp and the IEEE VIS Open Practices program, covering what…
Install Vis Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-artifact-evaluation --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-artifact-evaluation .claude/skills/vis-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-artifact-evaluation into .claude/skills/vis-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-artifact-evaluation", 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-artifact-evaluationType 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-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-artifact-evaluation --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-artifact-evaluation .agents/skills/vis-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-artifact-evaluation into .agents/skills/vis-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-artifact-evaluation", 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-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-artifact-evaluation --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-artifact-evaluation .cursor/skills/vis-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-artifact-evaluation into .cursor/skills/vis-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-artifact-evaluation", 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-artifact-evaluation--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-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-artifact-evaluation --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-artifact-evaluation .gemini/skills/vis-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-artifact-evaluation into .gemini/skills/vis-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-artifact-evaluation", 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-artifact-evaluationInstalls 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-artifact-evaluation -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-artifact-evaluation .github/skills/vis-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-artifact-evaluation into .github/skills/vis-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-artifact-evaluation", 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-artifact-evaluation -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-artifact-evaluation --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-artifact-evaluation .opencode/skills/vis-artifact-evaluation && 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-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-artifact-evaluation into .opencode/skills/vis-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-artifact-evaluation", 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-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 509 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when packaging an IEEE VIS artifact for the Graphics Replicability Stamp Initiative (GRSI) / TVCG Replicability Stamp and the IEEE VIS Open Practices program, covering what…
- Covering what an independent GRSI volunteer reproduces first
- SKILL.md covers What GRSI certifies (verify…, What a GRSI volunteer opens…, Packaging plan and Anonymized review artifact vs.…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- DOI-issuing archives
What it does
Vis Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging an IEEE VIS artifact for the Graphics Replicability Stamp Initiative (GRSI) / TVCG Replicability Stamp and the IEEE VIS Open Practices program, covering what an independent GRSI volunteer reproduces first, DOI-issuing archives, evaluator-proof documentation for visualization code and data, and how VIS reproducibility differs from ACM-style artifact badges.
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.
It sits in Research & Science, covering Reproducible research. 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
- Covering what an independent GRSI volunteer reproduces first
- DOI-issuing archives
- Evaluator-proof documentation for visualization code and data
- How VIS reproducibility differs from ACM-style artifact badges
Example prompts
- “/vis-artifact-evaluation”
Requirements
- Docker
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 Artifact Evaluation loads about 1.3k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 509 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). 509 words, ~1,330 tokens.
Download SKILL.mdSave it as
.claude/skills/vis-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- vis-artifact-evaluation
- description
- Use when packaging an IEEE VIS artifact for the Graphics Replicability Stamp Initiative (GRSI) / TVCG Replicability Stamp and the IEEE VIS Open Practices program, covering what an independent GRSI volunteer reproduces first, DOI-issuing archives, evaluator-proof documentation for visualization code and data, and how VIS reproducibility differs from ACM-style artifact badges.
VIS Artifact Evaluation
Use this for the reproducibility track. IEEE VIS does not use ACM-style artifact badges; its recognition is the Graphics Replicability Stamp Initiative (GRSI) — issued to TVCG papers as the TVCG Replicability Stamp — plus the conference's Open Practices program. Two things to internalize: the stamp is earned by an independent volunteer actually reproducing your results from a public archive, and the review artifact (anonymized, for your paper's reviewers) is not the same deliverable as the stamp artifact (de-anonymized, permanently archived).
What GRSI certifies (verify the current process)
| Mechanism | What it certifies | What earns it |
|---|---|---|
| TVCG Replicability Stamp (GRSI) | An independent volunteer reproduced the paper's results from your code/data | A public repository + a single documented build/run path that regenerates the key figures/results |
| Open Practices disclosures | Transparent reporting of open code, data, preprints, preregistration | Filling the camera-ready Open Practices form honestly and posting the materials |
Unlike a graded badge ladder, the stamp is binary: an evaluator either reproduces your results or does not. The failure mode is therefore always "it did not build/run on their machine," never "the idea was weak" — design for a stranger's clean environment.
What a GRSI volunteer opens first
| Claim type | First thing reproduced | Common failure caught |
|---|---|---|
| A visualization technique/algorithm | The build + a script that regenerates a key figure | Undocumented deps; only-builds-on-authors'-GPU |
| A system/tool | The install and a demo on bundled sample data | Requires a private server, API key, or paid license |
| A perceptual/empirical study | The analysis scripts that turn raw responses into the paper's stats | Numbers in the PDF no script reproduces; raw data missing |
| A rendering result | The pipeline + reference images with a comparison | Non-deterministic output with no tolerance/seed documented |
Assume the evaluator gives your package a bounded time budget on a clean machine. The first build and the first regenerated figure must succeed.
Packaging plan
[Container] ship a Dockerfile or a pinned environment (requirements/lockfile, exact toolchain
versions); avoid "install these 40 things by hand" and undocumented GPU/driver needs
[README] one-screen orientation: what it is, how to build, how to run the demo, how to
regenerate each figure/result, expected runtime and outputs
[Mapping] an explicit table: paper figure/result -> script -> expected output
[Data] the actual dataset or stimuli (or documented access), not just a pointer
[Determinism] seeds, tolerances, and reference images for anything stochastic or GPU-dependent
[License] an OSI-approved license so others can reuse the visualization code
[Archive] deposit in a DOI-issuing repository (OSF, Zenodo, Software Heritage) for permanenceShow full SKILL.md (207 more words)Show less
Anonymized review artifact vs. stamp artifact
- At submission (if double-blind): the supplemental code/data/video is anonymized for the paper's reviewers — no owner strings, lab names, institutional URLs, or identity-revealing demo links, and no live repository that discloses authors.
- After acceptance: replace anonymized placeholders with the public, licensed, DOI-issuing archive; this is the version a GRSI volunteer reproduces and the camera-ready cites.
Worked vignette: stamping a technique + system paper
A paper contributes a new graph-layout technique and an interactive system. To target the stamp:
ship a Docker image with the layout code pre-built; a run_demo.sh that lays out a small bundled
graph and writes the teaser figure in under a minute; a reproduce/ directory whose scripts
regenerate each quantitative figure from logged benchmark data; a figure-to-script mapping in the
README; the benchmark graphs themselves with provenance; and an MIT/BSD license. State honestly
which figures are turnkey and which need the full (slow) benchmark run.
Calibration
- The GRSI review is independent of and after camera-ready; do not conflate them, and do not block the paper on the stamp result.
- The exact GRSI submission process, the Open Practices requirements, and whether any element is mandatory vary by cycle — confirm on the current Open Practices page and the GRSI site.
Output format
[Target recognition] TVCG Replicability Stamp / Open Practices disclosures
[Artifact role] anonymized review artifact / public stamp artifact
[Contents] <code/data/stimuli/determinism aids/license>
[Clean-machine test] does build + demo + one regenerated figure succeed? yes/no
[Figure mapping] <figure/result -> script -> expected output present? yes/no>
[Fixes before archiving] <ordered list>© 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-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vis Artifact Evaluation 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 Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw | 617 | 1 repos | ~1.8k | Automated safety check: Pass | None | |
| Compute Environment Setupaipoch/open-science | 5.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Figure Styleaipoch/open-science | 5.5k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Bactopia Toolbactopia/bactopia | 522 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
Compute Environment Setup
aipoch/open-science
Prepares setup instructions and a named activation file for a user-managed software environment on an Open-Science SSH or Slurm compute host.
Figure Style
aipoch/open-science
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots.
Add Bactopia Tool
bactopia/bactopia
Scaffold a complete Bactopia Tool across all three tiers -- module, subworkflow, and workflow entry point under workflows/bactopia-tools/.
Modeling Code and Result Contracts
yushui2022/MathModel-Skill
Generates result-evidence contracts, tables and runnable q1 to q3 modeling code scaffolds for a math modeling paper from a model route, a data plan and cleaned data.
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 Artifact Evaluation
What does Vis Artifact Evaluation do?
A skill your agent uses when packaging an IEEE VIS artifact for the Graphics Replicability Stamp Initiative (GRSI) / TVCG Replicability Stamp and the IEEE VIS Open Practices program, covering what…. Vis Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging an IEEE VIS artifact for the Graphics Replicability Stamp Initiative (GRSI) / TVCG Replicability Stamp and the IEEE VIS Open Practices program, covering what an independent GRSI volunteer reproduces first, DOI-issuing archives, evaluator-proof documentation for visualization code and data, and how VIS reproducibility differs from ACM-style artifact badges.
When should I use Vis Artifact Evaluation?
Vis Artifact Evaluation fits situations like: covering what an independent GRSI volunteer reproduces first; DOI-issuing archives; evaluator-proof documentation for visualization code and data; how VIS reproducibility differs from ACM-style artifact badges.
How do I install Vis Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-artifact-evaluation -a claude-code`. Or copy the skill folder (VIS-Skills/skills/vis-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vis-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Vis Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-artifact-evaluation -a codex`. Or copy the skill folder (VIS-Skills/skills/vis-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vis-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Vis Artifact Evaluation 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-artifact-evaluation -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-artifact-evaluation, .gemini/skills/vis-artifact-evaluation, .github/skills/vis-artifact-evaluation and .opencode/skills/vis-artifact-evaluation in your project.
What does Vis Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Vis Artifact Evaluation is instructions for the agent only. Our summary lists: Docker.
Does Vis Artifact Evaluation 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 Artifact Evaluation 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 Artifact Evaluation use?
Vis Artifact Evaluation 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 Artifact Evaluation use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Artifact Evaluation?
Skills that share tags, products or a category with Vis Artifact Evaluation: Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Compute Environment Setup (aipoch/open-science, 5.5k stars) and Figure Style (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vis Artifact Evaluation?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.