Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
A skill your agent uses when splitting a UAI paper between the 8-page main part, the unlimited in-PDF appendix for proofs and protocols, and the optional 50 MB supplementary ZIP, deciding what…
Install Uai Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-supplementary --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/UAI-Skills/skills/uai-supplementary .claude/skills/uai-supplementary && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "uai-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-supplementary into .claude/skills/uai-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-supplementary", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-supplementaryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-supplementary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/UAI-Skills/skills/uai-supplementary .agents/skills/uai-supplementary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "uai-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-supplementary into .agents/skills/uai-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-supplementary", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-supplementary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/UAI-Skills/skills/uai-supplementary .cursor/skills/uai-supplementary && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "uai-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-supplementary into .cursor/skills/uai-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-supplementary", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path UAI-Skills/skills/uai-supplementary--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-supplementary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/UAI-Skills/skills/uai-supplementary .gemini/skills/uai-supplementary && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "uai-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-supplementary into .gemini/skills/uai-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-supplementary", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-supplementaryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-supplementary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/UAI-Skills/skills/uai-supplementary .github/skills/uai-supplementary && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "uai-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-supplementary into .github/skills/uai-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-supplementary", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-supplementary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-supplementary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/UAI-Skills/skills/uai-supplementary .opencode/skills/uai-supplementary && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "uai-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-supplementary into .opencode/skills/uai-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-supplementary", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
uai-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 764 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when splitting a UAI paper between the 8-page main part, the unlimited in-PDF appendix for proofs and protocols, and the optional 50 MB supplementary ZIP, deciding what…
- Splitting a UAI paper between the 8-page main part
- SKILL.md covers The three tiers, Placement heuristics, Appendix architecture that… and ZIP assembly under the 50 MB cap, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The unlimited in-PDF appendix for proofs and protocols
What it does
Uai Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when splitting a UAI paper between the 8-page main part, the unlimited in-PDF appendix for proofs and protocols, and the optional 50 MB supplementary ZIP, deciding what reviewers must see in the body versus what may sit in material they are not required to read, all under double-blind and single-file constraints.
Its SKILL.md is about 1.6k 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, covering PDF. 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
- Splitting a UAI paper between the 8-page main part
- The unlimited in-PDF appendix for proofs and protocols
- The optional 50 MB supplementary ZIP
- Deciding what reviewers must see in the body versus what may sit in material they are not required to read
Example prompts
- “/uai-supplementary”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are latex).
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
Uai Supplementary loads about 1.6k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 764 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). 764 words, ~1,630 tokens.
Download SKILL.mdSave it as
.claude/skills/uai-supplementary/SKILL.md (or your agent's skills folder).- name
- uai-supplementary
- description
- Use when splitting a UAI paper between the 8-page main part, the unlimited in-PDF appendix for proofs and protocols, and the optional 50 MB supplementary ZIP, deciding what reviewers must see in the body versus what may sit in material they are not required to read, all under double-blind and single-file constraints.
UAI Supplementary
UAI's packaging model (2026 cycle, verified 2026-07-08) has three tiers with sharply different review status. Getting content into the right tier is a strategic decision, not a formatting chore. Reconfirm tier rules in the current submission instructions before finalizing.
The three tiers
| Tier | 2026 constraint | Review status | Belongs here |
|---|---|---|---|
| Main part | ≤ 8 pages, UAI template | Read by everyone, judged on all four criteria | Claims, assumptions, method, key evidence, limitations |
| Appendix | Unlimited, same PDF, after references | Part of the reviewed submission; consulted when reviewers verify | Full proofs, protocols, extra experiments, derivations |
| Supplementary ZIP | ≤ 50 MB, separate upload | Explicitly optional for reviewers | Code, data, generators, logs, checkpoints |
Two structural consequences follow. First, because the appendix travels inside the reviewed PDF, UAI has no "the reviewers never saw my proofs" excuse — but also no mercy for identity leaks buried on appendix page 30. Second, because the ZIP is officially optional reading, nothing decision-critical may live only there.
Placement heuristics
- A result whose absence would change the accept/reject argument goes in the main part, even as a two-line proof sketch pointing to the appendix.
- A step a skeptical reviewer must verify to trust a theorem goes in the appendix — in full, with the theorem restated so the appendix reads without page-flipping.
- Anything executable goes in the ZIP, plus a pointer sentence in the paper so its existence is on the reviewed record.
- Never cite the ZIP as evidence for a claim ("see supplementary code for the full results"): reviewers are entitled to ignore it, so the claim becomes unbacked.
Appendix architecture that works here
Statisticians and probabilistic-ML researchers navigate by statement numbers. Structure for that reading style:
- One appendix section per theorem or per experiment family, in main-text order.
- Restate every assumption with its original label (A1, A2…) before using it; an appendix proof invoking an unlabeled assumption is where correctness objections start.
- Give experimental appendices the same table discipline as the body: full hyperparameter grids, per-dataset results, per-seed dispersion.
- Cross-reference forward from the body precisely ("proof in App. B.2", not "proofs in the appendix").
% Single-PDF assembly, UAI style: appendix follows references in the same document
\bibliography{refs} % references end the main part
\clearpage
\appendix
\section{Proofs for Section 3}\label{app:proofs}
\paragraph{Assumption A2 (restated).} The mixing weights are bounded away from zero.
\begin{proof}[Proof of Theorem 3]
... % full argument; the body kept only the sketch
\end{proof}
\section{Experimental Protocols}\label{app:protocols}
% grids, seeds, per-dataset tables, computeZIP assembly under the 50 MB cap
- Ship generators and configs rather than bulky outputs; include checksums for anything regenerable.
- Structure by claim, not by code module: a reviewer looks for
figure2/, not forsrc/utils/. - Keep the archive as anonymous as the PDF: no
.githistory, no notebook author metadata, no cluster paths, no account-bound experiment-tracker URLs. - Test the unzip-and-run path on a clean machine; a broken optional artifact is worse than no artifact, because it documents carelessness.
Show full SKILL.md (343 more words)Show less
Pre-merge integrity checklist
Run after the last content edit, before assembling the final PDF:
- Every theorem/lemma/proposition statement in the body is character-identical to its restatement in the appendix (diff them mechanically, not by eye).
- Every assumption label used in an appendix proof is defined in the body.
- Every "App. X.Y" reference in the body resolves to an existing section after the latest appendix reshuffle.
- Appendix figures and tables are numbered in a scheme that cannot collide with the body's (e.g., Table 7 vs Table A.3 — pick one convention).
- No appendix section silently introduces a claim absent from the body; reviewers may treat body-less claims as unreviewable.
- The references section sits between main part and appendix per the current template's convention.
- Page count of the main part re-verified after the merge; late appendix edits sometimes push floats forward into page 8.
- The ZIP's README points into the appendix ("protocol details in App. C") and not vice versa for anything decision-critical.
Budgeting the 50 MB
A workable allocation when the archive is tight: code and configs are effectively free (rarely over 5 MB); reserve the bulk for whichever single item most de-risks your weakest claim — a gold-standard posterior sample set, a preprocessed data extract with checksums, or trained-model files for the headline table. Everything else ships as a generator script plus a hash of its output. If two heavyweight items compete, keep the one a reviewer cannot regenerate in minutes.
Failure patterns seen at single-PDF venues
- Overflow laundering: pushing the method description itself into the appendix to make the 8-page cap. Reviewers score clarity on the main part; an unintelligible body with a beautiful appendix fails.
- Appendix drift: editing a theorem in the body during deadline week without touching its appendix proof. Diff statement text mechanically before upload.
- Reference squeeze: trimming citations to save space, forgetting references are outside the 8-page cap and cost nothing.
- ZIP-only ablations: the reviewer asks "why no ablation?" and the answer "it was in the ZIP" wins no points, because the rules told them they could skip it.
Output format
[Tier map] main <pages> / appendix <pages> / ZIP <MB>
[Misplaced content] <items in the wrong tier, with target tier>
[Appendix integrity] statements match body? assumptions labeled?
[ZIP status] runs clean? anonymous? claim-indexed?
[Pointer sentences] <paper locations announcing appendix and ZIP contents>© 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 UAI-Skills/skills/uai-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Uai Supplementary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Uai Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Gzh Designisjiamu/gzh-design-skill | 4k | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| GenOffice Document CLIgenspark-ai/genoffice | 9.2k | — | ~19k | Automated safety check: Pass | Apache-2.0 | |
| Harness Book Best Practicewquguru/harness-books | 3.2k | — | ~4.1k | Automated safety check: Pass | None | |
| Bookforge Korean Ebook PDF Makergongnyang/bookforge | 316 | 1 repos | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
GenOffice Document CLI
genspark-ai/genoffice
Creates, converts, reads and edits real pptx, xlsx, docx and PDF files locally through the genoffice command line.
Harness Book Best Practice
wquguru/harness-books
Best practices for working on the Harness books repo. An agent skill from wquguru/harness-books.
Bookforge Korean Ebook PDF Maker
gongnyang/bookforge
Produces book-style Korean ebook PDFs from a topic or finished manuscript, with six design styles, real book parts and quality-check gates before output.
- Official
Instrument Data To Allotrope
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
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 Uai Supplementary
What does Uai Supplementary do?
A skill your agent uses when splitting a UAI paper between the 8-page main part, the unlimited in-PDF appendix for proofs and protocols, and the optional 50 MB supplementary ZIP, deciding what…. Uai Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when splitting a UAI paper between the 8-page main part, the unlimited in-PDF appendix for proofs and protocols, and the optional 50 MB supplementary ZIP, deciding what reviewers must see in the body versus what may sit in material they are not required to read, all under double-blind and single-file constraints.
When should I use Uai Supplementary?
Uai Supplementary fits situations like: splitting a UAI paper between the 8-page main part; the unlimited in-PDF appendix for proofs and protocols; the optional 50 MB supplementary ZIP; deciding what reviewers must see in the body versus what may sit in material they are not required to read.
How do I install Uai Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-supplementary -a claude-code`. Or copy the skill folder (UAI-Skills/skills/uai-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uai-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Uai Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-supplementary -a codex`. Or copy the skill folder (UAI-Skills/skills/uai-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uai-supplementary in your project. Codex loads it when a task matches its description.
Can I use Uai Supplementary in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-supplementary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/uai-supplementary, .gemini/skills/uai-supplementary, .github/skills/uai-supplementary and .opencode/skills/uai-supplementary in your project.
What does Uai Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Uai Supplementary is instructions for the agent only.
Does Uai Supplementary access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Uai Supplementary safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Uai Supplementary use?
Uai Supplementary is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Uai Supplementary use?
About 1.6k tokens (SKILL.md is roughly 6.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 Uai Supplementary?
Skills that share tags, products or a category with Uai Supplementary: Markitdown (ImCa0/just-laws, 781 stars), Gzh Design (isjiamu/gzh-design-skill, 4k stars), GenOffice Document CLI (genspark-ai/genoffice, 9.2k stars) and Harness Book Best Practice (wquguru/harness-books, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Uai Supplementary?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.