Suiko
nwiizo/suiko
日本語文書のAI由来の均一さ、翻訳調、不自然さ、論旨、読解負荷を、決定的なRust CLIと目視で診断し、依頼に応じて書く・直す。日本語の学術論文・研究報告では、中心命題、用語、論証、DOCX/PDF納品を監査契約で確認する。Use when the user explicitly mentions suiko, asks whether Japanese text looks…
A skill your agent uses to write the PNAS Nexus Significance Statement — between 50 and 120 words, in plain language for a broad scientific audience, explaining why the work matters.
Install Pnasnexus Significance
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-significance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-significance --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/PNAS-Nexus-Skills/skills/pnasnexus-significance .claude/skills/pnasnexus-significance && 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 "pnasnexus-significance" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-significance into .claude/skills/pnasnexus-significance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-significance", 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/PNAS-Nexus-Skills/skills/pnasnexus-significanceType 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 pnasnexus-significance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-significance --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/PNAS-Nexus-Skills/skills/pnasnexus-significance .agents/skills/pnasnexus-significance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pnasnexus-significance" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-significance into .agents/skills/pnasnexus-significance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-significance", 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 pnasnexus-significance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-significance --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/PNAS-Nexus-Skills/skills/pnasnexus-significance .cursor/skills/pnasnexus-significance && 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 "pnasnexus-significance" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-significance into .cursor/skills/pnasnexus-significance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-significance", 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 PNAS-Nexus-Skills/skills/pnasnexus-significance--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 pnasnexus-significance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-significance --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/PNAS-Nexus-Skills/skills/pnasnexus-significance .gemini/skills/pnasnexus-significance && 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 "pnasnexus-significance" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-significance into .gemini/skills/pnasnexus-significance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-significance", 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 pnasnexus-significanceInstalls 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 pnasnexus-significance -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/PNAS-Nexus-Skills/skills/pnasnexus-significance .github/skills/pnasnexus-significance && 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 "pnasnexus-significance" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-significance into .github/skills/pnasnexus-significance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-significance", 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 pnasnexus-significance -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 pnasnexus-significance --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/PNAS-Nexus-Skills/skills/pnasnexus-significance .opencode/skills/pnasnexus-significance && 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 "pnasnexus-significance" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-significance into .opencode/skills/pnasnexus-significance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-significance", 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
pnasnexus-significance- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 679 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to write the PNAS Nexus Significance Statement — between 50 and 120 words, in plain language for a broad scientific audience, explaining why the work matters.
- Works in 4 steps: The problem / gap (1–2 sentences). What… → What this work shows (1–2 sentences).… → Why it matters (1–2 sentences). The… → …
- Write the PNAS Nexus Significance Statement — between 50 and 120 words
- SKILL.md covers Why this is a flagship PNAS…, When to trigger, The hard rule: 50–120 words,… and What it must do (and not do), plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pnasnexus Significance is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to write the PNAS Nexus Significance Statement — between 50 and 120 words, in plain language for a broad scientific audience, explaining why the work matters. Required for Research Reports and Stage 2 Registered Reports. Distinct from the abstract. One of the highest-value PNAS Nexus front-matter artifacts.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Plain language and style rules, Deep research and Markdown. 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
- Write the PNAS Nexus Significance Statement — between 50 and 120 words
- In plain language for a broad scientific audience
- Explaining why the work matters
Example prompts
- “/pnasnexus-significance”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- The problem / gap (1–2 sentences). What broad question or limitation does the field face? State the stakes plainly.
- What this work shows (1–2 sentences). The advance, in non-technical terms — the result, not the method.
- Why it matters (1–2 sentences). The consequence for the field, for other fields, or for society.
- (Optional) one sentence on a concrete broader application or future direction.
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
Pnasnexus Significance loads about 1.4k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 679 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). 679 words, ~1,383 tokens.
Download SKILL.mdSave it as
.claude/skills/pnasnexus-significance/SKILL.md (or your agent's skills folder).- name
- pnasnexus-significance
- description
- Use to write the PNAS Nexus Significance Statement — between 50 and 120 words, in plain language for a broad scientific audience, explaining why the work matters. Required for Research Reports and Stage 2 Registered Reports. Distinct from the abstract. One of the highest-value PNAS Nexus front-matter artifacts.
Significance Statement (pnasnexus-significance)
Why this is a flagship PNAS Nexus skill
Every PNAS Nexus Research Report (and Stage 2 Registered Report) must include a Significance Statement — a short, mandatory paragraph that explains, in plain language, why the work matters to science and society. It is read by editors at triage and by the broad, cross-disciplinary readership. It is not a second abstract. Getting it right is one of the highest-leverage things you can do, so draft it as soon as the central claim is locked.
When to trigger
- The submission (Research Report / Stage 2 Registered Report) has no Significance Statement.
- The Significance Statement just restates or condenses the abstract.
- It is dense with jargon and undefined acronyms.
- It is shorter than 50 words or longer than 120 words.
The hard rule: 50–120 words, written for a broad audience
- Length: between 50 and 120 words. PNAS Nexus states an explicit minimum of 50 and maximum of 120 words — so unlike a one-line summary, a too-short statement is also non-compliant. Confirm both bounds in the current PNAS Nexus author guidelines.
- Audience: an educated scientist outside your field. Write so a reader from another PNAS Nexus division (biological/health/medical, physical sciences & engineering, social & political) can follow it. (PNAS Nexus does not publish the exact flagship-PNAS "bright undergraduate" phrasing — but writing to roughly that level is a safe target.)
- Test: read it aloud to someone smart but not in your subfield. If they can say back why the result matters, it works.
What it must do (and not do)
The Significance Statement answers "so what, and who cares?" — the abstract answers "what did you do and find?"
| Significance Statement | Abstract (pnasnexus-abstract) |
|---|---|
| Why it matters, for a broad reader | What/how/found, for scientists |
| Plain language, minimal jargon | Technical but accessible |
| The gap + the advance + the broader consequence | Context, methods, quantified results, conclusion |
| 50–120 words | ≤250 words |
Template (a few short moves, no headings)
- The problem / gap (1–2 sentences). What broad question or limitation does the field face? State the stakes plainly.
- What this work shows (1–2 sentences). The advance, in non-technical terms — the result, not the method.
- Why it matters (1–2 sentences). The consequence for the field, for other fields, or for society.
- (Optional) one sentence on a concrete broader application or future direction.
One paragraph. No citations, no figure references, no undefined acronyms, no equations. Keep it within 50–120 words.
Show full SKILL.md (281 more words)Show less
Worked shape
"[Broad phenomenon] underlies [important process], yet how [specific gap] remains unclear. Here we show that [plain-language advance], demonstrating that [general principle]. This finding [changes/explains/enables] [broad consequence], with implications for [adjacent field or application]."
The non-specialist rewrite drill
When a draft statement is too technical, run this pass:
- Underline every word a researcher in another discipline would not know.
- Replace each with a plain phrase, or cut the sentence it lives in.
- Replace gene/protein/parameter names and acronyms with what they do ("a protein that controls cell division", not "CDK1").
- Read what remains. If the "why it matters" is now gone, you were hiding it behind jargon — write it back in plainly.
- Check the word count is still ≥ 50 — if the cuts dropped it below the floor, add a sentence of plain consequence, not more jargon.
Common failures (rewrite on sight)
- Out of bounds — under 50 or over 120 words; PNAS Nexus enforces both limits.
- A restatement of the abstract — editors notice immediately; it must be genuinely broader and plainer.
- Too technical — jargon, gene names, model parameters, acronyms.
- Method-led — leads with what you did rather than why it matters.
- Over-claiming — promising societal impact the data do not support (cross-check
pnasnexus-fit). - No "so what" — describes the result but never says why a non-specialist should care.
Output format
【Word count】 N — within 50–120? (both bounds enforced)
【Reader test】 can a non-specialist from another division state why it matters? yes/no
【Moves present?】 gap / advance(plain) / why-it-matters / (optional) application
【Distinct from abstract?】 yes/no (if no, rewrite — not a condensed abstract)
【Jargon / acronym hits removed】 [...]
【Over-claiming check】 consequence supported by the data? (link pnasnexus-fit if not)
【Next】 pnasnexus-abstractAnti-patterns
- Do not copy-paste or compress the abstract into the Significance Statement.
- Do not write it for specialists — write it for a reader outside the field.
- Do not fall below 50 words or exceed 120 — PNAS Nexus enforces both.
- Do not lead with methods; lead with the problem and the consequence.
- Do not claim societal impact the evidence cannot back.
© 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 PNAS-Nexus-Skills/skills/pnasnexus-significance of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pnasnexus Significance 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 |
|---|---|---|---|---|---|---|
| Pnasnexus Significance this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Suikonwiizo/suiko | 114 | — | ~1.8k | Automated safety check: Pass | MIT | |
| ISO 24495 Text AuditGaZmagik/iso-24495 | 190 | — | ~817 | Automated safety check: Pass | MIT | |
| Moai Domain HTML Reportmodu-ai/moai-adk | 1.2k | — | ~6.4k | Automated safety check: Notes | Apache-2.0 | |
| Writing Reference DocsBuilderIO/agent-native | 7.1k | — | ~3.5k | Automated safety check: Pass | None | |
| Content Productionborghei/Claude-Skills | 891 | — | ~4.8k | Automated safety check: Pass | MIT |
Similar skills
ISO 24495 Text Audit
GaZmagik/iso-24495
Audits a Markdown or text file or folder you choose for plain-language problems such as legalese, wordy phrases and long sentences, reporting each finding with file and line.
Moai Domain HTML Report
modu-ai/moai-adk
Markdown-to-single-file-HTML report renderer. An agent skill from modu-ai/moai-adk.
Writing Reference Docs
BuilderIO/agent-native
How to write a function/hook/action reference section, and how to write or rework a whole app's multi-page doc set (Overview/Features/Talk to the Agent/Cross-App Use/Developer Guide): plain-language…
Content Production
borghei/Claude-Skills
Full content production pipeline from blank page to publish-ready piece: research, briefs, drafting, SEO, readability, and editorial gates.
Rational Red Blue Debate
digoal/blog
Answer general or cross-domain questions with a non-pleasing rational mode: adversarial red-team and blue-team expert analysis, mutually exclusive conclusions, up to five debate rounds, saved…
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 Pnasnexus Significance
What does Pnasnexus Significance do?
A skill your agent uses to write the PNAS Nexus Significance Statement — between 50 and 120 words, in plain language for a broad scientific audience, explaining why the work matters. Pnasnexus Significance is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to write the PNAS Nexus Significance Statement — between 50 and 120 words, in plain language for a broad scientific audience, explaining why the work matters.
When should I use Pnasnexus Significance?
Pnasnexus Significance fits situations like: write the PNAS Nexus Significance Statement — between 50 and 120 words; in plain language for a broad scientific audience; explaining why the work matters.
How do I install Pnasnexus Significance in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-significance -a claude-code`. Or copy the skill folder (PNAS-Nexus-Skills/skills/pnasnexus-significance in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pnasnexus-significance in your project. Claude Code loads it when a task matches its description.
How do I install Pnasnexus Significance in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-significance -a codex`. Or copy the skill folder (PNAS-Nexus-Skills/skills/pnasnexus-significance in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pnasnexus-significance in your project. Codex loads it when a task matches its description.
Can I use Pnasnexus Significance 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 pnasnexus-significance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pnasnexus-significance, .gemini/skills/pnasnexus-significance, .github/skills/pnasnexus-significance and .opencode/skills/pnasnexus-significance in your project.
What does Pnasnexus Significance need to run?
SKILL.md names no scripts, command-line tools or credentials: Pnasnexus Significance is instructions for the agent only.
Does Pnasnexus Significance 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 Pnasnexus Significance 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 Pnasnexus Significance use?
Pnasnexus Significance 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 Pnasnexus Significance use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pnasnexus Significance?
Skills that share tags, products or a category with Pnasnexus Significance: Suiko (nwiizo/suiko, 114 stars), ISO 24495 Text Audit (GaZmagik/iso-24495, 190 stars), Moai Domain HTML Report (modu-ai/moai-adk, 1.2k stars) and Writing Reference Docs (BuilderIO/agent-native, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pnasnexus Significance?
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.