How To Communicate
databasus/databasus
Communicate clearly in every response, progress update and agent-authored document.
A skill your agent uses when planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission, where no standing rebuttal phase exists — covering pre-emptive writing…
MITAuto-check passed
Install Stoc Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-author-response --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/STOC-Skills/skills/stoc-author-response .claude/skills/stoc-author-response && 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 "stoc-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-author-response into .claude/skills/stoc-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-author-response", 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/STOC-Skills/skills/stoc-author-responseType 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 stoc-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-author-response --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/STOC-Skills/skills/stoc-author-response .agents/skills/stoc-author-response && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stoc-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-author-response into .agents/skills/stoc-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-author-response", 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 stoc-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-author-response --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/STOC-Skills/skills/stoc-author-response .cursor/skills/stoc-author-response && 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 "stoc-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-author-response into .cursor/skills/stoc-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-author-response", 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 STOC-Skills/skills/stoc-author-response--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 stoc-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-author-response --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/STOC-Skills/skills/stoc-author-response .gemini/skills/stoc-author-response && 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 "stoc-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-author-response into .gemini/skills/stoc-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-author-response", 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 stoc-author-responseInstalls 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 stoc-author-response -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/STOC-Skills/skills/stoc-author-response .github/skills/stoc-author-response && 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 "stoc-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-author-response into .github/skills/stoc-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-author-response", 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 stoc-author-response -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 stoc-author-response --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/STOC-Skills/skills/stoc-author-response .opencode/skills/stoc-author-response && 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 "stoc-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-author-response into .opencode/skills/stoc-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-author-response", 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
stoc-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 874 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission, where no standing rebuttal phase exists — covering pre-emptive writing…
- Planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission
- SKILL.md covers Channel 1: the response you…, Channel 2: chair-mediated…, Channel 3: the post-decision… and Reading theory reviews…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Where no standing rebuttal phase exists — covering pre-emptive writing that answers objections in advance
What it does
Stoc Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission, where no standing rebuttal phase exists — covering pre-emptive writing that answers objections in advance, chair-mediated technical clarifications if the PC asks, and the FOCS resubmission letter after a rejection.
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.
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
- Planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission
- Where no standing rebuttal phase exists — covering pre-emptive writing that answers objections in advance
- Chair-mediated technical clarifications if the PC asks
- The FOCS resubmission letter after a rejection
Example prompts
- “/stoc-author-response”
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
Stoc Author Response loads about 1.7k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 874 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). 874 words, ~1,740 tokens.
Download SKILL.mdSave it as
.claude/skills/stoc-author-response/SKILL.md (or your agent's skills folder).- name
- stoc-author-response
- description
- Use when planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission, where no standing rebuttal phase exists — covering pre-emptive writing that answers objections in advance, chair-mediated technical clarifications if the PC asks, and the FOCS resubmission letter after a rejection.
STOC Author Response
Set expectations first: the STOC 2026 Call for Papers announced no author-response or rebuttal round, and the decision timeline ran directly from the November 4, 2025 deadline to notification on or before February 1, 2026 (checked 2026-07-08). Historically STOC decisions arrive without authors ever seeing the reviews before the outcome. Whether any given cycle adds a feedback experiment is a per-year choice: 待核实 against the live CFP and PC-chair announcements each fall. This skill therefore covers the three channels that actually exist.
Channel 1: the response you write before submitting
At a no-rebuttal venue, every anticipated objection must be answered inside the submission itself, because there is no second chance. Build an objection ledger during the final month and discharge each row into the paper:
| Predictable objection | Where to discharge it in a STOC submission |
|---|---|
| "Is this not implied by [known result]?" | A "Comparison with prior work" paragraph that names the result and states the formal gap |
| "The improvement is only in the exponent/log factor" | An explicit "Why this barrier matters" passage citing the known obstruction |
| "The technique looks standard" | A technical-overview section isolating the genuinely new step |
| "Does the proof of Lemma X really work?" | Full proof in the appendix plus a one-line proof idea at the statement |
| "Why STOC and not SODA/CCC/ITCS?" | First-page framing that names the cross-area consequence |
| "The model seems contrived" | A remarks subsection defending the model with prior uses |
A useful drill: have a colleague write three hostile review sentences, then verify the submission already contains the counter-text at a location the table of contents makes findable.
Channel 2: chair-mediated clarification
Theory PCs sometimes route a narrow technical question to authors through the PC chair when correctness of a specific step is the deciding issue. You cannot solicit this contact; you can only be ready for it. If it comes:
- Answer only the question asked. This is not a rebuttal; volunteered advocacy reads poorly and may be discarded.
- Point to line numbers and displayed equations in the submitted PDF, not to a revised draft the committee has never seen.
- If the questioned step is actually broken, say so and state precisely what survives — theory committees have accepted papers whose authors honestly downgraded one lemma, and rejected papers whose authors papered over a gap.
Reply skeleton (keep under ~300 words, anonymous if the cycle is double-blind):
1. Restate the question in one line.
2. The direct answer: the step holds because <argument>, see p.<n>, Eq. (<k>).
3. If a hypothesis was implicit: name it, confirm it is satisfied where used.
4. If repair is needed: the corrected statement, and what changes downstream.Channel 3: the post-decision letter to yourself
Reviews arrive with the decision. The productive response is a resubmission memo written within a week, while the reviews are fresh:
- Sort review points into: correctness challenges (must resolve before any resubmission), significance challenges (need reframing or a stronger result), and presentation complaints (cheap to fix).
- The default next stop is FOCS, whose deadline sits roughly five months after
STOC notification (FOCS 2026: April 1, 2026, 21:00 UTC, for a November 2026
conference in New York — verified 2026-07-08 at
focs.computer.org/2026/). The same community reviews both venues; an unchanged resubmission is frequently re-reviewed by an overlapping pool, so visible improvement is strategy, not courtesy. - If reviewers questioned significance rather than correctness, consider whether the result is better amortized into a stronger merged paper than resubmitted alone.
Show full SKILL.md (361 more words)Show less
Reading theory reviews accurately
STOC reviews released with decisions vary from a paragraph to several pages. Decode them before reacting:
- A long, detailed review with line-level proof comments means a subreviewer invested real verification effort — its technical points are usually right and always worth fixing, whatever the outcome.
- "I could not verify Section 5" is not a neutral remark; at this venue an unverified central section is a rejection reason by itself, and the repair is exposition, not indignation.
- "Better suited to
<venue>" is the breadth axis talking. It is often the most actionable sentence in the review: the mathematics passed, the framing or the routing failed. - Contradictory reviews (one calls it deep, another incremental) usually mean
the technical overview let readers form divergent models of the
contribution; that is a writing bug with a known fix (
stoc-writing-style).
What not to do
- Do not email PC members or the chair to argue a decision; theory norms treat this as a serious breach, and decisions are final.
- Do not post a public rebuttal thread attacking anonymous reviewers while the companion journal version is under review with the same community.
- Do not treat the absence of rebuttal as license to leave known weaknesses unaddressed "unless asked" — at STOC, unasked is unanswered.
Timing the channels
- Objection-ledger work belongs in the last month before the deadline, once the results are frozen — earlier, and the objections target statements that will change; later, and the discharge text has no pages left to live in.
- A chair-mediated query, if it comes, tends to arrive mid-cycle (December–January in the 2026 calendar) with a short fuse; keep the proof sources and the corrections file warm rather than reconstructing context under a 48-hour clock.
- The resubmission memo has a one-week half-life: written immediately, it captures what the reviews actually said; written a month later, it captures what you wish they had said.
Cycle-volatility warnings
- Any experiment adding an author-visible feedback step will be announced in the CFP or on the HotCRP site for that year; do not assume continuity (待核实).
- The chair-mediated clarification practice is a community custom, not a documented right; some cycles use it, some never do.
Output format
[Channel in play] pre-emptive writing / chair query received / post-decision triage
[Objection ledger] <objection -> discharge location in the PDF>
[Query reply plan] <question, answer location, honesty check>
[Resubmission target] FOCS <deadline> / SODA / journal / strengthen first
[Risk] <the one unresolved reviewer concern>© 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 STOC-Skills/skills/stoc-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Stoc Author Response 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 |
|---|---|---|---|---|---|---|
| Stoc Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| How To Communicatedatabasus/databasus | 8.8k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Abp Authorizationabpframework/abp | 14k | — | ~1.3k | Automated safety check: Pass | LGPL-3.0 | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Focs Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
Abp Authorization
abpframework/abp
ABP permission system - PermissionDefinitionProvider, [Authorize] attribute, CheckPolicyAsync, IsGrantedAsync, ICurrentUser, IPermissionManager, multi-tenancy side.
Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
Focs Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when managing author-side communication around a FOCS (IEEE Symposium on Foundations of Computer Science) submission, where no rebuttal round exists — discharging objections…
Cikm Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when preparing author-side communication around CIKM reviews — drafting for a response window if the cycle offers one (unconfirmed for 2026), writing camera-ready revision…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Stoc Author Response
What does Stoc Author Response do?
A skill your agent uses when planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission, where no standing rebuttal phase exists — covering pre-emptive writing…. Stoc Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission, where no standing rebuttal phase exists — covering pre-emptive writing that answers objections in advance, chair-mediated technical clarifications if the PC asks, and the FOCS resubmission letter after a rejection.
When should I use Stoc Author Response?
Stoc Author Response fits situations like: planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission; where no standing rebuttal phase exists — covering pre-emptive writing that answers objections in advance; chair-mediated technical clarifications if the PC asks; the FOCS resubmission letter after a rejection.
How do I install Stoc Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-author-response -a claude-code`. Or copy the skill folder (STOC-Skills/skills/stoc-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/stoc-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Stoc Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-author-response -a codex`. Or copy the skill folder (STOC-Skills/skills/stoc-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/stoc-author-response in your project. Codex loads it when a task matches its description.
Can I use Stoc Author Response 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 stoc-author-response -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stoc-author-response, .gemini/skills/stoc-author-response, .github/skills/stoc-author-response and .opencode/skills/stoc-author-response in your project.
What does Stoc Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Stoc Author Response is instructions for the agent only.
Does Stoc Author Response 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 Stoc Author Response 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 Stoc Author Response use?
Stoc Author Response 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 Stoc Author Response use?
About 1.7k tokens (SKILL.md is roughly 7k 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 Stoc Author Response?
Skills that share tags, products or a category with Stoc Author Response: How To Communicate (databasus/databasus, 8.8k stars), Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Abp Authorization (abpframework/abp, 14k stars) and Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stoc Author Response?
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.