Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
A skill your agent uses when deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit, structuring the in-PDF appendix versus the…
Install Cikm Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-supplementary --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/CIKM-Skills/skills/cikm-supplementary .claude/skills/cikm-supplementary && 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 "cikm-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-supplementary into .claude/skills/cikm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-supplementary", 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/CIKM-Skills/skills/cikm-supplementaryType 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 cikm-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-supplementary --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/CIKM-Skills/skills/cikm-supplementary .agents/skills/cikm-supplementary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cikm-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-supplementary into .agents/skills/cikm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-supplementary", 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 cikm-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-supplementary --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/CIKM-Skills/skills/cikm-supplementary .cursor/skills/cikm-supplementary && 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 "cikm-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-supplementary into .cursor/skills/cikm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-supplementary", 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 CIKM-Skills/skills/cikm-supplementary--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 cikm-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-supplementary --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/CIKM-Skills/skills/cikm-supplementary .gemini/skills/cikm-supplementary && 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 "cikm-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-supplementary into .gemini/skills/cikm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-supplementary", 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 cikm-supplementaryInstalls 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 cikm-supplementary -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/CIKM-Skills/skills/cikm-supplementary .github/skills/cikm-supplementary && 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 "cikm-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-supplementary into .github/skills/cikm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-supplementary", 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 cikm-supplementary -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 cikm-supplementary --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/CIKM-Skills/skills/cikm-supplementary .opencode/skills/cikm-supplementary && 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 "cikm-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-supplementary into .opencode/skills/cikm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-supplementary", 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
cikm-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 812 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit, structuring the in-PDF appendix versus the…
- Deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit
- SKILL.md covers The three containers, Building the anonymous artifact, What the uncounted sections… and Appendix design rules (for the…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Structuring the in-PDF appendix versus the anonymously cited artifact
What it does
Cikm Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit, structuring the in-PDF appendix versus the anonymously cited artifact, keeping both double-blind, and handling the uncounted GenAI-disclosure and reference sections correctly.
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 Documents & Office, covering PDF. 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 what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit
- Structuring the in-PDF appendix versus the anonymously cited artifact
- Keeping both double-blind
- Handling the uncounted GenAI-disclosure and reference sections correctly
Example prompts
- “/cikm-supplementary”
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
Cikm Supplementary loads about 1.7k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 812 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). 812 words, ~1,652 tokens.
Download SKILL.mdSave it as
.claude/skills/cikm-supplementary/SKILL.md (or your agent's skills folder).- name
- cikm-supplementary
- description
- Use when deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit, structuring the in-PDF appendix versus the anonymously cited artifact, keeping both double-blind, and handling the uncounted GenAI-disclosure and reference sections correctly.
CIKM Supplementary
CIKM 2026 gives supporting material no free rider: every track's budget counts the appendix inside the page limit — 10 pages for full papers, 4/7/4/4 for short/applied/resource/demo — and only the references (full track: up to 2 pages) plus the GenAI Usage Disclosure section sit outside it (source map, 2026-07-08). There is no separate supplementary-upload channel in the verified 2026 calls. The design question is therefore three-way: costed appendix pages, the anonymously cited artifact, or cut.
The three containers
| Container | Costs | Right contents |
|---|---|---|
| Main body | Budget pages | Everything needed to evaluate the claim unaided |
| In-PDF appendix | Budget pages too | Only material reviewers must see during review that the body cannot hold: a proof, a prompt set, a schema diagram |
| Cited anonymous artifact | Zero pages, but discretionary attention | Configs, full hyperparameter grids, extra per-dataset tables, code, data cards |
Decision rule per candidate item: must a reviewer see this to score the paper? If yes and it is short, appendix — knowing it displaces body content one-for-one. If yes and it is long, restructure the body so a summary suffices, and put the whole in the artifact. If no, artifact or delete.
Building the anonymous artifact
- Host with an anonymity-preserving service (anonymized repository links of the usual kind); the URL, commit history, issue templates, CI badges, and README must not resolve to authors or institutions.
- Strip notebook metadata, license headers naming people, internal hostnames, and
data paths like
/home/username/— the classic leak channels. - Structure for a ten-minute reviewer visit: a top-level README mapping paper section → directory, and one script per headline table. Reviewers sample; make the sample they take be the strongest material.
- Reference the artifact from the PDF at the point of relevance ("full grids: artifact §3"), not only in a final availability statement, so the pointer is found when the question arises.
What the uncounted sections may and may not carry
The GenAI Usage Disclosure section and the references are outside the budget — and they are not overflow space. Substantive results, extra experiments, or method details placed there violate the sections' declared purposes and read as budget gaming to a panel that sees the trick every year. The disclosure section carries disclosure; references carry references; nothing else.
Appendix design rules (for the pages you do spend)
When appendix pages are budget pages, they must earn their cost like body pages:
- Order appendix sections by reference order from the body, and give each a one-line purpose header ("A. Prompt templates used in §4.3") — a reviewer arriving from a citation should land exactly where sent.
- No orphans: appendix content never referenced from the body is invisible at best and budget-waste at worst; either reference it or move it to the artifact.
- Keep appendix tables to the same caption standard as body tables (protocol, variance, source); reviewers do not lower standards past the references.
- Never let the appendix complete an incomplete body argument. The body must stand alone; the appendix substantiates, it does not continue.
Show full SKILL.md (321 more words)Show less
Reviewer-attention economics
Plan the material split around how attention actually distributes:
| Material location | Realistic reviewer attention | Design consequence |
|---|---|---|
| Body pages 1-2 | Everyone, carefully | The whole argument, compressed |
| Body middle | Everyone, once | Protocol and headline evidence |
| In-PDF appendix | Sometimes, when following a specific doubt | Doubt-resolving material only |
| Artifact README | A minority, for ~10 minutes | Orientation + strongest single script |
| Artifact internals | Rarely, and only if the README earned trust | Completeness, not persuasion |
The split fails when persuasion-critical material sits below its audience's attention line — which is why "nothing decision-critical lives only in the artifact" recurs across this pack.
Worked split: a 13-page full-paper draft
A draft holds 9 pages of core, 2 pages of extra per-dataset tables, 1 page of prompts, 1 page of proofs. Target: 10 including appendix. Moves: per-dataset tables → artifact, keeping one summary row per dataset in the body (saves ~1.7 pages); prompts → appendix at half a page by showing one template plus deltas, full set → artifact; proof → appendix, compressed to the lemma statements with the full derivation in the artifact. Result: 10 pages with the review-critical material still in the PDF, and nothing decision-relevant living solely in the artifact — because artifact inspection is at reviewer discretion, never guaranteed.
Version-consistency discipline
Body, appendix, and artifact are three copies of one experimental truth, and they drift independently under deadline pressure. Locks that prevent it: generate paper tables from the same logged results the artifact ships (one source of numbers, two renderings); when a result updates, update body summary, appendix table, and artifact data in the same commit; and record in the artifact README which commit corresponds to the submitted PDF, so a reviewer comparing the two sees agreement, not archaeology. A number that differs between the PDF and the artifact is read as sloppiness at best — and at a venue that reserves automated compliance checking, consistency across submitted surfaces is the cheap kind of integrity to maintain.
Pre-upload verification
[ ] Page count with appendix ≤ track budget (measure, don't estimate)
[ ] Artifact URL anonymous end-to-end (open it logged out; check git log)
[ ] Every artifact pointer in the PDF resolves to real content
[ ] GenAI/reference sections carry only their declared content
[ ] Body survives a reviewer who never opens the artifactOutput format
[Budget state] <measured pages incl. appendix vs. track limit>
[Split map] <item → body / appendix / artifact / cut>
[Artifact health] anonymity / README / per-table scripts
[Gaming check] uncounted sections clean?
[Residual risk] <what a no-artifact reviewer would still miss>© 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 CIKM-Skills/skills/cikm-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cikm Supplementary 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 |
|---|---|---|---|---|---|---|
| Cikm Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Gzh Designisjiamu/gzh-design-skill | 4k | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| GenOffice Document CLIgenspark-ai/genoffice | 9.2k | — | ~19k | Automated safety check: Pass | Apache-2.0 | |
| Harness Book Best Practicewquguru/harness-books | 3.2k | — | ~4.1k | Automated safety check: Pass | None | |
| Bookforge Korean Ebook PDF Makergongnyang/bookforge | 316 | 1 repos | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
GenOffice Document CLI
genspark-ai/genoffice
Creates, converts, reads and edits real pptx, xlsx, docx and PDF files locally through the genoffice command line.
Harness Book Best Practice
wquguru/harness-books
Best practices for working on the Harness books repo. An agent skill from wquguru/harness-books.
Bookforge Korean Ebook PDF Maker
gongnyang/bookforge
Produces book-style Korean ebook PDFs from a topic or finished manuscript, with six design styles, real book parts and quality-check gates before output.
- Official
Instrument Data To Allotrope
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
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 Cikm Supplementary
What does Cikm Supplementary do?
A skill your agent uses when deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit, structuring the in-PDF appendix versus the…. Cikm Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit, structuring the in-PDF appendix versus the anonymously cited artifact, keeping both double-blind, and handling the uncounted GenAI-disclosure and reference sections correctly.
When should I use Cikm Supplementary?
Cikm Supplementary fits situations like: deciding what supporting material accompanies a CIKM submission given budgets that count appendices inside the page limit; structuring the in-PDF appendix versus the anonymously cited artifact; keeping both double-blind; handling the uncounted GenAI-disclosure and reference sections correctly.
How do I install Cikm Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-supplementary -a claude-code`. Or copy the skill folder (CIKM-Skills/skills/cikm-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cikm-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Cikm Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-supplementary -a codex`. Or copy the skill folder (CIKM-Skills/skills/cikm-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cikm-supplementary in your project. Codex loads it when a task matches its description.
Can I use Cikm Supplementary 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 cikm-supplementary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cikm-supplementary, .gemini/skills/cikm-supplementary, .github/skills/cikm-supplementary and .opencode/skills/cikm-supplementary in your project.
What does Cikm Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Cikm Supplementary is instructions for the agent only.
Does Cikm Supplementary 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 Cikm Supplementary 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 Cikm Supplementary use?
Cikm Supplementary 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 Cikm Supplementary use?
About 1.7k tokens (SKILL.md is roughly 6.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 Cikm Supplementary?
Skills that share tags, products or a category with Cikm Supplementary: Markitdown (ImCa0/just-laws, 781 stars), Gzh Design (isjiamu/gzh-design-skill, 4k stars), GenOffice Document CLI (genspark-ai/genoffice, 9.2k stars) and Harness Book Best Practice (wquguru/harness-books, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cikm Supplementary?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.