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 database-theory project belongs at ICDT (International Conference on Database Theory) or should be routed to PODS, the co-located EDBT systems track…
MITAuto-check passed
Install Icdt Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-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/ICDT-Skills/skills/icdt-topic-selection .claude/skills/icdt-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 "icdt-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-topic-selection into .claude/skills/icdt-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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/ICDT-Skills/skills/icdt-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 icdt-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-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/ICDT-Skills/skills/icdt-topic-selection .agents/skills/icdt-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 "icdt-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-topic-selection into .agents/skills/icdt-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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 icdt-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-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/ICDT-Skills/skills/icdt-topic-selection .cursor/skills/icdt-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 "icdt-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-topic-selection into .cursor/skills/icdt-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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 ICDT-Skills/skills/icdt-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 icdt-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-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/ICDT-Skills/skills/icdt-topic-selection .gemini/skills/icdt-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 "icdt-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-topic-selection into .gemini/skills/icdt-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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 icdt-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 icdt-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/ICDT-Skills/skills/icdt-topic-selection .github/skills/icdt-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 "icdt-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-topic-selection into .github/skills/icdt-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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 icdt-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 icdt-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/ICDT-Skills/skills/icdt-topic-selection .opencode/skills/icdt-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 "icdt-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-topic-selection into .opencode/skills/icdt-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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
icdt-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 645 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 database-theory project belongs at ICDT (International Conference on Database Theory) or should be routed to PODS, the co-located EDBT systems track…
- Deciding whether a database-theory project belongs at ICDT (International Conference on Database Theory)
- SKILL.md covers The routing question that…, Sibling-venue routing table, What makes a paper ICDT-shaped and The two sharpening tests, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Should be routed to PODS
What it does
Icdt Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a database-theory project belongs at ICDT (International Conference on Database Theory) or should be routed to PODS, the co-located EDBT systems track, a pure-TCS venue (LICS, ICALP, STACS), or a journal (ACM TODS, LMCS, TheoretiCS), and when distinguishing ICDT from its sibling database-theory flagship PODS by calendar, publisher, and community.
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 database-theory project belongs at ICDT (International Conference on Database Theory)
- Should be routed to PODS
- The co-located EDBT systems track
- A pure-TCS venue (LICS
Example prompts
- “/icdt-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
Icdt Topic Selection loads about 1.5k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 645 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). 645 words, ~1,489 tokens.
Download SKILL.mdSave it as
.claude/skills/icdt-topic-selection/SKILL.md (or your agent's skills folder).- name
- icdt-topic-selection
- description
- Use when deciding whether a database-theory project belongs at ICDT (International Conference on Database Theory) or should be routed to PODS, the co-located EDBT systems track, a pure-TCS venue (LICS, ICALP, STACS), or a journal (ACM TODS, LMCS, TheoretiCS), and when distinguishing ICDT from its sibling database-theory flagship PODS by calendar, publisher, and community.
ICDT Topic Selection
Decide the venue before drafting. ICDT — the International Conference on Database Theory — is the European foundations-of-data-management venue, held jointly with EDBT and published open access in LIPIcs. Its referees read for a precise theorem with a clear consequence for data management: query languages, the complexity of query evaluation, finite model theory over databases, consistent query answering, provenance, and the theory of data integration. A technically strong paper whose real content is generic complexity theory, pure logic, or a systems benchmark is respected and then rejected as out of scope.
The routing question that matters most
ICDT and PODS are the two database-theory flagships and overlap almost completely in scope, so the decisive question is rarely "is this database theory?" but "which of the two theory venues, and which calendar and publisher, fits this paper now?" Both want a real theorem with a data-management payoff. Use the finer signals below and the live deadlines to choose.
Sibling-venue routing table
| Signal in your project | Better home | Why |
|---|---|---|
| Foundational data-management theorem; you want European co-location and the next ICDT cycle is nearer | ICDT | Two-cycle LIPIcs venue with a Cycle-1 revision option; co-located with EDBT |
| Same kind of theorem, but PODS's single annual cycle lands better or you want the SIGMOD stage | PODS | The other database-theory flagship; ACM PACMMOD, co-located with SIGMOD |
| The contribution is a system, an algorithm with an experimental evaluation, or a benchmark | EDBT (co-located) or a systems venue | Experimental data management, not a theorem — the reproducibility track lives here |
| The core is generic finite model theory / logic with no data-management consequence | LICS / ICALP / STACS | EATCS/logic venues reward the theory itself; ICDT wants the querying/constraints payoff |
| The result is too long, or wants a full journal treatment with all proofs | ACM TODS / LMCS / TheoretiCS | Journals with no page ceiling; some are the natural home for the extended version |
| A neat connection between database theory and a neighboring field, short | ICDT "Database Theory in Action" | The 4-page non-anonymous track for bridging results and applications |
Show full SKILL.md (310 more words)Show less
What makes a paper ICDT-shaped
- A theorem about querying or data. A new expressiveness result, a tight complexity bound for evaluating a query language, a decidability/undecidability result for a class of constraints, a dichotomy — with the database-theory consequence stated, not implied.
- Matching upper and lower bounds where the field expects them; a one-sided bound is often a "revise," not an accept.
- A model that connects to data management. Finite structures, relational/graph/semistructured data models, incomplete or inconsistent databases, provenance semirings, integration mappings — the "database" in the name is load-bearing.
- Foundational or conceptual advances — a new framework, a semantics, or a proof technique that the data-management theory community can build on.
The two sharpening tests
- PODS-swap test: could this paper appear at PODS and read as native there? Almost certainly yes — so the choice is by calendar, publisher preference (open-access LIPIcs vs ACM PACMMOD), and community pull, not by scope. Pick the nearer honest deadline unless a specific reason favors the other.
- Consequence test: strip the data-management framing — is there still a database-theory lesson, or just a complexity/logic result? If only the latter survives, a pure-TCS venue fits better and ICDT referees will say the data connection is decorative.
Maturity, without the ladder cliché
An idea sits at different doors depending on how finished the proof is. A conjecture with partial evidence is a workshop or "in action" contribution, not a regular ICDT paper; a theorem with a gap you can close belongs in Cycle 1 where the revision option exists; a fully worked, book-length treatment belongs in a journal. Submitting a one-sided bound when the field expects a matching one costs a cycle.
Cheap reconnaissance before committing
[Scope] scan the last two ICDT and PODS programs (dblp, databasetheory.org) for your subarea
-> present at both = pick by calendar; present at neither = mismatch or a new opening
[Citations] is your bibliography majority ICDT/PODS/LICS/TODS/LMCS?
-> majority systems venues => you may actually have an EDBT/SIGMOD paper
[Calendar] compare the next ICDT cycle deadline with the PODS deadline and journal timelines
-> route to the nearest honest fit; ICDT's two cycles give you two shots a yearDecision procedure
[Consequence] who in data management cares if the theorem holds? -> real payoff or decorative?
[Claim type] expressiveness / complexity / decidability / semantics / framework
[ICDT vs PODS] both fit? -> choose by calendar, open-access LIPIcs vs PACMMOD, community pull
[Sibling check] systems+experiments -> EDBT; pure logic -> LICS/ICALP; over-long -> journal
[Verdict] ICDT regular track / PODS / EDBT / TCS venue / journal, with a one-line reasonRun this before the writing skills; a wrong venue decision wastes every later step. When the verdict
is ICDT, continue with icdt-workflow for the two-cycle calendar and icdt-writing-style for the
theorem-proof 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 ICDT-Skills/skills/icdt-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icdt 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 |
|---|---|---|---|---|---|---|
| Icdt Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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 | |
| Integration Theoryparcadei/Continuous-Claude-v3 | 3.9k | 1 repos | ~929 | Automated safety check: Notes | MIT | |
| Bestblogs Topicginobefun/BestBlogs | 4k | — | ~670 | Automated safety check: Pass | None | |
| Asymptotic Theorybrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~4.6k | Automated safety check: Pass | Custom licence |
Similar skills
Topic Modeling
brycewang-stanford/Auto-Empirical-Research-Skills
Structural topic modeling: STM spec, topic count, coherence-exclusivity.
Integration Theory
parcadei/Continuous-Claude-v3
Problem-solving strategies for integration theory in measure theory
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.
Asymptotic Theory
brycewang-stanford/Auto-Empirical-Research-Skills
M-estimation, influence functions, and semiparametric efficiency theory for causal inference
Zsxq Topic
itwanger/toBeBetterJavaer
知识星球主题管理：搜索主题、查看主题详情、发布帖子、编辑主题、发表评论、回复某条评论（楼中楼）、回答提问、删除主题；通过 api call 查看主题评论列表、设置精华、设置标签、查看自己提的问题与已回答记录。当用户需要查找内容、发帖、编辑主题、评论、回复评论、回答问题、删除主题、查看主题评论、查看自己的提问记录、或管理主题精华和标签时使用。
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 Icdt Topic Selection
What does Icdt Topic Selection do?
A skill your agent uses when deciding whether a database-theory project belongs at ICDT (International Conference on Database Theory) or should be routed to PODS, the co-located EDBT systems track…. Icdt Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a database-theory project belongs at ICDT (International Conference on Database Theory) or should be routed to PODS, the co-located EDBT systems track, a pure-TCS venue (LICS, ICALP, STACS), or a journal (ACM TODS, LMCS, TheoretiCS), and when distinguishing ICDT from its sibling database-theory flagship PODS by calendar, publisher, and community.
When should I use Icdt Topic Selection?
Icdt Topic Selection fits situations like: deciding whether a database-theory project belongs at ICDT (International Conference on Database Theory); should be routed to PODS; the co-located EDBT systems track; A pure-TCS venue (LICS.
How do I install Icdt Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-topic-selection -a claude-code`. Or copy the skill folder (ICDT-Skills/skills/icdt-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icdt-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Icdt Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-topic-selection -a codex`. Or copy the skill folder (ICDT-Skills/skills/icdt-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icdt-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Icdt 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 icdt-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/icdt-topic-selection, .gemini/skills/icdt-topic-selection, .github/skills/icdt-topic-selection and .opencode/skills/icdt-topic-selection in your project.
What does Icdt Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Icdt Topic Selection is instructions for the agent only.
Does Icdt 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 Icdt 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 Icdt Topic Selection use?
Icdt 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 Icdt 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 Icdt Topic Selection?
Skills that share tags, products or a category with Icdt Topic Selection: Topics (ZimoLiao/scholaraio, 577 stars), Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Integration Theory (parcadei/Continuous-Claude-v3, 3.9k stars) and Bestblogs Topic (ginobefun/BestBlogs, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icdt 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.