Topics
ZimoLiao/scholaraio
A skill your agent uses when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.
A skill your agent uses when deciding whether a software-engineering project belongs at ESEC/FSE or should be routed to ICSE, ASE, ISSTA, MSR, ICSME, or an SE journal (EMSE/TSE/TOSEM), and when…
MITAuto-check passed
Install Fse Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-topic-selection --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/FSE-Skills/skills/fse-topic-selection .claude/skills/fse-topic-selection && 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 "fse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-topic-selection into .claude/skills/fse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-topic-selection", 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/FSE-Skills/skills/fse-topic-selectionType 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 fse-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-topic-selection --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/FSE-Skills/skills/fse-topic-selection .agents/skills/fse-topic-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-topic-selection into .agents/skills/fse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-topic-selection", 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 fse-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-topic-selection --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/FSE-Skills/skills/fse-topic-selection .cursor/skills/fse-topic-selection && 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 "fse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-topic-selection into .cursor/skills/fse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-topic-selection", 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 FSE-Skills/skills/fse-topic-selection--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 fse-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-topic-selection --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/FSE-Skills/skills/fse-topic-selection .gemini/skills/fse-topic-selection && 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 "fse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-topic-selection into .gemini/skills/fse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-topic-selection", 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 fse-topic-selectionInstalls 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 fse-topic-selection -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/FSE-Skills/skills/fse-topic-selection .github/skills/fse-topic-selection && 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 "fse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-topic-selection into .github/skills/fse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-topic-selection", 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 fse-topic-selection -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 fse-topic-selection --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/FSE-Skills/skills/fse-topic-selection .opencode/skills/fse-topic-selection && 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 "fse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-topic-selection into .opencode/skills/fse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-topic-selection", 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
fse-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 625 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a software-engineering project belongs at ESEC/FSE or should be routed to ICSE, ASE, ISSTA, MSR, ICSME, or an SE journal (EMSE/TSE/TOSEM), and when…
- Deciding whether a software-engineering project belongs at ESEC/FSE
- SKILL.md covers The routing question that…, Sibling-venue routing table, Contribution shapes FSE rewards and The model-swap and re-label…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Should be routed to ICSE
What it does
Fse Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a software-engineering project belongs at ESEC/FSE or should be routed to ICSE, ASE, ISSTA, MSR, ICSME, or an SE journal (EMSE/TSE/TOSEM), and when distinguishing FSE from its sibling general-SE flagship ICSE by contribution shape, evidence maturity, and the PACMSE journal-style fit.
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.
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
- Deciding whether a software-engineering project belongs at ESEC/FSE
- Should be routed to ICSE
- An SE journal (EMSE/TSE/TOSEM)
- When distinguishing FSE from its sibling general-SE flagship ICSE by contribution shape
Example prompts
- “/fse-topic-selection”
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
Fse Topic Selection loads about 1.4k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 625 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). 625 words, ~1,429 tokens.
Download SKILL.mdSave it as
.claude/skills/fse-topic-selection/SKILL.md (or your agent's skills folder).- name
- fse-topic-selection
- description
- Use when deciding whether a software-engineering project belongs at ESEC/FSE or should be routed to ICSE, ASE, ISSTA, MSR, ICSME, or an SE journal (EMSE/TSE/TOSEM), and when distinguishing FSE from its sibling general-SE flagship ICSE by contribution shape, evidence maturity, and the PACMSE journal-style fit.
FSE Topic Selection
Decide the venue before drafting. FSE — the ACM International Conference on the Foundations of Software Engineering, historically ESEC/FSE on its European rotation — is one of the two general software-engineering flagships, alongside ICSE, and the ACM SIGSOFT home for foundational and empirical SE. Its research papers are PACMSE journal articles, so reviewers read for a durable software-engineering contribution, not a one-conference result. A technically strong paper whose real lesson is about compilers, PL semantics, or pure ML is respected and then rejected as out of scope.
The routing question that matters most
FSE and ICSE overlap heavily in scope and reviewer pool, so the decisive question is rarely "is this SE?" but "which SE community and calendar fits this paper now?" Both welcome techniques, empirical studies, and human-factors work. Use the finer signals below and the live deadlines to choose — a strong paper is publishable at either, and the nearer honest deadline usually wins.
Sibling-venue routing table
| Signal in your project | Better home | Why |
|---|---|---|
| Broad SE contribution, empirical or conceptual, ready now, and the next FSE deadline is nearer | ESEC/FSE | PACMSE journal-style track; the second general-SE flagship |
| Equally broad, but ICSE's cycle lands sooner or you want its stage | ICSE | Sibling general-SE flagship; different calendar and template (IEEE 10+2) |
| Core is automating a development task; tool/systems flavor dominates | ASE | Automated software engineering is its named center |
| Core is testing, program analysis, or fault detection with depth | ISSTA | Deeper testing/analysis expertise, round-based reviewing |
| The whole method is repository mining | MSR | Purpose-built co-located conference |
| Maintenance and software evolution focus | ICSME | Scope match |
| Study is too long or too nuanced for the page budget | EMSE / TSE / TOSEM | Journals with no conference page ceiling; some offer a journal-first path back to an FSE stage |
Contribution shapes FSE rewards
- Technique + tool + evaluation on real subjects — a new analysis, testing, repair, synthesis, or recommendation technique, embodied in a tool and evaluated on real systems against credible baselines (the CUTE lineage).
- Empirical study — mining, controlled experiments, or mixed-methods work that changes what the community believes about how software is built or maintained (the flaky-tests lineage).
- Methodology / measurement validity — interrogating an instrument the field relies on (the "are mutants a valid substitute?" lineage) — a distinctly prized FSE mode.
- Human and organizational factors — how practitioners actually use, trust, or abandon tools, with sound qualitative method.
- Foundational or conceptual — models, theories, or formal underpinnings with a clear SE payoff — the "foundations" in the name is not decorative.
Show full SKILL.md (216 more words)Show less
The model-swap and re-label tests
Two quick tests sharpen a borderline verdict:
- Model-swap test: if your paper leans on an LLM or learner, ask whether the software- engineering lesson survives swapping the model for another. If not, the model is the contribution and a PL/ML venue fits better.
- Re-label test: could this paper be submitted to ISSTA or ASE unchanged and read as native there? If its heart is testing depth or automation machinery, route accordingly; FSE rewards the broader SE framing and empirical breadth.
Evidence maturity, without the ladder cliché
Fit is necessary but not sufficient: the same idea sits at different doors depending on how far the evidence has come. An observation with an argument but no study is a workshop or vision paper; a working technique evaluated only on examples you chose needs real subjects before the research track; a study too deep for the page budget belongs in a journal first. Submitting one step early earns a polite "promising, but..." and costs a full cycle, because FSE, like its siblings, runs on an annual rhythm.
Cheap reconnaissance before committing
[Scope] scan the last two FSE programs (dblp, conf.researchr.org) for your subarea
-> 3+ recent papers = a reviewer pool exists; 0 = opening or mismatch
[Citations] is your bibliography majority SE venues (ICSE/FSE/ASE/ISSTA/EMSE/TSE)?
-> majority non-SE => reviewers read you as a visitor; naturalize the intro first
[Calendar] compare the next FSE deadline with ICSE/ASE/ISSTA/journal dates -> route to the
nearest honest fit rather than waiting a year for a marginal preferenceDecision procedure
[Audience] who acts differently if the claim holds? -> SE developers/testers/maintainers/researchers?
[Claim type] technique / empirical / methodology / human-factors / foundational
[FSE vs ICSE] both fit? -> choose by calendar, community pull, and template preference
[Sibling check] testing depth -> ISSTA; automation core -> ASE; mining-only -> MSR
[Verdict] ESEC/FSE research track / sibling venue / journal-first, with a one-line reasonRun this before the writing skills; a wrong venue decision wastes every later step. When the
verdict is FSE, continue with fse-workflow for the calendar and fse-writing-style for the
paper shape.
© 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 FSE-Skills/skills/fse-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fse Topic Selection 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 |
|---|---|---|---|---|---|---|
| Fse Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| TopicsZimoLiao/scholaraio | 577 | — | ~294 | Automated safety check: Pass | MIT | |
| Topic Modelingbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Bestblogs Topicginobefun/BestBlogs | 4k | — | ~670 | Automated safety check: Pass | None | |
| Zsxq Topicitwanger/toBeBetterJavaer | 18k | — | ~564 | Automated safety check: Pass | None | |
| Pubmed Topic Recommendaipoch/medical-research-skills | 2k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Topic Modeling
brycewang-stanford/Auto-Empirical-Research-Skills
Structural topic modeling: STM spec, topic count, coherence-exclusivity.
Bestblogs Topic
ginobefun/BestBlogs
A skill your agent uses when the user asks about a specific topic, subject area, or wants to explore curated topic pages on BestBlogs.
Zsxq Topic
itwanger/toBeBetterJavaer
知识星球主题管理：搜索主题、查看主题详情、发布帖子、编辑主题、发表评论、回复某条评论（楼中楼）、回答提问、删除主题；通过 api call 查看主题评论列表、设置精华、设置标签、查看自己提的问题与已回答记录。当用户需要查找内容、发帖、编辑主题、评论、回复评论、回答问题、删除主题、查看主题评论、查看自己的提问记录、或管理主题精华和标签时使用。
Pubmed Topic Recommend
aipoch/medical-research-skills
Generate ~5 actionable research topic recommendations by querying PubMed E-utilities; use when a user provides a research direction/constraints and needs evidence-backed topic ideas quickly.
TiXL UI Topic Doc Writer
tixl3d/tixl
Fills in empty embedded help text for TiXL's UI topics by distilling the maintainer's own video explanations into short, user-facing doc entries.
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 Fse Topic Selection
What does Fse Topic Selection do?
A skill your agent uses when deciding whether a software-engineering project belongs at ESEC/FSE or should be routed to ICSE, ASE, ISSTA, MSR, ICSME, or an SE journal (EMSE/TSE/TOSEM), and when…. Fse Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a software-engineering project belongs at ESEC/FSE or should be routed to ICSE, ASE, ISSTA, MSR, ICSME, or an SE journal (EMSE/TSE/TOSEM), and when distinguishing FSE from its sibling general-SE flagship ICSE by contribution shape, evidence maturity, and the PACMSE journal-style fit.
When should I use Fse Topic Selection?
Fse Topic Selection fits situations like: deciding whether a software-engineering project belongs at ESEC/FSE; should be routed to ICSE; an SE journal (EMSE/TSE/TOSEM); when distinguishing FSE from its sibling general-SE flagship ICSE by contribution shape.
How do I install Fse Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-topic-selection -a claude-code`. Or copy the skill folder (FSE-Skills/skills/fse-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fse-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Fse Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-topic-selection -a codex`. Or copy the skill folder (FSE-Skills/skills/fse-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fse-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Fse Topic Selection 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 fse-topic-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fse-topic-selection, .gemini/skills/fse-topic-selection, .github/skills/fse-topic-selection and .opencode/skills/fse-topic-selection in your project.
What does Fse Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Fse Topic Selection is instructions for the agent only.
Does Fse Topic Selection 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 Fse Topic Selection 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 Fse Topic Selection use?
Fse Topic Selection 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 Fse Topic Selection use?
About 1.4k tokens (SKILL.md is roughly 5.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 Fse Topic Selection?
Skills that share tags, products or a category with Fse Topic Selection: Topics (ZimoLiao/scholaraio, 577 stars), Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Bestblogs Topic (ginobefun/BestBlogs, 4k stars) and Zsxq Topic (itwanger/toBeBetterJavaer, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fse Topic Selection?
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.