Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026, de-anonymization and the one-page acknowledgments allowance, folding…
Install Colm Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-camera-ready --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/COLM-Skills/skills/colm-camera-ready .claude/skills/colm-camera-ready && 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 "colm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-camera-ready into .claude/skills/colm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-camera-ready", 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/COLM-Skills/skills/colm-camera-readyType 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 colm-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-camera-ready --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/COLM-Skills/skills/colm-camera-ready .agents/skills/colm-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "colm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-camera-ready into .agents/skills/colm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-camera-ready", 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 colm-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-camera-ready --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/COLM-Skills/skills/colm-camera-ready .cursor/skills/colm-camera-ready && 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 "colm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-camera-ready into .cursor/skills/colm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-camera-ready", 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 COLM-Skills/skills/colm-camera-ready--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 colm-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-camera-ready --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/COLM-Skills/skills/colm-camera-ready .gemini/skills/colm-camera-ready && 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 "colm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-camera-ready into .gemini/skills/colm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-camera-ready", 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 colm-camera-readyInstalls 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 colm-camera-ready -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/COLM-Skills/skills/colm-camera-ready .github/skills/colm-camera-ready && 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 "colm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-camera-ready into .github/skills/colm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-camera-ready", 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 colm-camera-ready -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 colm-camera-ready --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/COLM-Skills/skills/colm-camera-ready .opencode/skills/colm-camera-ready && 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 "colm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-camera-ready into .opencode/skills/colm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-camera-ready", 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
colm-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 851 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026, de-anonymization and the one-page acknowledgments allowance, folding…
- Converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026
- SKILL.md covers The one-month plan, De-anonymization, done in both…, Honoring the rebuttal ledger and Metadata and the public record, plus 5 more sections
- Calls pdftotext
- De-anonymization and the one-page acknowledgments allowance
What it does
Colm Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026, de-anonymization and the one-page acknowledgments allowance, folding rebuttal commitments into the text, publishing on OpenReview, releasing artifacts publicly, and planning the October conference in San Francisco.
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.
It sits in Research & Science. 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
- Converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026
- De-anonymization and the one-page acknowledgments allowance
- Folding rebuttal commitments into the text
- Publishing on OpenReview
Example prompts
- “/colm-camera-ready”
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
Shell commands in SKILL.md call:
pdftotext
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
Colm Camera Ready loads about 1.7k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 851 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). 851 words, ~1,699 tokens.
Download SKILL.mdSave it as
.claude/skills/colm-camera-ready/SKILL.md (or your agent's skills folder).- name
- colm-camera-ready
- description
- Use when converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026, de-anonymization and the one-page acknowledgments allowance, folding rebuttal commitments into the text, publishing on OpenReview, releasing artifacts publicly, and planning the October conference in San Francisco.
COLM Camera-Ready
Decisions for COLM 2026 landed July 8 and camera-ready is due August 7 — a one-month window. COLM publishes its papers openly on OpenReview rather than through an external proceedings publisher, which makes the camera-ready unusually final: what you upload is the public record, discoverable within days, forever attached to your OpenReview forum with its reviews.
The one-month plan
| Week (2026 dates) | Work |
|---|---|
| Jul 8-14 | Read the meta-review and decision notes; list every commitment made in rebuttal; decide which promised changes are in-scope for camera-ready |
| Jul 15-24 | Execute the text changes; de-anonymize; build the public artifact release in parallel (colm-artifact-evaluation) |
| Jul 25-31 | Full-paper cold read by a co-author who did not edit it; verify every link resolves to the public, de-anonymized artifact |
| Aug 1-7 | Format check on the final COLM template, metadata check, upload with days to spare |
De-anonymization, done in both directions
Adding identity back is the easy half. The camera-ready pass must also reverse every anonymization workaround the submission introduced:
- Restore author names, affiliations, and correspondence.
- Add acknowledgments — under the 2026 format an optional acknowledgments section of at most one page sits outside the 9-page limit. Fund-source and compute-donor acknowledgments live here; check funder-mandated wording.
- Swap anonymized repository links for the real, tagged public repo; replace anonymized model-hub IDs with your org's actual IDs.
- Un-contort self-citations: "the dataset of [7]" can become "our earlier dataset [7]" where that is clearer.
- Then sweep for stragglers — a leftover "anonymous.4open.science" link in the published PDF is the classic COLM-camera-ready fossil.
# Fossil hunt on the final PDF before upload
pdftotext camera-ready.pdf - | grep -niE 'anonym|blinded|redacted|placeholder|TODO|XXX' | head
pdftotext camera-ready.pdf - | grep -noE 'https?://[^ ]+' | sort -u # every link: click each oneHonoring the rebuttal ledger
Reviewers and the AC accepted a paper that includes what you promised in the May-June discussion. Fold in: rescoped claims exactly as conceded, the R1/R2/... tables or their summaries, corrected version strings and query dates, and the limitations you agreed to add. Silently dropping a rebuttal commitment is visible — the whole discussion sits on the same OpenReview page as your final PDF.
Also re-check facts that aged during review: an API model you evaluated in March
may have been deprecated by August. Do not re-run and overwrite (the paper reports
the March measurements); do update the availability language so readers know what
is still queryable (colm-reproducibility).
Metadata and the public record
- Title, author order, and abstract in the OpenReview form must match the PDF exactly — this metadata is what indexers and citation managers scrape.
- The LLM-usage disclosure travels with the paper; if camera-ready edits changed what should be disclosed, update it.
- 待核实 items this cycle (verify on the current author guide before upload): whether camera-ready grants extra content pages beyond 9, the exact license terms of the OpenReview publication, and any required funding/COI statement format. None was verifiable on 2026-07-08.
Artifact release and the arXiv decision
Ship the public artifacts in the same pass as the PDF: tagged code release, weights and datasets with cards, the cached-outputs archive if ToS permits, and the paper's OpenReview URL embedded in each artifact's documentation. If you also post to arXiv, note that the OpenReview version is the version of record and keep the two synchronized — a drifting arXiv copy generates years of confused citations.
Show full SKILL.md (336 more words)Show less
The forum is part of the publication
Because COLM publishes on OpenReview, your paper's public page carries the entire review history: scores, rebuttal, AC notes. Readers will scroll down. Three consequences worth acting on during camera-ready week:
- The rebuttal is now documentation. Numbers and clarifications that exist only in the discussion thread get cited by careful readers; make sure everything load-bearing from the thread made it into the PDF so the paper does not depend on its own comment section.
- Discrepancies are visible. If the discussion says "we will rescope claim X" and the final PDF still makes claim X, anyone can see it. The rebuttal ledger audit above is not optional politeness; it is public-record consistency.
- The forum stays live. Post-publication questions sometimes arrive as comments. Decide who on the author team watches the forum through the October conference and answers with the same care as the rebuttal.
October logistics
COLM 2026 runs October 6-9 at the Hilton Union Square, San Francisco (main conference October 6-8, workshop day October 9). Presentation format assignments, registration requirements for accepted papers, poster specs, and any remote- participation option were not verifiable at pack-build time — all 待核实 via the conference's announcements before booking. What is safely plannable now: at least one author available in San Francisco that week, a poster-design slot in late September, and visa timelines for authors who need them, which in a July-to-October gap are the item most often fumbled.
Common fossils, ranked by embarrassment
From most to least visible in published COLM-style PDFs: an "Anonymous Authors" block surviving into the final version; anonymized-repo links next to the real ones; "we thank the anonymous reviewers" without the funding acknowledgments the grant requires; rebuttal-era "R1/R2" table labels leaking into the final text; appendix cross-references broken by post-acceptance renumbering; and an abstract in the OpenReview form that still matches the March submission instead of the August PDF. Each is a two-minute check; the full sweep is under an hour and is the last hour that matters.
Output format
[Countdown] days to camera-ready: <n>
[Rebuttal ledger] commitments folded in: <k>/<total> — outstanding: <items>
[De-anon sweep] identity restored ▢ workarounds reversed ▢ fossils: <hits>
[Links] all resolve to public artifacts ▢
[待核实 checked live] extra-pages? license? attendance rules?
[October] presenter ▢ visa ▢ poster slot ▢© 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 COLM-Skills/skills/colm-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Colm Camera Ready 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 |
|---|---|---|---|---|---|---|
| Colm Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
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 Colm Camera Ready
What does Colm Camera Ready do?
A skill your agent uses when converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026, de-anonymization and the one-page acknowledgments allowance, folding…. Colm Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026, de-anonymization and the one-page acknowledgments allowance, folding rebuttal commitments into the text, publishing on OpenReview, releasing artifacts publicly, and planning the October conference in San Francisco.
When should I use Colm Camera Ready?
Colm Camera Ready fits situations like: converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026; de-anonymization and the one-page acknowledgments allowance; folding rebuttal commitments into the text; publishing on OpenReview.
How do I install Colm Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-camera-ready -a claude-code`. Or copy the skill folder (COLM-Skills/skills/colm-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/colm-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Colm Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-camera-ready -a codex`. Or copy the skill folder (COLM-Skills/skills/colm-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/colm-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Colm Camera Ready 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 colm-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/colm-camera-ready, .gemini/skills/colm-camera-ready, .github/skills/colm-camera-ready and .opencode/skills/colm-camera-ready in your project.
What does Colm Camera Ready need to run?
Going by SKILL.md and its folder, Colm Camera Ready needs the command-line tools its instructions call (pdftotext).
Does Colm Camera Ready 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 Colm Camera Ready 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 Colm Camera Ready use?
Colm Camera Ready 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 Colm Camera Ready use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Colm Camera Ready?
Skills that share tags, products or a category with Colm Camera Ready: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Colm Camera Ready?
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.