Ito Compute
affaan-m/ECC
Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, revoke device credentials, and run explicitly gated node qualification through the separately…
A skill your agent uses when deciding whether a pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when…
MITAuto-check passed
Install Percom Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-topic-selection .claude/skills/percom-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 "percom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-topic-selection into .claude/skills/percom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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/PerCom-Skills/skills/percom-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 percom-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-topic-selection .agents/skills/percom-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 "percom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-topic-selection into .agents/skills/percom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-topic-selection .cursor/skills/percom-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 "percom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-topic-selection into .cursor/skills/percom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 PerCom-Skills/skills/percom-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 percom-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-topic-selection .gemini/skills/percom-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 "percom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-topic-selection into .gemini/skills/percom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-topic-selection .github/skills/percom-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 "percom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-topic-selection into .github/skills/percom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-topic-selection .opencode/skills/percom-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 "percom-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-topic-selection into .opencode/skills/percom-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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
percom-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 608 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 pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when…
- Deciding whether a pervasive-computing project belongs at IEEE PerCom
- SKILL.md covers The routing question that…, Neighbor-venue routing table, Contribution shapes PerCom… and The human-centricity and…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Should be routed to ACM UbiComp/IMWUT
What it does
Percom Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when distinguishing PerCom's human-centric ubicomp focus from networked-sensor-systems venues by contribution shape, the human-centricity test, and the IEEE-conference vs. IMWUT-journal model.
Its SKILL.md is about 1.5k 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 pervasive-computing project belongs at IEEE PerCom
- Should be routed to ACM UbiComp/IMWUT
- When distinguishing PerComs human-centric ubicomp focus from networked-sensor-systems venues by contribution shape
- The human-centricity test
Example prompts
- “/percom-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
Percom Topic Selection loads about 1.5k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 608 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). 608 words, ~1,501 tokens.
Download SKILL.mdSave it as
.claude/skills/percom-topic-selection/SKILL.md (or your agent's skills folder).- name
- percom-topic-selection
- description
- Use when deciding whether a pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when distinguishing PerCom's human-centric ubicomp focus from networked-sensor-systems venues by contribution shape, the human-centricity test, and the IEEE-conference vs. IMWUT-journal model.
PerCom Topic Selection
Decide the venue before drafting. PerCom — the IEEE International Conference on Pervasive Computing and Communications — is IEEE's flagship for human-centric ubiquitous computing: activity recognition, context-awareness, wearable and mobile sensing, and smart environments. Its papers are IEEE Xplore proceedings read for a pervasive-computing contribution grounded in real human use. A technically strong paper whose real lesson is about network protocols, low-power hardware, or a pure ML model is respected and then rejected as out of scope.
The routing question that matters most
PerCom overlaps most with ACM UbiComp/IMWUT in topic — both cover HAR, wearables, and smart spaces — so the decisive question is rarely "is this ubicomp?" but "which model and calendar fits this paper now?" UbiComp presents papers published in the IMWUT journal on rolling quarterly deadlines with a revise cycle; PerCom is an IEEE conference with a single annual deadline, a bounded rebuttal, and an in-person-presentation requirement. A strong ubicomp paper is publishable at either — choose by the publication model you want and the nearer honest deadline.
Neighbor-venue routing table
| Signal in your project | Better home | Why |
|---|---|---|
| Human-centric ubicomp (HAR, context, wearables, smart space), ready now, PerCom deadline nearer | IEEE PerCom | IEEE conference flagship; annual deadline + rebuttal |
| Same topic, but you want a journal publication and a rolling deadline | ACM UbiComp / IMWUT | Journal model, quarterly submissions, revise cycle |
| Core is wireless/cellular networking or the mobile network itself | MobiCom / MobiSys | Mobile-networking and mobile-systems centers |
| Core is a low-power networked-sensor system or sensor-platform design | SenSys | Networked sensor systems, not human-centric ubicomp |
| Core is information processing in sensor networks / signal-level sensing | IPSN | Sensor-network information processing |
| Study is a deep dataset/measurement better as an archival journal article | IMWUT / IEEE journals | Journal length and revise cycle |
Contribution shapes PerCom rewards
- Human activity / context recognition — a recognizer or model for human activity, context, or behavior from mobile/wearable/ambient sensors, evaluated cross-subject on real people (the EMGSense lineage).
- Pervasive system / infrastructure — a deployable system for sensing, localization, or smart environments whose insight outlives the specific hardware (the LANDMARC lineage).
- Sensing tooling / datasets — a generator, framework, or dataset that unblocks how the community evaluates (the SmartSPEC lineage).
- Sensing consequence / privacy — surfacing what ubiquitous sensing makes possible on real devices, for good or ill (the DeepMag side-channel lineage).
- Context modeling / device-to-device — treating context as a first-class systems concern with real deployment tradeoffs (the CHITCHAT lineage).
Show full SKILL.md (220 more words)Show less
The human-centricity and model-swap tests
Two quick tests sharpen a borderline verdict:
- Human-centricity test: is a person — their activity, context, behavior, or environment — the center of the contribution? If the paper is really about the network stack or the sensor hardware with no human at the center, route to MobiCom/MobiSys or SenSys/IPSN.
- Model-swap test: if the paper leans on a deep model, ask whether the pervasive-computing lesson survives swapping the model for another. If not, the model is the contribution and an ML venue fits better; PerCom rewards the ubicomp insight, not the architecture.
Evidence maturity, without the ladder cliché
Fit is necessary but not sufficient: the same idea sits at different doors depending on evidence maturity. A recognizer evaluated only within-subject or in-lab needs cross-subject, free-living data before the research track; a system shown only on your own testbed needs a realistic deployment; a study too deep and long for 9 pages may belong in IMWUT first. Submitting a step early earns a polite "promising, but the evaluation is within-subject" and costs a full cycle, because PerCom runs on an annual rhythm.
Cheap reconnaissance before committing
[Scope] scan the last two PerCom programs (dblp, percom.org) for your subarea
-> 3+ recent papers = a reviewer pool exists; 0 = opening or mismatch
[Citations] is your bibliography majority ubicomp/mobile/sensing venues (PerCom/UbiComp/IMWUT/
MobiCom/SenSys)? -> majority non-ubicomp => reviewers read you as a visitor; naturalize first
[Calendar] compare the next PerCom deadline (annual, ~Sep) with IMWUT's rolling quarterly cutoffs
and MobiCom/SenSys dates -> route to the nearest honest fit, not a year's waitDecision procedure
[Audience] who acts differently if the claim holds? -> ubicomp researchers/practitioners/users?
[Claim type] recognition / system / tooling-dataset / sensing-consequence / context-modeling
[Human-centricity] is a person at the center? -> yes: PerCom-family; no: MobiCom/SenSys/IPSN
[PerCom vs IMWUT] both fit? -> conference+rebuttal+annual (PerCom) vs journal+rolling (IMWUT)
[Verdict] PerCom research track / neighbor 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 PerCom, continue with percom-workflow for the calendar and percom-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 PerCom-Skills/skills/percom-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Percom 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 |
|---|---|---|---|---|---|---|
| Percom Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Ito Computeaffaan-m/ECC | 275k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Senior Computer Visiondavila7/claude-code-templates | 32k | 3 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Senior Computer Visionalirezarezvani/claude-skills | 28k | 2 repos | ~3.2k | Automated safety check: Pass | MIT | |
| GCP Computesickn33/agentic-awesome-skills | 47k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Computer UseQwenLM/qwen-code | 28k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Senior Computer Vision
davila7/claude-code-templates
World-class computer vision skill for image/video processing, object detection, segmentation, and visual AI systems.
Senior Computer Vision
alirezarezvani/claude-skills
Computer vision engineering skill for object detection, image segmentation, and visual AI systems.
GCP Compute
sickn33/agentic-awesome-skills
Manage Compute Engine instances and instance templates. An agent skill from sickn33/agentic-awesome-skills.
Computer Use
QwenLM/qwen-code
Control local desktop applications through Computer Use for tasks that require reading or operating app UI.
Codewhale Computer Use Controller
codewhale-hq/Codewhale
Operates desktop apps and isolated or disposable browsers on registered computers through an observe, act, verify loop, separate from driving the user's own signed-in Chrome.
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 Percom Topic Selection
What does Percom Topic Selection do?
A skill your agent uses when deciding whether a pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when…. Percom Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when distinguishing PerCom's human-centric ubicomp focus from networked-sensor-systems venues by contribution shape, the human-centricity test, and the IEEE-conference vs.
When should I use Percom Topic Selection?
Percom Topic Selection fits situations like: deciding whether a pervasive-computing project belongs at IEEE PerCom; should be routed to ACM UbiComp/IMWUT; when distinguishing PerComs human-centric ubicomp focus from networked-sensor-systems venues by contribution shape; the human-centricity test.
How do I install Percom Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-topic-selection -a claude-code`. Or copy the skill folder (PerCom-Skills/skills/percom-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/percom-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Percom Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-topic-selection -a codex`. Or copy the skill folder (PerCom-Skills/skills/percom-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/percom-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Percom 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 percom-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/percom-topic-selection, .gemini/skills/percom-topic-selection, .github/skills/percom-topic-selection and .opencode/skills/percom-topic-selection in your project.
What does Percom Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Percom Topic Selection is instructions for the agent only.
Does Percom 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 Percom 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 Percom Topic Selection use?
Percom 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 Percom Topic Selection use?
About 1.5k tokens (SKILL.md is roughly 6k 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 Percom Topic Selection?
Skills that share tags, products or a category with Percom Topic Selection: Ito Compute (affaan-m/ECC, 275k stars), Senior Computer Vision (davila7/claude-code-templates, 32k stars), Senior Computer Vision (alirezarezvani/claude-skills, 28k stars) and GCP Compute (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Percom Topic Selection?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.